OpenControls Logo

STIG Viewer

STIGViewer Support

The Cisco ASA must be configured to use FIPS-validated SHA-2 or higher for Internet Key Exchange (IKE) Phase 2.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-239959CASA-VN-000240SV-239959r1005430_ruleCCI-001184high
Description
Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions. Although allowed by SP800-131Ar2 for some applications, SHA-1 is considered a compromised hashing standard and is being phased out of use by industry and government standards. Unless required for legacy use, DOD systems should not be configured to use SHA-1 for integrity of remote access sessions. This requirement focuses on communications protection for the application session rather than for the network packet and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. Depending on the required degree of confidentiality and integrity, web services/SOA will require the use of mutual authentication (two-way/bidirectional). An IPsec Security Association (SA) is established using either IKE or manual configuration.
STIGDate
Cisco ASA VPN Security Technical Implementation Guide2024-08-22

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

NET-09Session Integrity
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (30) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
AU-9(3)Cryptographic Protection
1.00
CM-14Signed Components
1.00
CM-5(3)Signed Components
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
IA-2(1)Multi-factor Authentication to Privileged Accounts
1.00
IA-2(12)Acceptance of PIV Credentials
1.00

+20 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.13.15
1.00
CCI1 mapping
CCI-001184
1.00

Details

Check Text (C-239959r1005430_chk)

Review the ASA configuration to verify that SHA-2 or higher is specified for IKE Phase 2 as shown in the example below. Step 1: Review the crypto map for IKE Phase 2. crypto map IPSEC_MAP 10 set ikev2 ipsec-proposal AES_SHA Step 2: Verify that the proposal specifies SHA-2 or higher. crypto ipsec ikev2 ipsec-proposal AES_SHA protocol esp encryption … protocol esp integrity sha-384 sha-256 If the ASA is not configured to use SHA-2 or higher for IKE Phase 2, this is a finding.

Fix Text (F-43151r1005429_fix)

Configure the ASA to use FIPS-validated SHA-2 or higher for IKE Phase 2. Step 1: Configure the IKE Phase 2 proposal as shown in the example below. ASA1(config)# crypto ipsec ikev2 ipsec-proposal AES_SHA ASA1(config-ipsec-proposal)# protocol esp integrity sha-384 sha-256 ASA1(config-ipsec-proposal)# exit Step 2: Configure the crypto map using the configured proposal. ASA1(config)# crypto map IPSEC_MAP 10 set ikev2 ipsec-proposal ASA1(config)# end