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.