Skip to content

The Cisco ASA VPN remote access server must be configured to disable split-tunneling for remote clients.

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 in 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-239982r1005432_rule
Severity
Medium
References
Updated



Remediation - Manual Procedure

Configure the ASA to disable split-tunneling for remote clients VPNs as shown in the example below.

ASA2(config)# group-policy ANY_CONNECT_GROUP attributes
ASA2(config-group-policy)# split-tunnel-policy tunnelall
ASA2(config-group-policy)# end