Skip to content

All controls

PAN-SEC-052HighPAN-OS

IPSec crypto profile offers a weak algorithm

At a glance

Base severity

High

Area

IPSec VPN

Platform

PAN-OS

Evidence level

Fact1.00

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 IPSec phase two proposal is what actually protects tunnel payload. DES and 3DES are 64-bit block ciphers, and a long lived tunnel can carry enough traffic to make Sweet32 practical. MD5 and SHA1 weaken the integrity check that stops a payload being altered in transit.

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.

  1. Set ESP encryption to AES-128 or stronger, preferably an AES-GCM suite.
  2. Set ESP authentication to SHA-256 or stronger.
  3. Set the perfect forward secrecy group to group14 or stronger.
  4. Agree the change with the peer administrator, because both ends have to match.

Command line

PAN-OS CLI

set network ike crypto-profiles ipsec-crypto-profiles <object-name> esp encryption <encryption-algorithm>set network ike crypto-profiles ipsec-crypto-profiles <object-name> esp authentication <hash-algorithm>set network ike crypto-profiles ipsec-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 ipsec-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 two 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.

See it on your own firewall

One complete analysis of one firewall costs nothing. A card is required and nothing is charged.

Start a free analysis