No log forwarding profile is configured to alert on malicious WildFire verdicts
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
WildFire judges a file after it was delivered. A malicious verdict means a host may already hold, or have run, the file, and no destination receives an alert when that verdict arrives.
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.
- Under Objects, Log Forwarding, add a match list for the wildfire log type with a filter such as (verdict neq benign), sent to an email, syslog, SNMP trap or HTTP server profile.
- Attach the profile to the security rules that carry a WildFire Analysis profile.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 log-settings profiles <log-forwarding-profile> match-list <wildfire-match-list> log-type wildfireset vsys vsys1 log-settings profiles <log-forwarding-profile> match-list <wildfire-match-list> filter "(verdict neq benign)"set vsys vsys1 log-settings profiles <log-forwarding-profile> match-list <wildfire-match-list> send-syslog <server-profile>
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 log-settings profiles <log-forwarding-profile>Values to fill in3
- <log-forwarding-profile>
- The log forwarding profile to attach
- <wildfire-match-list>
- A name for the match list entry
- <server-profile>
- The server profile to use
Before you type it1
- A log forwarding profile sends nothing until a rule names it.
How to confirm the fix
- Confirm a WildFire test file produces an alert at the destination.
Limits
- Only match lists with no filter, or a filter naming the malicious verdict or excluding only benign, are counted; a WildFire match list with any other filter is recorded rather than judged.
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 Logging and Integrations
- PAN-SEC-032SNMP v2c is enabled
- PAN-SEC-074Syslog destination is sent without TLS
- PAN-SEC-075System or configuration logs are forwarded nowhere
- PAN-SEC-076SNMP trap profile uses SNMP v2c
- PAN-SEC-077SNMP answers on management with no permitted IP list
- PAN-SEC-079Log server profile is referenced by no log setting
- PAN-SEC-117No log entry when the data plane is fully loaded
- PAN-SEC-161Log forwarding profile does not forward traffic or threat logs
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.