The Juniper SRX Services Gateway VPN must use IKEv2 for IPsec VPN security associations.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-214683 | JUSX-VN-000016 | SV-214683r997555_rule | CCI-000382 | medium |
| Description | ||||
| Use of IKEv2 leverages DoS protections because of improved bandwidth management and leverages more secure encryption algorithms. | ||||
| STIG | Date | |||
| Juniper SRX Services Gateway VPN Security Technical Implementation Guide | 2024-12-20 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
CM-7
1.00
- DISA · V3R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.4.6
1.00
- DISA · V3R2 · 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 · V3R2 · disa_xccdf · related
Details
Check Text (C-214683r997555_chk)
Verify only IKEv2 is used for the IKE security configuration on all configured gateways. Use of IKEv1 mitigates the risk to a CAT III finding.
Show security ike gateway <VPN-GATEWAY>
If IKEv2 is not used for IKE associations, this is a finding.
Fix Text (F-15882r297637_fix)
For site-to-site VPNs, configure the Juniper SRX to use IKEv2 only.
[edit]
set security ike gateway <VPN-GATEWAY> address <GW-IP-ADDRESS>
set security ike gateway <VPN-GATEWAY> version v2-only