IKE crypto profile offers a weak algorithm
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
The IKE phase one exchange protects the keys every packet in the tunnel is later encrypted with. DES and 3DES are 64-bit block ciphers vulnerable to Sweet32, MD5 and SHA1 are broken for the integrity guarantees the exchange depends on, and Diffie-Hellman groups below group14 are within reach of precomputation. Recovering phase one exposes everything the tunnel carries.
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 the encryption to AES-128 or stronger, preferably an AES-GCM suite.
- Set the hash to SHA-256 or stronger.
- Set the Diffie-Hellman group to group14 or stronger, and group19 or group20 where the peer supports it.
- Agree the change with the peer administrator before applying it, because both ends have to match.
Command line
PAN-OS CLI
set network ike crypto-profiles ike-crypto-profiles <object-name> encryption <encryption-algorithm>set network ike crypto-profiles ike-crypto-profiles <object-name> hash <hash-algorithm>set network ike crypto-profiles ike-crypto-profiles <object-name> dh-group <dh-group>
An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Nothing here commits. Review the candidate configuration, then commit it yourself.
Read it back
show network ike crypto-profiles ike-crypto-profiles <object-name>Values to fill in4
- <object-name>
- The object's name, as it appears on your firewall
- <encryption-algorithm>
- The encryption algorithm both ends will offer
- <hash-algorithm>
- The authentication algorithm both ends will offer
- <dh-group>
- The Diffie-Hellman group both ends will offer
Before you type it1
- 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 the stronger proposal before the change window.
- Confirm phase one negotiates on the new proposal after the change.
Limits
- The peer's supported algorithms are set on the peer.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in IPSec VPN
- PAN-SEC-052IPSec crypto profile offers a weak algorithm
- PAN-SEC-053IKE gateway is configured for IKEv1
- PAN-SEC-054IPSec tunnel has no tunnel monitoring
- PAN-SEC-055IKE gateway has dead peer detection disabled
- PAN-SEC-092Weak crypto profile is used by no gateway or tunnel
- PAN-SEC-093Enabled IPSec tunnel has no route into it
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.