Configure Log Forwarding

1. Configure a server profile for each external service that will receive log information.
   You can use separate profiles to send different sets of logs, filtered by log attributes, to a different server. To increase availability, define multiple servers in a single profile.

   Configure one or more of the following server profiles:

   • Create an Email server profile.
   • Step Configure an SNMP Trap server profile. To enable the SNMP manager (trap server) to interpret firewall traps, you must load the Palo Alto Networks Supported MIBs into the SNMP manager and, if necessary, compile them. For details, refer to your SNMP management software documentation.
   • If the syslog server requires client authentication, you must also Create a certificate to secure syslog communication over TLSv1.2.
   • Configure an HTTP server profile (see Forward Logs to an HTTP/S Destination).
     Log forwarding to an HTTP server is designed for log forwarding at low frequencies and is not recommend for deployments with a high volume of log forwarding. You may experience log loss when forwarding to an HTTP server if your deployment generate a high volume of logs that need to be forwarded.
2. Create a Log Forwarding profile.
   The profile defines the destinations for Traffic, Threat, WildFire Submission, URL Filtering, Data Filtering, Tunnel and Authentication logs.
   1. Select ObjectsLog Forwarding and Add a profile.
   2. Enter a Name to identify the profile.
      If you want the firewall to automatically assign the profile to new security rules and zones, enter default. If you don’t want a default profile, or you want to override an existing default profile, enter a Name that will help you identify the profile when assigning it to security rules and zones.

      If no log forwarding profile named default exists, the profile selection is set to None by default in new security rules (Log Forwarding field) and new security zones (Log Setting field), although you can change the selection.
   3. Add one or more match list profiles.
      The profiles specify log query filters, forwarding destinations, and automatic actions such as tagging. For each match list profile:

      1. Enter a Name to identify the profile.
      2. Select the Log Type.
      3. In the Filter drop-down, select Filter Builder. Specify the following and then Add each query:
         • Connector logic (and/or)
         • Log Attribute
         • Operator to define inclusion or exclusion logic
         • Attribute Value for the query to match
      4. Select Panorama if you want to forward logs to Log Collectors or the Panorama management server.
      5. For each type of external service that you use for monitoring (SNMP, Email, Syslog, and HTTP), Add one or more server profiles.
   4. Click OK to save the Log Forwarding profile.
3. Assign the Log Forwarding profile to policy rules and network zones.
   Security, Authentication, and DoS Protection rules support log forwarding. In this example, you assign the profile to a Security rule.

   Perform the following steps for each rule that you want to trigger log forwarding:
   1. Select PoliciesSecurity and edit the rule.
   2. Select Actions and select the Log Forwarding profile you created.
   3. Set the Profile Type to Profiles or Group, and then select the security profiles or Group Profile required to trigger log generation and forwarding for:
      • Threat logs—Traffic must match any security profile assigned to the rule.
      • WildFire Submission logs—Traffic must match a WildFire Analysis profile assigned to the rule.
   4. For Traffic logs, select Log At Session Start and/or Log At Session End.
      Log At Session Start consumes more resources than logging only at the session end. In most cases, you only Log At Session End. Enable both Log At Session Start and Log At Session End only for troubleshooting, for long-lived tunnel sessions such as GRE tunnels (you can't see these sessions in the ACC unless you log at the start of the session), and to gain visibility into Operational Technology/Industrial Control Systems (OT/ICS) sessions, which are also long-lived sessions.
   5. Click OK to save the rule.
4. Configure the destinations for System, Configuration, Correlation, GlobalProtect, HIP Match, and User-ID logs.
   Panorama generates Correlation logs based on the firewall logs it receives, rather than aggregating Correlation logs from firewalls.
   1. Select DeviceLog Settings.
   2. For each log type that the firewall will forward, see Step Add one or more match list profiles.
5. (PA-7000 Series firewalls only) Configure a log card interface to perform log forwarding.
   1. Select NetworkInterfacesEthernet and click Add Interface.
   2. Select the Slot and Interface Name.
   3. Set the Interface Type to Log Card.
   4. Enter the IP Address, Default Gateway, and (for IPv4 only) Netmask.
   5. Select Advanced and specify the Link Speed, Link Duplex, and Link State.
      These fields default to auto, which specifies that the firewall automatically determines the values based on the connection. However, the minimum recommended Link Speed for any connection is 1000 (Mbps).
   6. Click OK to save your changes.
6. Commit and verify your changes.
   1. Commit your changes.
   2. Verify the log destinations you configured are receiving firewall logs:
      • Panorama—If the firewall forwards logs to a Panorama virtual appliance in Panorama mode or to an M-Series appliance, you must configure a Collector Group before Panorama will receive the logs. You can then verify log forwarding.
      • Email server—Verify that the specified recipients are receiving logs as email notifications.
      • Syslog server—Refer to your syslog server documentation to verify it’s receiving logs as syslog messages.
      • SNMP manager—Use an SNMP Manager to Explore MIBs and Objects to verify it’s receiving logs as SNMP traps.
      • HTTP server—Forward Logs to an HTTP(S) Destination.