The ICS must be configured to disable split-tunneling for remote client VPNs.
An XCCDF Rule
Description
<VulnDiscussion>Split tunneling would in effect allow unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information. A VPN hardware or software client with split tunneling enabled provides an unsecured backdoor to the enclave from the internet. With split tunneling enabled, a remote client has access to the internet while at the same time has established a secured path to the enclave via an IPsec tunnel. A remote client connected to the internet that has been compromised by an attacker on the internet, provides an attack base to the enclave's private network via the IPsec tunnel. Hence, it is imperative that the VPN gateway enforces a no split-tunneling policy to all remote clients.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-258596r930476_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
In the ICS Web UI, navigate to Users >> Resource Policies >> Split Tunneling Networks.
1. If there are any split-tunnel network policies configured, select all of them and delete them.
2. If the split tunneling policies are needed for debugging or testing only, ensure the role being applied is only for the debugging or test group.