Palo Alto Networks

UTMStack v12 collects Palo Alto Networks firewall logs through the UTMStack Forwarder, which the web interface calls the Collector. You enable the Palo Alto integration on a Collector, then configure PAN-OS to send syslog to that Collector. Nothing is installed on the firewall.

Connection details

SettingValue
Card on the Integrations pagePalo Alto (category Firewall)
Data typefirewall-paloalto
Default ports on the Collector7006/UDP; 7006/TCP (also used for TLS)
Log format UTMStack readsPAN-OS default CSV log format, with a BSD or IETF syslog header. Palo Alto's documented CEF templates are also read.
Parsing pipelinepaloalto/pa_firewall.yaml, version 3.1.3. Filters in the card's drawer opens it.
Detection rules11. Rules in the card's drawer opens them.

Before you begin

  • A Collector must be installed and online. If you do not have one, see UTMStack Forwarder. One Collector can serve all your integrations.

  • The firewall must reach the Collector host on the port you use. Open it on the Collector host and on any firewall in between.

  • You need the integrations.write permission to enable the integration from the web interface.

  • Threat and URL log lines can be long. If you can, send over TCP or TLS: over UDP, the Collector reads at most 2,048 bytes of each message.

Step 1: Enable the integration on a Collector

  1. 1

    Open the integration

    In UTMStack, go to Configure > Integrations and open the Palo Alto card.

    Palo Alto Networks setup guide in UTMStack, showing How it works and the Enable this integration remotely panel with the Collector, Protocol and Port fields

    A different number typed in Port does not change the port the Collector listens on; see Use a different port below.

  2. 2

    Choose the Collector and protocol

    Under Enable this integration remotely, select the Collector and the Protocol (UDP, TCP or TLS). Leave Port at the default it fills in.

  3. 3

    Enable it

    Click Enable integration. The panel then shows, for example, Currently: enabled · udp · port 7006.

To do the same on the Collector host instead, run:

sudo /opt/utmstack-forwarder/utmstack_forwarder enable-integration firewall-paloalto udp

The command prints the port the Collector really listens on, for example Integration "firewall-paloalto" enabled on udp port 7006.

To use TLS, load a certificate on the Collector first. See UTMStack Forwarder.

Use a different port

For built-in integrations, the Collector always listens on the port saved on the Collector host. That is the default port unless you change it there. A different number typed in Port, or on the enable-integration command line, is not used. To use another port:

  1. On the Collector host, change the saved port, for example:

    sudo /opt/utmstack-forwarder/utmstack_forwarder change-port firewall-paloalto tcp 7106

    Use udp instead of tcp for UDP.

  2. In the Palo Alto card, type the same port in Port when you enable the integration. If it is already enabled, click Disable integration first, then enable it again with the new port. The panel shows the port you type there, not a value read from the Collector, so typing the same port keeps the two in step.

  3. Use the new port in the syslog server profile in step 2.

Step 2: Configure PAN-OS to forward logs

  1. 1

    Create a Syslog Server Profile

    In PAN-OS, go to Device > Server Profiles > Syslog and add a profile. Add a server with the address of the Collector host, transport UDP (or TCP or SSL, matching what you enabled in step 1), port 7006 and format BSD. Leave the Custom Log Format tab empty, so PAN-OS sends its default CSV format.

  2. 2

    Create a Log Forwarding profile

    Go to Objects > Log Forwarding and create a profile that sends Traffic, Threat and the other log types you want to the syslog profile above.

  3. 3

    Attach it to your security rules

    Attach the Log Forwarding profile to your Security policy rules (Policies > Security > rule > Actions > Log Forwarding).

  4. 4

    Forward system and configuration logs (optional)

    To also send System and Configuration logs, go to Device > Log Settings and add the syslog profile to those log types.

  5. 5

    Commit

    Click Commit.

The setup guide in UTMStack fills in your UTMStack server's address in this step. Keep it only if the Collector runs on the UTMStack server; otherwise use the address of the Collector host.

For SSL (TLS), the firewall must trust the certificate loaded on the Collector. See Palo Alto Networks' documentation on syslog over SSL for your PAN-OS version.

Step 3: Check that logs arrive

  1. 1

    Open the logs

    In the Palo Alto drawer, click View logs. Log Explorer opens with the firewall-paloalto data type for the last 24 hours. You can also open Log Explorer, keep the data set logs and choose firewall-paloalto as the data type.

  2. 2

    Check the parsed fields

    Expand an event. Parsed events have standard fields such as origin.ip, target.ip, target.port and action, and Palo Alto fields under log., such as log.paFormat (CSV or CEF). The event should have no errors.

  3. 3

    Check the data source

    Within about 20 minutes, the firewall appears on the Data Sources page under Direct, named after the address its logs come from.

To list the latest events and any processing errors, switch Log Explorer to SQL mode and run:

SELECT `@timestamp`, dataSource, errors, raw
FROM logs
WHERE dataType = 'firewall-paloalto'
  AND `@timestamp` > now() - INTERVAL 1 HOUR
ORDER BY `@timestamp` DESC
LIMIT 20

Troubleshooting

SymptomLikely causeWhat to do
Nothing arrivesThe Collector is offline, the configuration was not committed, or the firewall sends to the wrong address, port or transport, or a firewall blocks the port.Check that the Collector shows as online in the Collector list, that the change is committed, and that the Collector host allows the port in. See Forwarder Troubleshooting.
Nothing arrives, and the Forwarder guide filled in the UTMStack server's addressThe firewall sends to the UTMStack server, but the Collector runs on another host.Use the Collector host's address in the syslog server profile.
Only some traffic arrivesSome Security policy rules have no Log Forwarding profile, or logging at session end is off.Attach the Log Forwarding profile to every rule you care about.
Events keep only log.paFormat and log.paVsys, and errors contains column index out of rangeThe log line does not have the column layout of the default PAN-OS format, for example because of a custom log format, or because a long line was cut off over UDP.Clear the Custom Log Format tab of the syslog profile, and send over TCP or TLS so long lines arrive whole.
Long Threat or URL lines are cut offOver UDP, the Collector reads at most 2,048 bytes of each message.Send over TCP or SSL.
Palo Alto logs appear under another data typeThe firewall sends to the port of a different integration.Send to the port that the Palo Alto integration listens on.

Stop collecting

In the Palo Alto card, select the same Collector and click Disable integration, or run on the Collector host, with the protocol you enabled (udp, tcp or tls):

sudo /opt/utmstack-forwarder/utmstack_forwarder disable-integration firewall-paloalto udp

Then remove the syslog profile from your Log Forwarding profiles and log settings, and commit.