Log forwarding profile does not forward traffic or threat logs
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
Rules with this profile attached are configured to keep those logs on the firewall alone. The firewall's local log storage rolls over, so a threat or a session that needs investigating later may be found nowhere else.
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 a match list for each missing log type to the profile, under Objects, Log Forwarding, with Panorama or a syslog server as the destination.
Command line
PAN-OS CLI, standalone firewall, vsys1
set vsys vsys1 log-settings profiles <object-name> match-list <traffic-match-list> log-type trafficset vsys vsys1 log-settings profiles <object-name> match-list <traffic-match-list> send-syslog <server-profile>set vsys vsys1 log-settings profiles <object-name> match-list <threat-match-list> log-type threatset vsys vsys1 log-settings profiles <object-name> match-list <threat-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 <object-name>Values to fill in4
- <object-name>
- The object's name, as it appears on your firewall
- <traffic-match-list>
- A name for the match list entry
- <threat-match-list>
- A name for the match list entry
- <server-profile>
- The server profile to use
Before you type it2
- Add a match list only for a log type that has none. A type that already reaches a destination needs no second one.
- A log forwarding profile sends nothing until a rule names it.
How to confirm the fix
- Confirm the destination receives traffic and threat entries after commit.
Limits
- A rule's profile is found where PAN-OS looks for it: the rule's own virtual system or device group, the device group's ancestors, then Shared, nearest first. A profile this file does not hold is recorded rather than judged.
- Traffic logs may be left local on purpose where their volume is too high to forward; the finding names the gap, the decision is the organization's.
Compliance references
No benchmark recommendation is mapped to this control in this version.
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-162No log forwarding profile is configured to alert on malicious WildFire verdicts
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.