STIGViewer Support

Forescout must be configured so client machines do not communicate with other network devices in the DMZ or subnet except as needed to perform an access client assessment or to identify themselves. This is required for compliance with C2C Step 2.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-233319FORE-NC-000110SV-233319r1111892_ruleCCI-000213medium
Description
Devices not compliant with DOD secure configuration policies are vulnerable to attack. While endpoints are undergoing NAC authorization assessment, they must communicate only with the NAC. These devices should not communicate with other hosts in the DMZ or other network segments.
STIGDate
Forescout Network Access Control Security Technical Implementation Guide2025-06-12

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (20) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
HRS-02Position Categorization
1.00
HRS-11Separation of Duties (SoD)
1.00
IAC-01Identity & Access Management (IAM)
1.00
IAC-01.2Authenticate, Authorize and Audit (AAA)
1.00
IAC-02Identification & Authentication for Organizational Users
1.00
IAC-03Identification & Authentication for Non-Organizational Users
1.00
IAC-04Identification & Authentication for Devices
1.00

+10 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (93) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-18(1)Authentication and Encryption
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00

+83 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.1
1.00
3.1.2
1.00
CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

Who does this work

17 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-233319r1111892_chk)

If DOD is not at C2C Step 2 or higher, this is not a finding. Verify ForeScout is configured so endpoints under assessment are isolated from peer communication. 1. Navigate to the Policy tab and examine the Compliance Assessment policy. 2. Verify either a Quarantine VLAN, ACL Enforcement Method, or Forescout Virtual Firewall is configured as part of the policy. If Forescout allows endpoints under assessment to communicate with other endpoints in the DMZ or on other network segments, this is a finding.

Fix Text (F-36479r1111891_fix)

Configure ForeScout so devices being assessed for compliance do not communicate with other devices in the DMZ or other network segments. There are different approaches; however, this typically involves isolating noncompliant devices into a quarantine or assessment zone until they meet compliance requirements. The following are examples. Create a Quarantine VLAN: 1. Set up a dedicated VLAN (e.g., "Quarantine_VLAN") for devices under assessment. 2. This VLAN should have restricted access, blocking communication to other devices or production network segments. 3. Allow traffic only to specific remediation servers (e.g., patch servers, ForeScout appliance for assessment). 4. Configure the switches to support dynamic VLAN assignment via CounterACT. 5. Enforce Network Isolation using a VLAN: - Select the "Quarantine_VLAN". - CounterACT will instruct the switch (via SNMP or CLI) to move the device to this VLAN upon detection. Or ACL Enforcement Method: 1. If VLANs are not feasible, use the **Apply ACL** action. 2. Configure an ACL on the switches or routers to block all traffic from the device’s IP or MAC to other network devices, allowing only traffic to remediation servers (e.g., IP of patch server, DNS, or CounterACT appliance). - Example ACL (syntax depends on the switch/router): ``` deny ip <device_IP> 0.0.0.0 <network_range> <network_mask> permit ip <device_IP> 0.0.0.0 <remediation_server_IP> 0.0.0.0 permit ip <device_IP> 0.0.0.0 <forescout_IP> 0.0.0.0 deny ip any any ``` Or Virtual Firewall Method: 1. Use CounterACT’s Virtual Firewall action to block all traffic from the device except to specific IPs/ports (e.g., remediation servers, CounterACT). 2. Configure rules in the action settings to allow only necessary outbound traffic.