Configure Log Forwarding from Panorama to External Destinations
Table of Contents
10.0 (EoL)
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy Mode
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on Alibaba Cloud
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on Hyper-V
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Oracle Cloud Infrastructure (OCI)
- Mount the Panorama ESXi Server to an NFS Datastore
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on Alibaba Cloud
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on Hyper-V
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Oracle Cloud Infrastructure (OCI)
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
-
- Panorama, Log Collector, Firewall, and WildFire Version Compatibility
- Install Updates for Panorama in an HA Configuration
- Install Updates for Panorama with an Internet Connection
- Install Updates for Panorama When Not Internet-Connected
- Install Updates Automatically for Panorama without an Internet Connection
- Migrate Panorama Logs to the New Log Format
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
-
- Add a Firewall as a Managed Device
-
- Add a Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute Data to Managed Firewalls
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- View Log Query Jobs
- Troubleshoot Commit Failures
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Downgrade from Panorama 10.0
End-of-Life (EoL)
Configure Log Forwarding from Panorama to External Destinations
Panorama enables you to forward logs to external
services, including syslog, email, SNMP trap, and HTTP-based services.
Using an external service enables you to receive alerts for important
events, archive monitored information on systems with dedicated
long-term storage, and integrate with third-party security monitoring tools.
In addition to forwarding firewall logs, you can forward the logs
that the Panorama management server and Log Collectors generate.
The Panorama management server or Log Collector that forwards the
logs converts them to a format that is appropriate for the destination
(syslog message, email notification, SNMP trap, or HTTP payload).
Forwarded logs have a maximum log record size of 4,096 bytes. A forwarded
log with a log record size larger than the maximum is truncated
at 4,096 bytes while logs that do not exceed the maximum log record
size are not.
Log forwarding is supported
only for supported log fields. Forwarding
logs that contain unsupported log fields or pseudo-fields causes
the firewall to crash.
If your Panorama management
server is a Panorama virtual appliance in Legacy mode, it converts
and forwards logs to external services without using Log Collectors.
You
can also forward logs directly from firewalls to external services:
see Log
Forwarding Options.
On a Panorama virtual appliance
running Panorama 5.1 or earlier releases, 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 Panorama virtual appliance. A Panorama virtual appliance
running Panorama 6.0 or later releases, and M-Series appliances running
any release, do not support these options because the log database
on those models is too large for an export or import to be practical.
To
forward logs to external services, start by configuring the firewalls
to forward logs to Panorama. Then you must configure the server
profiles that define how Panorama and Log Collectors connect to
the services. Lastly, you assign the server profiles to the log
settings of Panorama and to Collector Groups.
- Configure the firewalls to forward logs to Panorama.
- Configure a server profile for each external service
that will receive log information.
- Select PanoramaServer Profiles and select the type of server that will receive the log data: SNMP Trap, Syslog, Email, or HTTP.
- Configure the server profile:
- Configure an SNMP Trap server profile. For details on how SNMP works for Panorama and Log Collectors, refer to SNMP Support.
- Configure a Syslog server profile. If the syslog server requires client authentication, use the PanoramaCertificate ManagementCertificates page to create a certificate for securing syslog communication over SSL.
- Configure destinations for:
- Logs that the Panorama management server and Log Collectors generate.
- Firewall logs that a Panorama virtual appliance in Legacy mode collects.
- Select PanoramaLog Settings.
- Add one
or more match list profiles for each log type.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 AttributeOperator to define inclusion or exclusion logicAttribute Value for the query to match
- Add the server profiles you configured for each external service.
- Click OK to save the profile.
- Configure destinations for firewall logs that Log Collectors
receive.Each Collector Group can forward logs to different destinations. If the Log Collectors are local to a high availability (HA) pair of Panorama management servers, you must log into each HA peer to configure log forwarding for its Collector Group.
- Select PanoramaCollector Groups and edit the Collector Group that receives the firewall logs.
- (Optional, SNMP trap forwarding only) Select Monitoring and configure the SNMP settings.
- Select Collector Log Forwarding and Add configured match list profiles as necessary.
- Click OK to save your changes to the Collector Group.
- (Syslog forwarding only) If the syslog server
requires client authentication and the firewalls forward logs to
Dedicated Log Collectors, assign a certificate that secures syslog
communication over SSL.Perform the following steps for each Dedicated Log Collector:
- Select PanoramaManaged Collectors and edit the Log Collector.
- Select the Certificate for Secure Syslog and click OK.
- (SNMP trap forwarding only) Enable your SNMP
manager to interpret traps.Load the Supported MIBs and, if necessary, compile them. For the specific steps, refer to the documentation of your SNMP manager.
- Commit and verify your configuration changes.
- Select CommitCommit and Push to commit your changes to Panorama and push the changes to device groups, templates, and Collector Groups.
- Verify that the external services are receiving the
log information:
- 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’s receiving logs as syslog messages.
- SNMP manager—Refer to the documentation for your SNMP trap server to verify it’s receiving logs as SNMP traps.
- HTTP server—Verify that the HTTP-based server is receiving logs in the correct payload format.