Panorama Administrator's Guide
    : Manage the Master Key from Panorama
    Focus
    Download PDF
    Focus
    1. Home
    2. Panorama
    3. Panorama Administrator's Guide
    4. Manage Firewalls
    5. Manage the Master Key from Panorama
    Download PDF

    Panorama Administrator's Guide

    Manage the Master Key from Panorama

    Table of Contents
    End-of-Life (EoL)

    Manage the Master Key from Panorama

    Deploy new, or renew expiring master keys, to firewalls, log collectors, and WF-500 appliances from the Panorama™ management server.
    Panorama, firewalls, Log Collectors, and WF-500 appliances use a master key to encrypt sensitive elements in the configuration and they have a default master key they use to encrypt passwords and configuration elements. As part of a standard security practice, you should replace the default master key and change the key on each individual firewall, Log Collector, WildFire appliance, and Panorama before it expires.
    To strengthen your security posture, configuring a unique master key for Panorama and for each managed firewall. By configuring unique master keys, you can ensure that a compromised master key does not compromise the configuration encryption of your entire deployment. Unique master keys are supported only for Panorama and managed firewalls. Log Collectors and WildFire appliances must share the same master key as Panorama. For Panorama or managed firewalls in a high availability (HA) configuration, you must deploy the same master key for both HA peers as the master key is not synchronized across HA peers.
    The default encryption algorithm that the master key uses to encrypt data is AES-256-CBC—the same algorithm that the master key used prior to PAN-OS 10.0. AES-256-CBC is the default encryption level because when you manage firewalls with Panorama, the managed firewalls may be on different PAN-OS releases, and firewalls on PAN-OS releases earlier than PAN-OS 10.0 do not support AES-256-GCM. This is why Panorama must use the lowest level of encryption that its managed devices can use. For example, if some managed devices run PAN-OS 10.0 and some run earlier versions, Panorama must use AES-256-CBC. However, if all managed devices run PAN-OS 10.0 or later, then Panorama and all of its managed devices can use AES-256-GCM.
    Palo Alto Networks recommends using AES 256-GCM level 2 for master key encryption.
    When a master key expires, you must enter the current master key in order to configure a new master key.
    Be sure to keep track of the master key you deploy to your managed firewalls, Log Collectors, and WildFire appliances because master keys cannot be recovered. you must reset to factory default if you cannot provide the current master key when it expires.
    1. Log in to the Panorama Web Interface.
    2. (Best Practice) Select Commit and Commit and Push any pending configuration changes.
      Panorama must re-encrypt data using the new master key. To ensure all configuration elements are encrypted with the new master key, you should commit all pending changes before deploying the new master key.
    3. Configure a unique master key for a managed firewall.
      1. (HA only) Disable Config Sync for managed firewalls.
        This step is required before deploying a new master key to a firewall HA pair
        1. Log in to the Panorama Web Interface.
        2. Select DeviceHigh AvailabilityGeneral and select the Template containing the managed firewall HA configuration.
        3. Edit the HA Pair Settings Setup.
        4. Disable (clear) Enable Config Sync and click OK.
        5. Commit and Commit and Push your configuration changes.
      2. Select PanoramaManaged DevicesSummary and Deploy Master Key.
      3. Select a managed firewall and Change the master key.
        If you want to deploy a unique master key for a specific set of managed firewalls, you can select those specific managed firewalls as well.
      4. Configure the master key:
        1. If renewing a master key, enter the Current Master Key. If you are replacing the default master key with a new master key, do not specify a Current Master Key.
        2. (Optional) Enable (check) Stored on HSM if the master key is encrypted on a Hardware Security Module (HSM).
        3. Specify the New Master Key and Confirm Master Key.
        4. Configure the master key Lifetime and Time for Reminder.
        5. Click OK.
          The new master key is automatically pushed to your managed firewalls after you click OK. Proceed only if you are certain you are ready to change the master key for your managed firewalls.
      5. Verify that the master key was deployed successfully to all selected managed firewalls.
        A System log generates when you deploy a new master key from Panorama.
      6. (Optional) Configure the master key to automatically renew for your managed firewalls.
        Configure this setting to automatically renew the master key deployed on the managed firewalls associated with the selected template. Otherwise, the master key expires per the configured master key lifetime and you must deploy a new master key.
        1. Select DeviceMaster Key and Diagnostic and select the Template containing the target managed firewalls.
        2. Edit the Master Key settings and configure the Auto Renew With Same Master Key setting.
        3. Click OK.
        4. Commit and Commit and Push your configuration changes.
    4. Configure the master key on Panorama.
      1. (HA only) Disable the HA configuration for Panorama.
        This step is required to successfully change the master for both Panorama HA peers. You are unable to commit configuration changes on the secondary HA peer when Panorama is in an HA configuration.
        1. Log in to the Panorama Web Interface.
        2. Select PanoramaHigh AvailabilityGeneral and edit the HA Setup.
        3. Disable (uncheck) Enable HA and click OK.
        4. Commit and Commit to Panorama.
      2. Select PanoramaMaster Key and Diagnostics and configure the master key.
        1. If renewing a master key, enter the Current Master Key. If you are replacing the default master key with a new master key, o not specify a Current Master Key.
        2. Configure the New Master Key and Confirm Master Key.
        3. Configure the master key Lifetime and Time for Reminder.
        4. Click OK.
          The new master key is automatically committed to Panorama after you click OK. Proceed only if you are certain you are ready to change the master key on Panorama.
      3. (Optional) Configure the Panorama master key to automatically renew.
        Configure this setting to automatically renew the master key deployed on Panorama. Otherwise, the master key expires per the configured master key lifetime and you must deploy a new master key.
        1. Select PanoramaMaster Key and Diagnostic and edit the Master Key setting.
        2. Configure the Auto Renew With Same Master Key setting.
        3. Click OK.
      4. Select CommitCommit to Panorama and Commit your changes.
      5. (HA only) Repeat this step to configure an identical master key on the secondary HA peer.
        You must manually configure an identical master key on the primary and secondary HA peers when Panorama is in an HA configuration. The master key is not synchronized between the primary and secondary HA peers.
    5. Deploy the master key to Log Collectors.
      The master key configured for your Log Collectors must be identical to the master key configured for Panorama.
      1. Select PanoramaManaged Collectors and Deploy Master Key.
      2. Select all devices and Change the master key.
      3. Configure the master key:
        1. If renewing a master key, enter the Current Master Key. If you are replacing the default master key with a new master key, do not specify a Current Master Key.
        2. Specify the New Master Key and Confirm Master Key.
        3. Configure the master key Lifetime and Time for Reminder.
        4. Click OK.
          The new master key is automatically pushed to your Log Collectors after you click OK. Proceed only if you are certain you are ready to change the master key for your Log Collectors.
      4. Verify that the master key was deployed successfully to all selected devices.
        A System log generates when you deploy a new master key from Panorama.
    6. Deploy the master key to managed WildFire appliances.
      The master key configured your WildFire appliances must be identical to the master key configured for Panorama.
      1. Select PanoramaManaged WildFire Appliances and Deploy Master Key.
      2. Select all devices and Change the master key.
      3. Configure the master key:
        1. If renewing a master key, enter the Current Master Key. If you are replacing the default master key with a new master key, do not specify a Current Master Key.
        2. Specify the New Master Key and Confirm Master Key.
        3. Configure the master key Lifetime and Time for Reminder.
        4. Click OK.
          The new master key is automatically pushed to your WildFire appliances after you click OK. Proceed only if you are certain you are ready to change the master key for your WildFire appliances.
      4. Verify that the master key was deployed successfully to all selected devices.
        A System log generates when you deploy a new master key from Panorama.
    7. (HA Panorama only) Reconfigure the Panorama HA configuration.
      Repeat this step for both the primary and secondary Panorama HA peers.
      1. Select PanoramaHigh AvailabilityGeneral and edit the HA Setup.
      2. Enable (check) Enable HA and click OK.
      3. Commit and Commit to Panorama.
    8. (HA Firewalls only) Enable config sync for managed firewalls.
      1. Select DeviceHigh AvailabilityGeneral and select the Template containing the managed firewall HA configuration.
      2. Edit the HA Pair Settings Setup.
      3. Enable (check) Enable Config Sync and click OK.
      4. Commit and Commit and Push your configuration changes.

    © 2024 Palo Alto Networks, Inc. All rights reserved.