End-of-Life (EoL)
Configure Log Forwarding
To use Panorama or Use External Services for Monitoring the firewall,
you must configure the firewall to forward its logs. Before forwarding
to external services, the firewall automatically converts the logs
to the necessary format: syslog messages, SNMP traps, or email notifications.
Before starting this procedure, ensure that Panorama or the external
server that will receive the log data is already set up.
The
PA-7000 Series firewall can’t forward logs to Panorama, only to
external services. However, when you use Panorama to monitor logs or
generate reports for a device group that includes a PA-7000 Series
firewall, Panorama queries the PA-7000 Series firewall in real-time
to display its log data.
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 Manage Reporting, but only
on a per log type basis, not the entire log database.
- Configure a server profile for each external service that will receive log data.You can use separate profiles to send each log type to a different server. To increase availability, define multiple servers in a single profile.
- 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.
- Configure a Syslog server profile. If the syslog server requires client authentication, you must also Create a certificate to secure syslog communication over SSL.
- Create a log forwarding profile.The profile defines the destinations for Traffic, Threat, and WildFire Submission logs. (Threat logs include URL Filtering and Data Filtering logs.)
- Selectand clickObjectsLog ForwardingAdd.
- Enter aNameto identify the profile. If you want the firewall to automatically assign the profile to new security rules and zones, enterdefault. If you don’t want a default profile, or you want to override an existing default profile, enter aNamethat will help you identify the profile when assigning it to security rules and zones.If no log forwarding profile nameddefaultexists, the profile selection is set toNoneby default in new security rules (Log Forwardingfield) and new security zones (Log Settingfield), although you can change the selection.
- Perform the following steps for each log type and each severity level or WildFire verdict:
- Select thePanoramacheck box if you want to aggregate firewall logs on Panorama. (You can then configure Panorama to forward the logs to external services.)
- Select theSNMP Trap,Email, orSyslogserver profile you configured for this log type, and clickOK.
- Assign the log forwarding profile to security rules.To trigger log generation and forwarding, the rules require certain Security Profiles according to log type:
- Traffic logs—No security profile is necessary; the traffic only needs to match a specific security rule.
- Threat logs—The traffic must match any security profile assigned to a security rule.
- WildFire logs—The traffic must match a WildFire Analysis profile assigned to a security rule.
Perform the following steps for each rule that will trigger log forwarding:- Selectand click the rule.PoliciesSecurity
- Select theActionstab and select theLog Forwardingprofile you just created.
- In theProfile Typedrop-down, selectProfilesorGroup, and then select the security profiles orGroup Profilerequired to trigger log generation and forwarding.
- For Traffic logs, select one or both of theLog At Session StartandLog At Session Endcheck boxes, and clickOK.
- Configure the destinations for System, Config, HIP Match, and Correlation logs.
- Select.DeviceLog Settings
- Perform the following steps for each log type. For System and Correlation logs, start by clicking the Severity level. For Config and HIP Match logs, start by editing the section.
- Select thePanoramacheck box if you want to aggregate System, Config, and HIP Match logs on Panorama. Optionally, you can then configure Panorama to forward the logs to the external services.Panorama generates Correlation logs based on the firewall logs it receives, rather than aggregating Correlation logs from firewalls.
- Select theSNMP Trap,Email, orSyslogserver profile you configured for this log type and clickOK.
- (PA-7000 Series firewalls only) Configure a log card interface to perform log forwarding.
- Selectand clickNetworkInterfacesEthernetAdd Interface.
- Select theSlotandInterface Name.
- For theInterface Type, selectLog Card.
- Enter theIP Address,Default Gateway, and (for IPv4 only)Netmask.
- SelectAdvancedand specify theLink Speed,Link Duplex, andLink State.These fields default toauto, which specifies that the firewall automatically determines the values based on the connection. However, the minimum recommendedLink Speedfor any connection is1000(Mbps).
- ClickOKto save your changes.
- Commit and verify your changes.
- ClickCommitto complete the log forwarding configuration.
- Verify the log destinations you configured are receiving firewall logs:
- Panorama—If the firewall forwards logs 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 the documentation for your syslog server to verify it is receiving logs as syslog messages.
- SNMP manager—Use an SNMP Manager to Explore MIBs and Objects to verify it is receiving logs as SNMP traps.
Recommended For You
Recommended Videos
Recommended videos not found.