IPsec gateway on IKEv1
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
IKEv1 is superseded by IKEv2, which resists more attacks on the exchange and handles rekeying and peer failure better.
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.
- Set ike-version 2 on the gateway, together with the peer.
Command line
FortiOS CLI
config vpn ipsec phase1-interfaceedit <phase1-name>set ike-version 2nextend
An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. FortiOS saves a change when you type next or end, with no separate commit. Read every line first.
Read it back
show vpn ipsec phase1-interface <phase1-name>Values to fill in1
- <phase1-name>
- The IPsec gateway to change
Before you type it3
- Written from the FortiOS CLI Reference, not yet run on a device. Read each line before typing it.
- On a device with VDOMs, type these inside the VDOM (config vdom, edit the VDOM) or inside config global for a global setting.
- The far end has to offer the same proposal, so coordinate the change with whoever runs it.
How to confirm the fix
- Confirm the peer supports IKEv2 and the tunnel negotiates after the change.
Limits
- A setting the backup does not write is read as FortiOS's documented default for the device's release.
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.