Learn how to ingest detection data from Next-Generation Firewall and Panorama.
You can forward firewall data from your Next-Generation Firewall (NGFW) and Panorama devices to Cortex XDR.
Prerequisites
Ensure that you have completed the following on the NGFW or Panorama side:
For Panorama only, ensure that the Panorama Cloud Services plugin is installed.
Enable log forwarding profiles on firewall rules.
Configuration of data ingestion from multiple accounts requires Super User permissions on both the Cortex XDR tenant and on the device accounts.
On the Cortex XDR side, ensure that you have user role permissions for Data Collection > Log Collections .
Note
Ingesting logs from Next-Generation Firewall requires a Cortex XDR Pro per GB license.
Note
In the following procedure, general information is provided for NGFW and Panorama. For detailed instructions, consult the documentation for your specific devices and Panorama version.
Set up detection data ingestion
In the user interface for setting up firewalls, for Strata Logging Service/Cloud Logging, enable the following options directly, or using device templates.
(For example, go to → → → section)
Select Enable Strata Logging Service.
Select Enable Enhanced Application Logging.
(Optional, depending on your organization's requirements) Select Enable Duplicate Logging (Cloud and On-Premise).
Depending on your PAN-OS or Panorama version, generate either a certificate or PSK.
For PAN-OS and Panorama versions 10.1 and later, each firewall requires a separate certificate. Certificates need to be requested through the Customer Support portal. To sign in to the portal, click here. For PAN-OS and Panorama versions 10.0 and earlier, you are only required to generate one global PSK for all the firewall devices.
Note
Cortex XDR does not validate your firewall credentials, you must ensure the certificates or PSK details have been updated in your firewalls in order for data to stream.
Onboard the certificates.
Define a Log Forwarding profile.
Map the Log Forwarding profile to a Security Policy Rule.
Verify that the connection between the firewalls and Strata Logging Service is valid.
Push the configuration changes to the firewalls.
In Cortex XDR, select → → → .
On the Collection Integrations page, locate your NGFW data source and select Add Instance to begin a new connection.
Select Add NGFW Device or Add Panorama Device.
A list of all available devices allocated to your account is displayed. To include devices from other accounts, select Select devices from other accounts. For cross-account connections, you must have Super User permissions on the Cortex tenant account and the device account.
Devices already connected are listed at the end. A device may be connected via Strata Logging Service, or via Cortex XDR. Depending on the type of connection, you can rectify any streaming issues that may arise.
Connect to establish the instance.
Connection is established regardless of the firewall credential status and can take up to several minutes, select Sync now to refresh your instances.
Validate that your data is streaming. It might be necessary to create traffic before you verify data streaming.
To ensure the data is streaming into your tenant:
In your NGFW Standalone Firewall Devices, track the Last communication timestamp.
Run XQL Query: dataset = panw_ngfw_system_raw| filter log_source_id = "[NGFW device SN]"
(Optional) Manage your Instance.
After you create the NGFW instance, on the Collection Integrations page, expand the NGFW to track the status of your Standalone Firewall Devices and Panorama Devices.
Select the ellipses to Request Certificate, if required, or Delete the instance.
Note
It might take an hour or longer after connecting the firewall in Cortex XDR until you start seeing notifications that the certificate has been approved, and that the logging service license has appeared on the firewall.
As soon as Cortex XDR begins receiving detection data, the console begins stitching logs with other Palo Alto Network-generated logs to form stories. Use the XQL Search dataset panw_ngfw_*_raw to query your data, where the following logs are supported:
Authentication Logs—panw_ngfw_auth_raw
File Data Logs—panw_ngfw_filedata_raw
Global Protect Logs—panw_ngfw_globalprotect_raw
Hipmatch Logs—panw_ngfw_hipmatch_raw*
System Logs—panw_ngfw_system_raw
Threat Logs—panw_ngfw_threat_raw*
Traffic Logs—panw_ngfw_traffic_raw*
URL Logs—panw_ngfw_url_raw*
User ID Logs—panw_ngfw_userid_raw
*These datasets use the query field names as described in the Cortex schema documentation.
For stitched raw data, you can query the xdr_data dataset or use any preset designated for stitched data, such as network_story. For query examples, refer to the in-app XQL Library. When relevant, Cortex XDR can also raise Cortex XDR alerts (Analytics, Correlation Rules, IOC, and BIOC only) from Strata Logging Service detection data. While Correlation Rules alerts are raised on non-normalized and normalized logs, Analytics, IOC, and BIOC alerts are only raised on normalized logs.
Note
IOC and BIOC alerts are applicable on stitched data only and are not available on raw data.
Tip
You can see an overview of ingestion status for all log types, and a breakdown of each log type and its daily consumption quota on the NGFW Ingestion Dashboard.