Skip to content

AOS, when used as a VPN Gateway, must disable split-tunneling for remote client VPNs.

An XCCDF Rule

Description

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.

ID
SV-267000r1040766_rule
Version
ARBA-VN-001620
Severity
Medium
References
Updated

Remediation Templates

A Manual Procedure

Configure AOS using the following commands:
configure terminal
wlan virtual-ap <profile name>
forward-mode tunnel
exit
write memory