← Back to HPE Aruba Networking AOS VPN Security Technical Implementation Guide

V-266990

CAT III (Low)

AOS, when used as a VPN Gateway, must terminate all network connections associated with a communications session at the end of the session.

Rule ID

SV-266990r1040736_rule

STIG

HPE Aruba Networking AOS VPN Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-001133

Discussion

Idle Transmission Control Protocol (TCP) sessions can be susceptible to unauthorized access and hijacking attacks. By default, routers do not continually test whether a previously connected TCP endpoint is still reachable. If one end of a TCP connection idles out or terminates abnormally, the opposite end of the connection may still believe the session is available. These "orphaned" sessions use up valuable router resources and can be hijacked by an attacker. To mitigate this risk, routers must be configured to send periodic keep-alive messages to check that the remote end of a session is still connected. If the remote device fails to respond to the TCP keep-alive message, the sending router will clear the connection and free resources allocated to the session.

Check Content

Verify the AOS configuration with the following command:
show configuration effective | include dpd

If DPD is not configured, this is a finding.

Fix Text

Configure AOS with the following commands:
configure terminal
crypto-local isakmp dpd idle-timeout <idle_sec> retry-timeout <retry_sec> retry-attempts <retry_number>
write memory