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 5 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-266992

CAT II (Medium)

AOS, when used as a VPN Gateway, must ensure inbound and outbound traffic is configured with a security policy in compliance with information flow control policies.

Rule ID

SV-266992r1040904_rule

STIG

HPE Aruba Networking AOS VPN Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-001414

Discussion

Unrestricted traffic may contain malicious traffic, which poses a threat to an enclave or to other connected networks. Additionally, unrestricted traffic may transit a network, which uses bandwidth and other resources. VPN traffic received from another enclave with different security policy or level of trust must not bypass being inspected by the firewall before being forwarded to the private network.

Check Content

Verify the AOS configuration with the following command:
show running-config | begin "interface gigabit"

Note the configured IP access-group session ACL for each active interface. 

For each configured ACL:
show ip access-list <ACL name>

If each ACL does not end in an "any any deny log" for both IPv4 and IPv6, this is a finding.

Fix Text

Configure AOS with the following commands: 
configure terminal
ip access-list session <name>
network <A.B.C.D> <netmask A.B.C.D> any any permit
any any any deny log
ipv6 network <X:X:X:X::X/<0-128> any any permit
ipv6 any any any deny log
exit
write memory
interface gigabit <#/#/#>
ip access-group session <ACL name>
exit
write mem