Forward Logs to Cortex Data Lake

After you activate Cortex Data Lake, you can configure firewalls to start forwarding logs. This includes enabling the firewalls to communicate with Cortex Data Lake, and specifying the log types that you want to send.
The steps here describe how to start forwarding logs from firewalls that are not managed by Panorama. This direct onboarding to Cortex Data Lake—where you can provision the certificates firewalls require to connect to Cortex Data Lake without using Panorama—is supported for firewalls running PAN-OS 9.0.3 and later. When you activated Cortex Data Lake, you should have also generated a key that you’ll now use to authenticate the firewall to Cortex Data Lake. If you haven’t generated this key yet, do this now on the hub, and then come back to these steps.
If you’re using Panorama, Traps, or GlobalProtect cloud service:
  1. If you haven’t done so already, Activate Cortex Data Lake.
    Onboarding includes activating Cortex Data Lake, and generating the key that enables the firewall to securely connect to Cortex Data Lake. You’ll need to use the key in the coming steps.
    After you’ve activated Cortex Data Lake, log in to the firewall to continue.
  2. Select
    and confirm that the Logging Service (now called Cortex Data Lake) license is active.
    When you purchased Cortex Data Lake, all firewalls registered to your support account received a Cortex Data Lake license. If you don’t see the Logging Service license, select
    Retrieve license keys from license server
    to manually refresh the firewall licenses.
  3. Enable Cortex Data lake on the firewall.
    1. Select
      and find the
      Logging Service
      settings (Cortex Data Lake used to be called the Logging Service).
    2. Enable Logging Service
      to allow the firewall to send and store logs in Cortex Data Lake.
      Note that logging to Cortex Data Lake only begins after you set up Log Forwarding, which you’ll do in the coming steps.
      Do not select the option to
      Enable Duplicate Logging
      . This option applies only to Panorama-managed firewalls (in this case, you can choose if you’d like Panorama to also store firewall logs, in addition to Cortex Data Lake).
    3. Enable Enhanced Application Logging
      if you want the firewall to collect data that increases network visbility for Palo Alto Networks cloud applications, like Cortex XDR. Enhanced application logging will take effect after you set up log forwarding.
    4. Select the geographic
      of the Cortex Data Lake instance to which you’ll be forwarding logs. This is the region you chose when you were activating the Cortex Data Lake (either Europe or Americas).
    5. To
      Onboard Without Panorama
      , select
      and enter the
      you generated in the Cortex Data Lake app. Then, click
    6. Show Status
      to check
      Logging Service Status
      (Cortex Data Lake). All status indicators—License, Certificate, Customer Info, and Device Connectivity—should show as green.
  4. On the firewall, configure NTP so that the firewall can stay in sync with the Cortex Data Lake.
    On the firewall, select
    and set it to the same
    NTP Server Address
    you configured on Panorama, for example
  5. (Optional)
    If you do not want to use the management interface to forward logs to the Cortex Data Lake, enable the firewall to send traffic through a different interface.
    Beginning with content release version 8067, you can use the paloalto-shared-services and paloalto-logging-service App-IDs to safely enable traffic between the firewalls and the Cortex Data Lake. You will also need to create a security policy rule to allow this traffic on any firewalls between the firewalls sending the logs and the internet. If the upstream firewalls are not Palo Alto Networks firewalls, you must enable access to the TCP Ports and FQDNs Required for Cortex Data Lake. Keep in mind that the firewalls and the Cortex Data Lake use mutual certificate authentication and therefore cannot be decrypted and you cannot connect through a proxy server.
    1. Configure a service route for Palo Alto Networks Services.
    2. Create a security policy rule that enables the firewalls to communicate with the Cortex Data Lake.
      This is required if you are using the Palo Alto Networks Services service route instead of the management interface to forward logs to the Cortex Data Lake. To create this rule, set the
      (requires content release version 8066 or later) and
      (requires content release version 8033 or later). The paloalto-shared-services covers the common traffic for different Palo Alto Networks services and is a dependency for the paloalto-logging-service.
      Make sure you place this rule above any rule that allows the web-browsing and SSL traffic to the internet. In addition, if you have a firewall between Panorama and the internet, you must also add a rule that allows paloalto-shared-services and paloalto-logging service traffic on that firewall. The paloalto-logging-service app enables the firewalls and Panorama to connect to the Cortex Data Lake on ports 444 and 3978, the defaults ports for this communication.
      If that firewall is not a Palo Alto Networks firewall, create a security policy rule on that firewall that allows outbound SSL traffic to the internet to allow the TCP Ports and FQDNs Required for Cortex Data Lake so that the internet gateway firewall does not block traffic between Panorama and the Cortex Data Lake.
      The firewalls and Panorama need access to the domain 8.0.0 on port 3978 in order to forward logs to the Cortex Data Lake. This is true even if you are using the paloalto-logging-service App-ID to safely enable Cortex Data Lake traffic.
  6. Specify the log types to forward to the Cortex Data Lake.
    The way you enable forwarding depends on the log type. For logs that are generated based on a policy match, use a log forwarding profile within a device group. For other log types, use the Log Settings configuration within a template.
    1. To configure forwarding of System, Configuration, User-ID, and HIP Match logs:
      1. Select
        Log Settings
      2. For each log type that you to forward to the Cortex Data Lake,
        a match list filter. Give it a
        , optionally define a
        , select the
        Logging Service
        check box, and click
    2. To configure forwarding of all other log types that are generated when a policy match occurs—Traffic, Threat, WildFire Submission, URL Filtering, Data Filtering, and Authentication logs—create and attach a Log Forwarding profile to each policy rule for which you want to forward logs.
      1. Select
        Log Forwarding
        a profile. In the log forwarding profile match list, add each log type that you want to forward.
        If you have already turned on Enhanced Application Logs, fully enable the firewall to forward these log types by selecting
        Enable enhanced application logging to Cortex Data Lake
        . Notice that when you select this option, match lists that specify the logs types required for enhanced application logging are automatically added to the profile.
      2. Select
        Logging Service
        as the Forward Method to enable the firewalls in the device group to forward the logs to the Cortex Data Lake. You will be able to monitor the logs and generate reports from Panorama.
      3. If you haven’t already done so, Create basic security policy rules now.
        Until the firewall has interfaces and zones and a basic security policy, it will not let any traffic through, and only traffic that matches a security policy rule will be logged (by default).
      4. For each rule you create, select
        and select the Log Forwarding profile that allows the firewall to send logs to the Cortex Data Lake.
  7. Commit
    your changes.
  8. Verify that the firewall logs are being forwarded to the Cortex Data Lake.
    • Log in to Explore, available in the Cortex hub, to view and filter Cortex Data Lake logs.
    • On a firewall, enter the CLI command
      show logging-status
      ----------------------------------------------------------------------------------------------------------------------------- Type Last Log Created Last Log Fwded Last Seq Num Fwded Last Seq Num Acked Total Logs Fwded ----------------------------------------------------------------------------------------------------------------------------- > CMS 0 Not Sending to CMS 0 > CMS 1 Not Sending to CMS 1 >Log Collection Service 'Log Collection log forwarding agent' is active and connected to config 2017/07/26 16:33:20 2017/07/26 16:34:09 323 321 2 system 2017/07/31 12:23:10 2017/07/31 12:23:18 13634645 13634637 84831 threat 2014/12/01 14:47:52 2017/07/26 16:34:24 557404252 557404169 93 traffic 2017/07/28 18:03:39 2017/07/28 18:03:50 3619306590 3619306590 1740 hipmatch Not Available Not Available 0 0 0 gtp-tunnel Not Available Not Available 0 0 0 userid Not Available Not Available 0 0 0 auth Not Available Not Available 0 0 0
      Look for the
      ‘Log collection log forwardingagent’ is active and connected to <IP_address>
      line. You can also see that CMS 0 and CMS (the Log Collectors) are not receiving logs.
      On firewall running PAN-OS 8.1.7 or later, select the
      Show Status
      link on
      Cortex Data Lake
      to verify that the firewall is connected and sending logs to the Cortex Data Lake.
  9. You can use the Log Forwarding app to archive the logs you send to Cortex Data Lake.
    If you want to be able to archive the logs you send to the Cortex Data Lake for long-term storage, SOC, or internal audit directly from the Cortex Data Lake, you can use the Log Forwarding app, which is included with your Cortex Data Lake (formerly called Logging Service) license. This app enables log forwarding from the Cortex Data Lake to an external destination such as a Syslog server or an email server. Refer to the Log Forwarding App Getting Started Guide for more information. Alternatively, you continue to forward logs directly from the firewalls to your Syslog receiver.

Related Documentation