The Juniper SRX Services Gateway VPN IKE must use NIST FIPS-validated cryptography to implement encryption services for unclassified VPN traffic.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-214691 | JUSX-VN-000024 | SV-214691r1056097_rule | Medium |
| Description |
| Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The network element must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. |
| STIG | Date |
| Juniper SRX Services Gateway VPN Security Technical Implementation Guide | 2024-12-20 |
Details
| Check Text (C-15892r1056095_chk) |
| Verify all Internet Key Exchange (IKE) proposals are set to use AES256. [edit] show security ike View the value of the encryption algorithm for each defined proposal. If the value of the authentication method and other options are not set to use FIPS-validated values, this is a finding. |
| Fix Text (F-15890r1056096_fix) |
| The following example commands configure the IKE (phase 1) proposal. [edit] set security ike proposal <P1-PROPOSAL> authentication-method rsa-signatures set security ike proposal p1-proposal dh-group group19 set security ike proposal p1-proposal authentication-algorithm sha-384 set security ike proposal p1-proposal encryption-algorithm aes-256-cbc set security ike proposal p1-proposal lifetime-seconds 86400 |