>
    Strata Copilot
    Manage the Master Key from Panorama
    Focus
    Download PDF
    Focus
    1. Home
    2. Panorama
    3. Manage Firewalls with Panorama
    4. Manage the Master Key from Panorama
    Download PDF
    Panorama

    Manage the Master Key from Panorama

    Table of Contents

    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.
    Where Can I Use This?What Do I Need?
    • NGFW (Managed by Panorama)
    • Device management license
    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. Similarly, for Panorama andSD-WAN deployments, all devices participating in the cluster must share the same master key to maintain cluster synchronization.
    AES-256-CBC is the default encryption algorithm for master keys because Panorama and its managed devices must use the same encryption level. AES-256-GCM is supported from PAN-OS 10.0 onwards. If all managed firewalls run PAN-OS 10.0 or later, Panorama and all managed devices can use AES-256-GCM.
    Palo Alto Networks recommends using AES 256-GCM level 2 for master key encryption.
    Configuring a unique master key also eases the operational burden of updating your master keys. By configuring a unique master key for a managed firewall, you can update each master key individually without the need to coordinate changing the master key across a large number of managed firewalls.
    When replacing a master key, you must enter the current master key value to configure a new one.
    Keep track of all master keys deployed to managed firewalls, Log Collectors, and WildFire appliances — master keys cannot be recovered. If the current master key is lost, the only recovery method is a factory reset.
    Default Master Key Replacement
    (PAN-OS 12.2.2 and later releases)
    The default master key is publicly known and poses a critical security risk. Starting with PAN-OS 12.2.2, the system enforces replacement of the default master key with a custom master key within a configurable grace period.
    When the system detects the default master key, a 60-day grace period begins automatically. If you need additional time, you can extend the grace period to a maximum of 120 days, but you must configure this extension before the current grace period expires. This 120-day limit is absolute and measured from the original trigger event — an upgrade, factory reset, or first power-on. The extension does not add a new window from the date you configure it. The system always calculates the final deadline from the date of the original trigger event, regardless of when you configure the extension. You cannot extend the grace period beyond 120 days under any circumstances.
    After the grace period expires, the system blocks all standard configuration commits, commit-all jobs, and HA synchronization until you configure a custom master key. Auto-commits and dynamic updates, including content and antivirus deployments, continue to operate normally during this blocked state.
    Palo Alto Networks strongly recommends configuring a custom master key immediately after upgrading to PAN-OS 12.2.2. Do not wait for the default grace period of 60 days to approach expiry.
    The countdown begins when any of the following trigger events are detected:
    • You upgrade a device to PAN-OS 12.2.2 or a later version.
    • You restore a device running PAN-OS 12.2.2 or a later version to factory default settings.
    • You power on a new factory-default device running PAN-OS 12.2.2 or a later version for the first time.
    If a grace period timer is already running, upgrading or downgrading between PAN-OS 12.2.2 and later versions does not restart the timer. If the grace period has already expired and you downgrade to another PAN-OS 12.2.2 or later release, the timer does not restart and commits fail immediately on the downgraded version.

    Manual Deployment of Master Key

    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. Ensure there are no pending commits on the target managed firewalls before deploying the master key.
        A pending commit on the firewall may cause the master key deployment to fail or produce inconsistent results. Commit any pending firewall configuration changes before proceeding.
      3. Select PanoramaManaged DevicesSummary and Deploy Master Key.
      4. 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.
      5. Configure the master key in the Master Key dialog:
        The dialog is divided into two sections:
        • Set up a new Master Key — configure the master key credentials and validity settings:
          1. Enter the Current Master Key if one is already set on the device. If you are replacing the default master key, the field is pre-populated with a masked value (*); leave it as-is or clear it before entering the new key.
          2. (Optional) Enable (check) Stored on HSM if the master key is encrypted on a Hardware Security Module (HSM).
          3. Enter the New Master Key and Confirm New Master Key.
          4. Configure the Lifetime in Days and Hours (ranges from 1 hour to 18,250 days).
          5. Configure the Time for Reminder in Days and Hours (ranges from 1 hour to 365 days).
        • Auto-renewal & Grace Period — this section is informational only. It states: "To simplify management, you can enable auto-renewal and customize the grace period under Master Key and Diagnostics in your template or template stack." Auto-renewal and grace period settings are not configurable in this dialog. Configure them separately under PanoramaTemplates, navigating to DeviceMaster Key and Diagnostics in the relevant template or template stack.
        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.
      6. 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.
        Before verifying via system logs, check the task status in the task manager to confirm whether the deployment succeeded or failed.
      7. (Optional) Configure master key renewal options for your managed firewalls.
        This step configures master key renewal settings (auto-renew interval), not the master key itself. Configure this to automatically renew the master key deployed on the managed firewalls associated with the selected template. Otherwise, the master key expires per the configured lifetime and you must deploy a new one.
        1. Select DeviceMaster Key and Diagnostics 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 All Changes to push to all managed devices.
    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 CommitCommit to Panorama and Commit your changes to apply the HA configuration change before proceeding.
        Commit the HA disable change to Panorama before configuring the master key. This ensures Panorama is in a clean state before the master key is applied.
      3. 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, do 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.
      4. (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 Diagnostics and edit the Master Key setting.
        2. Configure the Auto Renew With Same Master Key setting.
        3. Click OK.
      5. Select CommitCommit to Panorama and Commit your changes.
      6. (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.
        If the secondary Panorama HA peer is in a passive state, you cannot commit configuration changes directly on it. You must first perform a manual failover to promote the passive peer to active state before configuring the master key. After the failover completes, configure the same master key on this peer to ensure commits and HA synchronization succeed when the peer transitions back to its original role.
    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.

    Automatic Deployment of Master Key to Managed Firewalls

    PAN-OS 12.2.2 and later releases
    PAN-OS 12.2.2 introduces an automated alternative way to deploy a master key to managed firewalls. After you configure a device master key on Panorama and enable automatic deployment for the associated device group, Panorama provisions the custom master key to every newly registering firewall on its first connection. Once configured, this process requires no further manual intervention as your network scales. This is the recommended approach for managing master keys across a growing fleet of managed firewalls.
    It is configured entirely on Panorama — the auto-deploy configuration block does not appear on individual firewalls.
    You need to meet the following two conditions for the auto-deploy workflow to work simultaneously:
    1. A device master key must be configured in the Master Key Configuration for Auto Deployed Devices section on Panorama.
    2. The Automatically push content when software device/VM or container or ZTP registers to Panorama checkbox must be enabled in the Template Stack associated with the target firewalls.
    Panorama needs to be running PAN-OS version 12.2.2 or later. Managed firewalls can be on earlier PAN-OS versions, provided they support legacy master-key functionality.
    Palo Alto Networks recommends the following order after upgrading Panorama to PAN-OS 12.2.2. First, configure a custom master key for Panorama itself (see Manage the Master Key from Panorama), and then configure the device master key for auto-deployment in this procedure. This ensures both Panorama and all newly onboarded firewalls immediately move off the default master key.
    1. Select PanoramaMaster Key and Diagnostics.
      The following screen appears:
    2. In the Master Key Configuration for Auto Deployed Devices section, click Edit (gear icon).
      It shows a read-only Status of Set or Unset. On a Panorama freshly upgraded to PAN-OS 12.2.2, the status defaults to Unset.
    3. Enter a New Master Key and Confirm New Master Key.
      There is no Current Master Key field in this dialog. This dialog sets the common key that will be pushed to auto-deployed firewalls; it does not change the master key of any already-connected device.
    4. Configure the Lifetime in Days and Hours (ranges from 1 hour to 18,250 days).
    5. Configure the Time for Reminder in Days and Hours (ranges from 1 hour to 365 days).
    6. Click OK to apply the auto-deployment master key configuration.
      No commit is required. The auto-deployment master key configuration is applied immediately as an operational command when you click OK.
    7. Enable the automatic content push checkbox in the Template Stack to activate auto-deployment of the master key to newly registering firewalls.
      1. Select PanoramaTemplates.
      2. Select the Template Stack associated with the target auto-deployed firewalls and click Edit.
        The device master key is associated with the Template Stack, not an individual Template, because this is where devices are associated in Panorama.
      3. In the Template Stack dialog, select the Automatically push content when software device/VM or container or ZTP registers to Panorama checkbox.
        This checkbox is a hard prerequisite for master key auto-deployment. Without it enabled in the associated template stack, Panorama will not push the device master key when a new firewall registers — even if the master key is configured in the Master Key Configuration for Auto Deployed Devices section.
      4. Click OK.
      5. Select Commit to Panorama and then Commit and Push to apply the updated template stack configuration to managed firewalls.
    8. Onboard the target firewalls to the same Template Stack where you enabled the checkbox.
      The auto-deployment of the master key applies only to firewalls whose serial numbers are registered under the Template Stack configured in the previous step. During device onboarding, add the firewall serial number to Panorama and associate it with that Template Stack. Firewalls that connect to Panorama under a different Template Stack, or with no Template Stack association, will not receive the auto-deployed master key.
    9. Verify that the master key was automatically deployed to a newly onboarded firewall.
      1. Select PanoramaManaged DevicesSummary.
      2. Locate the newly onboarded firewall. Check the two new status columns:
        • Default Master Key Enabled — should show No (custom key is now active).
        • Days Remaining to Configure Custom Master Key — should show Not Applicable.
      3. (Optional) Login to the firewall web interface to confirm directly.
        1. SelectDeviceMaster Key and Diagnostics.
        2. Confirm that a custom master key is configured and the Default Master Key Grace Period field is hidden — this confirms the device is no longer using the default master key and grace period enforcement is no longer applicable.

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