Forward Logs from Cortex Data Lake to a Syslog Server

Learn how forward logs from Cortex Data Lake to a Syslog server.
To meet your long term storage, reporting and monitoring, or legal and compliance needs, you can configure the Cortex Data Lake to forward all logs or a subset of logs to a Syslog receiver.
By default, Cortex Data Lake forwards logs in CSV format and follows IETF Syslog message format defined in RFC 5425. However, you can select other log record formats, such as LEEF, that may adhere to different standards.
For each instance of Cortex Data Lake, you can forward logs to ten Syslog destinations.
The communication between Cortex Data Lake and the Syslog destination uses Syslog over TLS, and upon connection Cortex Data Lake validates that the Syslog receiver has a certificate signed by a trusted root CA. To complete the SSL handshake and establish the connection, the Syslog receiver must present all the certificates from the chain of trust.
Cortex Data Lake does not support self-signed certificates.
  1. Enable communication between Cortex Data Lake and your Syslog receiver. 
    Ensure that your Syslog receiver can connect to Cortex Data Lake and can present a valid CA certificate to complete the connection request.
    • Allow an inbound TLS feed to your Syslog receiver from the following IP address ranges:
        New (December 2019)
        New (December 2019)
      SG (Singapore)
      CA (Canada)
      JP (Japan)
      If you have allowed specific IP addresses for inbound traffic, you must also allow the above IP address ranges to forward logs to your Syslog receiver.
    • Obtain a certificate from a well-known, public CA, and install it on your Syslog receiver.
      Because Cortex Data Lake validates the server certificate to establish a connection, you must verify that the Syslog receiver is configured to properly send the SSL certificate chain to Cortex Data Lake. If the app cannot verify that the certificate of the receiver and all CA's in the chain are trustworthy, the connection cannot be established. See the list of trusted certificates.
  2. Sign In
    to the hub at
  3. Select the Cortex Data Lake instance that you want to configure for Syslog forwarding.
    If you have multiple Cortex Data Lake instances, click the Cortex Data Lake tile and select an instance from the list of those available.
  4. Select
    Log Forwarding
    to add a new Syslog forwarding profile.
  5. Enter a descriptive
    for the profile.
  6. Enter the
    Syslog Server
    IPv4 address or FQDN.
  7. Enter the
    on which the Syslog server is listening.
    The default port for Syslog messages over TLS is 6514.
  8. Select the
    Choose one of the Syslog standard values. The value maps to how your Syslog server uses the facility field to manage messages. For details on the facility field, see the IETF standard for the log format that you will choose in the next step.
  9. Specify the
    in which you would like to forward your logs.
    The log format that you should select depends on the destination of your log data. For example, select LEEF if you are forwarding logs to IBM QRadar SIEM.
  10. Specify the
    that you would like to separate the fields in your log messages.
  11. (
    ) To receive a
    Status Notification
    when Cortex Data Lake is unable to connect to the Syslog server, enter the email address at which you’d like to receive the notification.
    These notifications describe the error impacting communication between Cortex Data Lake and the Syslog server, so that you can take the appropriate steps to restore Syslog connectivity.
  12. (
    ) Enter a
    Profile Token
    to send logs to a cloud Syslog receiver.
    If you use a third-party cloud-based Syslog service, you can enter a token that Cortex Data Lake inserts into the Syslog message so that the cloud Syslog provider can identify the source of the logs.
    1. Follow your cloud Syslog provider’s instructions for generating an identifying token.
    2. Enter the
      Profile Token
      Tokens have a maximum length of 128 characters.
  13. Select the logs you want to forward.
    1. Add
      a new log filter.
    2. Select the log type.
      The Threat log type does not include URL logs or Data logs. If you wish to forward these log types, you must add them individually.
    3. (Optional)
      Create a log filter to forward only the logs that are most critical to you.
      Log filters function like queries in Explore. As such, you can either write your own queries from scratch or use the query builder. Also, selecting the query field presents some common predefined queries that you can use.
      If you want to forward all logs of the type you selected, do not enter a query. Instead, proceed to the next step.
    4. Save
      your changes.
  14. Save
    your changes.
  15. Verify that the
    of your Syslog forwarding profile is
    ( healthy.PNG ).
  16. Verify that you can view logs on the Syslog receiver.
    For details about the log format, refer to the Syslog field descriptions (Select the PAN-OS Administrator’s Guide for your firewall version).

Recommended For You