Forescout appliance must not be configured to implement a DHCP layer 3 method for separation or device authorization. This is required for compliance with C2C Step 2.
An XCCDF Rule
Description
<VulnDiscussion>Using DHCP, an internal rogue device can still bypass the authentication process, regardless of the policy flow. Older version of the ForeScout may have a setting to support DHCP for NAC authorization. This capability should not be used. The DHCP Classifier Plugin allows Forescout to view and use DHCP properties that can be used to improve classification of uncategorized devices obtained from DHCP-enabled network-connected devices. However, DHCP should not be used as the primary authentication method on the NAC.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-233315r1018662_rule
- Severity
- High
- References
- Updated
Remediation - Manual Procedure
If the NAC software version has the capability to configure the DHCP protocol for device authentication or authorization for network access requests:
1. Log on to the Forescout UI.
2. Locate the Authentication & Authorization policy.
3. Disable DHCP if used.