Decryption profile permits a legacy cipher, hash or key exchange
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
RC4 and 3DES are broken or obsolete ciphers, SHA1 is a deprecated hash and RSA key exchange gives no forward secrecy. Permitting them lets a session the firewall decrypts be negotiated down to protection an attacker on the path can defeat.
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 enc-algo-rc4, enc-algo-3des, auth-algo-sha1 and keyxchg-algo-rsa to no in the profile's SSL protocol settings.
- Check what the profile is attached to first: an old server that only speaks these will stop completing sessions.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 profiles decryption <object-name> ssl-protocol-settings enc-algo-rc4 noset vsys vsys1 profiles decryption <object-name> ssl-protocol-settings enc-algo-3des noset vsys vsys1 profiles decryption <object-name> ssl-protocol-settings auth-algo-sha1 noset vsys vsys1 profiles decryption <object-name> ssl-protocol-settings keyxchg-algo-rsa no
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 vsys vsys1 profiles decryption <object-name> ssl-protocol-settingsValues to fill in1
- <object-name>
- The object's name, as it appears on your firewall
Before you type it1
- Clients that only speak the older versions stop connecting. Find them before you commit.
How to confirm the fix
- Reopen the profile's SSL protocol settings and confirm each algorithm is off.
- Confirm the applications carried by the rules using this profile still complete.
Limits
- A setting the profile does not write inherits a PAN-OS default this file does not record; the check reports it as not written, not as permitted.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in Decryption
- PAN-SEC-014No decryption policy covering outbound traffic
- PAN-SEC-089Decryption profile permits a TLS version with published breaks
- PAN-SEC-090Decryption profile permits an invalid server certificate
- PAN-SEC-091Decryption rule excludes a high-risk URL category from decryption
- PAN-SEC-107Decryption profile lets undecryptable forward proxy sessions through
- PAN-SEC-134Decrypted content is not forwarded to WildFire
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.