Weak IKE or IPsec algorithms
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
DES and 3DES, MD5 and SHA-1, and Diffie-Hellman groups 1, 2 and 5 are deprecated; a tunnel that can negotiate them is only as strong as the weakest offer.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- In FMC (or cdFMC): Objects > Object Management > VPN > IKEv2 Policy and IPsec Proposal: AES-GCM-256 or AES-256, SHA-384 or SHA-512, DH 20 or 21, then select them in the topology (agree with the peer first). Save, Deploy.
- In FDM: Objects > IKE Policies and IPsec Proposals, then select them in the connection and Deploy.
Command line
This analyzer version writes no command text for this control. The steps above are the remediation it offers.
How to confirm the fix
- On the FTD CLI (read only): show running-config crypto, and confirm the weak values are gone.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.