Forward Logs from Strata Logging Service
Focus
Focus
Strata Logging Service

Forward Logs from Strata Logging Service

Table of Contents

Forward Logs from Strata Logging Service

Learn how to forward logs from Strata Logging Service to an external destination.
Where Can I Use This?What Do I Need?
  • Prisma Access (Managed by Strata Cloud Manager)
  • Prisma Access (Managed by Panorama)
  • NGFW (Managed by PAN-OS or Panorama)
  • NGFW (Managed by Strata Cloud Manager)
  • Strata Logging Service
  • You must have at least one of these licenses to use Strata Cloud Manager:Prisma Access, AIOps for NGFW Premium, Prisma SD-WAN
To meet your organization's legal compliance requirements and operational needs, you can forward firewall logs stored in Strata Logging Service to external destinations. For example, you can forward logs using syslog to a SIEM for long term storage, SOC, or internal audit obligations, and forward email notifications for critical events to an email address. You can forward logs to the following SIEMs:
  • Exabeam
  • Google Chronicle
  • Microsoft Sentinel
  • Splunk HTTP Event Collector (HEC)
Strata Logging Service can forward logs in multiple formats: CSV, LEEF, CEF, JSON, or PARQUET. For each instance of Strata Logging Service, you can forward logs to up to 200 syslog destinations. Use the following table to find more information about supported log formats.
Log FormatWhere to find more information about the logs:IETF StandardDefault Field Delimiter
CSVLog Forwarding Schema ReferenceRFC 5425,
LEEF RFC 5425<tab>
CEF RFC 5425<space>
The Strata Logging Service ensures secure communication with log receivers through the following mechanisms:
  • TLS 1.2 Encryption: All communications are encrypted using TLS 1.2, ensuring data security during transmission.
  • Java 8 default cipher suites: The service uses Java 8 default cipher suites, with the exception of GCM ciphers, which are not currently supported.
  • Certificate Validation: To establish a secure connection, the Strata Logging Service requires that the log receiver provides a valid certificate.
    • Trusted Certification: The receiver's certificate must be signed by a trusted root CA or a private CA.
    • Chain of Trust: The receiver must present all certificates in the chain of trust to successfully complete the TLS handshake and establish the connection.