STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to HPE Aruba Networking AOS VPN Security Technical Implementation Guide

V-267000

CAT II (Medium)

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

Rule ID

SV-267000r1040766_rule

STIG

HPE Aruba Networking AOS VPN Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-002397

Discussion

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.

Check Content

Verify the AOS configuration with the following commands:
show wlan virtual-ap

For each active WLAN virtual-ap profile:
show wlan virtual-ap <name> | include "Forward mode"
 
show ap system-profile

For each active AP system-profile:
show ap system-profile <name> | include "Double Encrypt"
 
show aaa authentication via connection-profile

For each referenced profile:
show aaa authentication via connection-profile <name> | include "Enable split tunneling"
 
If any instances of remote access or virtual-ap profile forward mode of split-tunnel are found or if double-encrypt is not enabled per active AP system profile, this is a finding.

Fix Text

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

For each VIA connection profile:
vaaa authentication via connection-profile <name>
no split-tunneling
exit
write memory