Vulnerability protection profile does not block critical or high severity
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
Critical and high severity vulnerability signatures are the exploits for flaws that give an attacker code execution or control of a host. A profile that alerts on them, or leaves them to each signature's default, records the attempt and lets it reach the server.
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.
- Add or change a rule so that critical and high severity signatures take reset-both, reset-server or drop.
- Keep medium, low and informational at default unless there is a reason to change them.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 profiles vulnerability <object-name> rules <profile-rule> severity [ critical high ]set vsys vsys1 profiles vulnerability <object-name> rules <profile-rule> action reset-both
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 vulnerability <object-name> rulesValues to fill in2
- <object-name>
- The object's name, as it appears on your firewall
- <profile-rule>
- The rule inside the profile, as it appears on your firewall
Before you type it1
- A profile's rules match in order, first match wins. Place the blocking rule above any rule that alerts on the same signatures.
How to confirm the fix
- Reopen the profile and confirm a blocking action on every rule naming critical or high.
- Watch the threat log for the applications this profile covers for a day after the change, for exploits that were only alerted before.
Limits
- The action is read per rule. The benchmark asks for an explicit block on critical and high; a rule left at default follows each signature's own action and is reported here.
- A profile this check does not report is not shown to block critical and high: a severity no rule names is not listed by the reading, so it is counted as not established rather than as met.
Compliance references
CIS Palo Alto Firewall 11 Benchmark v1.2.0
Covers part of the recommendation
Where a control aligns with a recommendation of the CIS Palo Alto Firewall 11 Benchmark v1.2.0, that recommendation is cited as a reference. Only that version was checked. A reference is not a certification.
More in Security Profiles
- PAN-SEC-085URL filtering profile alerts on or allows a high-risk category
- PAN-SEC-086WildFire analysis profile forwards a narrowed set of file types or one direction
- PAN-SEC-087Anti-spyware profile has DNS lists and nothing set to sinkhole
- PAN-SEC-088Anti-spyware profile sinkholes DNS queries to no address
- PAN-SEC-100Anti-spyware profile does not block every severity
- PAN-SEC-133WildFire file size limit is below the documented default
- PAN-SEC-135WildFire session information is not all sent
- PAN-SEC-136Antivirus profile does not reset both sides on every decoder
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.