Configure a Managed Collector

1. Record the serial number of the Log Collector.

   You will need the serial number when you add the Log Collector as a managed collector.

   1. Access the Panorama web interface.
   2. Select Dashboard and record the Serial # in the General Information section.
2. Log in to the Panorama web interface.
3. Create a device registration authentication key.

   1. Select PanoramaDevice Registration Auth Key and Add a new authentication key.
   2. Configure the authentication key.

      • Name—Add a descriptive name for the authentication key.
      • Lifetime—Specify the key lifetime for how long you can use the authentication key to onboard new Log Collectors.
      • Count—Specify how many times you can use the authentication key to onboard new Log Collectors.
      • Device Type—Specify that this authentication key is used to authenticate only a Log Collector.
        You can select Any to use the device registration authentication key to onboard firewalls, Log Collectors, and WildFire appliances.
      • (Optional) Devices—Enter one or more device serial numbers to specify for which Log Collectors the authentication key is valid.
   3. Click OK.

   4. Copy Auth Key and Close.

4. (Dedicated Log Collector only) Add the device registration authentication key to the Log Collector.

   Add the device registration authentication key only to a Dedicated Log Collector. A Panorama in Panorama mode does not need to authenticate its own local Log Collector.

   1. Log in to the Log Collector CLI.
   2. Add the device registration authentication key.

      admin> request authkey set <auth-key>

5. Add the Log Collector as a managed collector.

   1. In the Panorama web interface, select PanoramaManaged Collectors and Add a new Log Collector.
   2. In the General settings, enter the serial number (Collector S/N) you recorded for the Log Collector.
   3. Click OK to save your changes.
   4. Select CommitCommit to Panorama.
6. (Optional) Configure the Log Collector admin authentication.

   Palo Alto Networks recommends adding at least one Local Administrator with Superuser privileges for Authentication if you configure an authorization list for your managed collector.

   If you added any Imported Panorama Admin Users, then you are required to add at least one Local Administrator with Superuser privileges.

   1. Select PanoramaManaged Collectors and edit the Log Collector by clicking its name.
   2. Configure the Log Collector admin password:

      1. Select the password Mode.
      2. If you selected Password mode, enter a plaintext Password and Confirm Password. If you selected Password Hash mode, enter a hashed password string of up to 63 characters.
   3. Configure the admin login security requirements:

      If you set the Failed Attempts to a value other than 0 but leave the Lockout Time at 0, then the admin user is indefinitely locked out until another administrator manually unlocks the locked out admin. If no other administrator has been created, you must reconfigure the Failed Attempts and Lockout Time settings on Panorama and push the configuration change to the Log Collector. To ensure that an admin is never locked out, use the default 0 value for both Failed Attempts and Lockout Time.

      1. Enter the number of login Failed Attempts value. The range is between the default value 0 to the maximum of 10 where the value 0 specifies unlimited login attempts.
      2. Enter the Lockout Time value between the default value 0 to the maximum of 60 minutes.
   4. Click OK to save your changes.
7. Enable the logging disks.

   1. Select PanoramaManaged Collectors and edit the Log Collector by clicking its name.

      The Log Collector name has the same value as the hostname of the Panorama management server.
   2. Select Disks and Add each disk pair.
   3. Click OK to save your changes.
   4. Select CommitCommit to Panorama.
8. (Optional) If your deployment is using custom certificates for authentication between Panorama and managed devices, deploy the custom client device certificate. For more information, see Configure Authentication Using Custom Certificates.

   1. Select PanoramaCertificate ManagementCertificate Profile and choose the certificate profile from the drop-down or click New Certificate Profile to create one.
   2. Select PanoramaManaged Collectors and Add a new Log Collector or select an existing one. Select Communication.
   3. Select the type of device certificate the Type drop-down.

      • If you are using a local device certificate, select the Certificate and Certificate Profile from the respective drop-downs.
      • If you are using SCEP as the device certificate, select the SCEP Profile and Certificate Profile from the respective drop-downs.
   4. Click OK.
9. (Optional) Configure Secure Server Communication on a Log Collector. For more information, see Configure Authentication Using Custom Certificates.

   1. Select PanoramaManaged Collectors and click Add. Select Communication.
   2. Verify that the Custom Certificate Only check box is not selected. This allows you to continue managing all devices while migrating to custom certificates.

      When the Custom Certificate Only check box is selected, the Log Collector does not authenticate and cannot receive logs from devices using predefined certificates.
   3. Select the SSL/TLS service profile from the SSL/TLS Service Profile drop-down. This SSL/TLS service profile applies to all SSL connections between the Log Collector and devices sending it logs.
   4. Select the certificate profile from the Certificate Profile drop-down.
   5. Select Authorize Client Based on Serial Number to have the server check clients against the serial numbers of managed devices. The client certificate must have the special keyword $UDID set as the CN to authorize based on serial numbers.
   6. In Disconnect Wait Time (min), enter the number of minutes Panorama should before breaking and reestablishing the connection with its managed devices. This field is blank by default and the range is 0 to 44,640 minutes.

      The disconnect wait time does not begin counting down until you commit the new configuration.
   7. (Optional) Configure an authorization list.

      1. Add an Authorization List.
      2. Select the Subject or Subject Alt Name as the Identifier type.
      3. Specify an identifier of the selected type.
      4. Click OK.
      5. Enable the Log Collector to Check Authorization List to enforce the authorization list.
   8. Click OK.
   9. Select CommitCommit to Panorama.
10. Verify your changes.

    1. Verify that the PanoramaManaged Collectors page lists the Log Collector you added. The Connected column displays a check mark to indicate that the Log Collector is connected to Panorama. You might have to wait a few minutes before the page displays the updated connection status.

       Until you Configure a Collector Group and push configuration changes to the Collector Group, the Configuration Status column displays Out of Sync, the Run Time Status column displays disconnected, and the CLI command show interface all displays the interfaces as down.
    2. Click Statistics in the last column to verify that the logging disks are enabled.
11. Next steps...

    Before a Log Collector can receive firewall logs, you must:

    1. Configure Log Forwarding to Panorama.
    2. Configure a Collector Group—On the M-Series appliances, a default Collector Group is predefined and already contains the local Log Collector as a member. On the Panorama virtual appliance, you must add the Collector Group and add the local Log Collector as a member. On both models, assign firewalls to the local Log Collector for log forwarding.

       You must add the Log Collector to a Collector Group before it can start ingesting firewall logs. The ElasticSearch health status displays as degraded and the Log Collector cannot ingest logs until added to a Collector Group.
    3. Monitor Managed Collector Health Status to identify and resolve issues impacting log collection should they arise.