Configure Log Forwarding
In an environment where you use multiple firewalls to control and analyze network traffic, any single firewall can display logs and reports only for the traffic it monitors. Because logging in to multiple firewalls can make monitoring a cumbersome task, you can more efficiently achieve global visibility into network activity by forwarding the logs from all firewalls to Panorama or external services. If you Use External Services for Monitoring , the firewall automatically converts the logs to the necessary format: syslog messages, SNMP traps, email notifications, or as an HTTP payload to send the log details to an HTTP(S) server. In cases where some teams in your organization can achieve greater efficiency by monitoring only the logs that are relevant to their operations, you can create forwarding filters based on any log attributes (such as threat type or source user). For example, a security operations analyst who investigates malware attacks might be interested only in Threat logs with the type attribute set to wildfire-virus.
You can forward logs from the firewalls directly to external services or from the firewalls to Panorama and then configure Panorama to forward logs to the servers . Refer to Log Forwarding Options for the factors to consider when deciding where to forward logs.
You can use Secure Copy (SCP) commands from the CLI to export the entire log database to an SCP server and import it to another firewall. Because the log database is too large for an export or import to be practical on the PA-7000 Series firewall, it does not support these options. You can also use the web interface on all platforms to View and Manage Reports , but only on a per log type basis, not for the entire log database.
- 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 ).
a Log Forwarding profile.The profile defines the destinations for Traffic, Threat, WildFire Submission, URL Filtering, Data Filtering, Tunnel and Authentication logs.
- Select ObjectsLog Forwarding and Add a profile.
- 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.
- 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:
- Enter a Name to identify the profile.
- Select the Log Type.
- 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
- Select Panorama if you want to forward logs to Log Collectors or the Panorama management server.
- For each type of external service that you use for monitoring (SNMP, Email, Syslog, and HTTP), Add one or more server profiles.
- Click OK to save the Log Forwarding profile.
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:
- Select PoliciesSecurity and edit the rule.
- Select Actions and select the Log Forwarding profile you created.
- Set the Profile Type to Profiles or Group,
and then select the security profiles
Profile required to trigger log generation and forwarding
- 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.
- For Traffic logs, select Log At Session Start and/or Log At Session End.
- Click OK to save the rule.
the destinations for System, Configuration, User-ID, HIP Match,
and Correlation logs.Panorama generates Correlation logs based on the firewall logs it receives, rather than aggregating Correlation logs from firewalls.
- Select DeviceLog Settings.
- For each log type that the firewall will forward, see Step Add one or more match list profiles.
- (PA-7000 Series firewalls only) Configure a
log card interface to perform log forwarding.
- Select NetworkInterfacesEthernet and click Add Interface.
- Select the Slot and Interface Name.
- Set the Interface Type to Log Card.
- Enter the IP Address, Default Gateway, and (for IPv4 only) Netmask.
- 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).
- Click OK to save your changes.
- Commit and verify your changes.
- Commit your changes.
- Verify the log destinations you configured are receiving
- 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 .