AOS, when used as a VPN Gateway, must be configured to use IPsec with SHA-2 at 384 bits or greater for hashing to protect the integrity of remote access sessions.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-266983	ARBA-VN-000220	SV-266983r1040715_rule	CCI-001453	medium
Description
Without strong cryptographic integrity protections, information can be altered by unauthorized users without detection. SHA-1 is considered a compromised hashing standard and is being phased out of use by industry and government standards. DOD systems must not be configured to use SHA-1 for integrity of remote access sessions. The remote access VPN provides access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Satisfies: SRG-NET-000063-VPN-000220, SRG-NET-000074-VPN-000250, SRG-NET-000168-VPN-000600, SRG-NET-000230-VPN-000780
STIG			Date
HPE Aruba Networking AOS VPN Security Technical Implementation Guide			2024-10-29

Related Frameworks

3 paths across 3 frameworks

NIST 800-531 mapping

AC-17(2)

1.00

DISA · V1R1 · disa_xccdf · related
DISA · 2025-01-23 · disa_cci_list · equivalent

NIST 800-1711 mapping

3.1.13

1.00

DISA · V1R1 · disa_xccdf · related
DISA · 2025-01-23 · disa_cci_list · equivalent
NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent

CCI1 mapping

CCI-001453

1.00

DISA · V1R1 · disa_xccdf · related

Details

Check Text (C-266983r1040715_chk)

1. Verify the AOS configuration with the following command: show crypto-local ipsec-map Note the IKEv2 Policy number for each configured map. 2. For each configured policy number, run the following command: show crypto isakmp policy <IKEv2 Policy #> If each configured IKEv2 policy hash algorithm is not configured with SHA-2 at 384 bit, this is a finding.

Fix Text (F-70810r1040714_fix)

Configure AOS with the following commands: configure terminal crypto isakmp policy <priority> hash sha2-384-192 exit write memory