The IPsec BIG-IP appliance must use IKEv2 for IPsec VPN security associations.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-266282 | F5BI-VN-300024 | SV-266282r1024757_rule | CCI-000382 | medium |
| Description | ||||
| To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types); organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems. Use of IKEv2 leverages denial of service (DoS) protections because of improved bandwidth management and leverages more secure encryption algorithms. | ||||
| STIG | Date | |||
| F5 BIG-IP TMOS VPN Security Technical Implementation Guide | 2024-09-09 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-7
1.00
- DISA · V1R1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.4.6
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-000382
1.00
- DISA · V1R1 · disa_xccdf · related
Details
Check Text (C-266282r1024757_chk)
From the BIG-IP GUI:
1. Network.
2. IPsec.
3. IKE Peers.
4. Click on the name of the IKE peer.
5. Verify "Version 2" is selected for "Version".
If the BIG-IP appliance is not configured to use IKEv2 for IPsec VPN security associations, this is a finding.
Fix Text (F-70109r1024093_fix)
From the BIG-IP GUI:
1. Network.
2. IPsec.
3. IKE Peers.
4. Click on the name of the IKE peer.
5. Select "Version 2" for "Version".
6. Click "Update".