The F5 BIG-IP appliance IPsec VPN must be configured to use FIPS-validated SHA-2 or higher for Internet Key Exchange (IKE).
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-266287 | F5BI-VN-300041 | SV-266287r1024762_rule | CCI-001184 | high |
| Description | ||||
| Without cryptographic integrity protections, information can be altered by unauthorized users without detection. 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 must not be configured to use SHA-2 for integrity of remote access sessions. This requirement is applicable to the configuration of IKE Phase 1 and Phase 2. | ||||
| STIG | Date | |||
| F5 BIG-IP TMOS VPN Security Technical Implementation Guide | 2024-09-09 | |||
Details
Check Text (C-266287r1024762_chk)
From the BIG-IP GUI:
1. Network.
2. IPsec.
3. IKE Peers.
4. Click on the name of the IKE peer.
5. Verify "SHA-1" or "MD5" is not selected for the following:
IKE Phase 1 Algorithms >> Authentication Algorithm
IKE Phase 1 Algorithms >> Pseudo-Random Function
From the BIG-IP GUI:
1. Network.
2. IPsec.
3. IPsec Policies.
4. Click the name of the IPsec Policy.
5. Verify "SHA-1" is not selected for the following:
IKE Phase 2 >> Authentication Algorithm
If the BIG-IP appliance is not configured to use FIPS-validated SHA-2 or higher for IKE, this is a finding.
Fix Text (F-70114r1024108_fix)
From the BIG-IP GUI:
1. Network.
2. IPsec.
3. IKE Peers.
4. Click on the name of the IKE peer.
5. Configure SHA-2 or higher for the following:
IKE Phase 1 Algorithms >> Authentication Algorithm
IKE Phase 1 Algorithms >> Pseudo-Random Function
6. Click "Update".
From the BIG-IP GUI:
1. Network.
2. IPsec.
3. IPsec Policies.
4. Click the name of the IPsec Policy.
5. Configure SHA-2 or higher for the following:
IKE Phase 2 >> Authentication Algorithm
6. Click "Update".