: Manage the Master Key from Panorama
Focus
Focus

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. You must deploy the same master key to all of your managed devices and you must configure the master key on Panorama to successfully push the configuration from Panorama to your managed devices. To ensure a uniform key deployment, deploy a new master key or renew an expiring master key on multiple firewalls, Log Collectors, and WF-500 appliances directly from Panorama. See Configure the Master Key for more information on configuring a master key.
To update the master key for managed firewalls from Panorama, the configuration pushed from Panorama and the local firewall configuration must not contain any cross references to each other in their configuration objects.
In this procedure, you must contact Palo Alto Networks Support to push the Panorama configuration back to managed firewalls for which you localized the configuration and ensure you have a complete list of all local overrides on your managed firewalls. Failure to preserve important local firewall configurations or restore any local overrides or references can result in network disruptions.
Palo Alto Networks recommends updating the master key from Panorama during a planned maintenance window and with the help of Palo Alto Networks Support to avoid network disruptions for your organization.
If your managed firewalls contain both local and Panorama pushed configuration that reference one another, you are required to either localize the configuration to the firewall. This removes any local overrides of a Panorama pushed configuration which may lead to network disruptions if not restored correctly.
For managed firewalls in a high availability (HA) configuration, you are required to disable HA as well.
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 the firewall, Log Collector, and WildFire appliance master key to automatically renew with the same master key after the lifetime of the key expires.
    Automatically renewing the master key allows you to keep your configuration encrypted in the event the key expires before a maintenance window but this is not a replacement for deploying a new master key after the key lifetime expires. Consider the number of days until your next available maintenance window when configuring the master key to automatically renew when the lifetime of the key expires.
    1. Select DeviceMaster Key and Diagnostics and select the template containing the managed firewall, Log Collector, or WildFire master key configuration settings.
    2. Edit the Master Key setting.
    3. Configure Panorama to Auto Renew with Same Master Key for a specified number of days or hours.
  4. Localize the managed firewall configuration.
    This step is required only if the managed firewall has a local and Panorama pushed configuration that reference each other or local overrides of a Panorama pushed configuration.
    Skip this step if your managed firewall configuration is entirely pushed from Panorama, or if the managed firewall configuration contains both a local and Panorama pushed configuration contains no references to each other or local overrides.
    1. Log in to the firewall web interface.
    2. Locate and document all local overrides of the Panorama pushed configuration.
      This step is required when you restore configuration objects pushed from Panorama to the managed firewall configuration. Localizing the managed firewall configuration removes all local overrides and converts them into local configuration objects. When you restore the managed firewall configuration, these objects may be overridden with a Panorama pushed configuration objects of the same name and not have the firewall specific values.
    3. Select DeviceSetupManagement and edit the Panorama Settings.
    4. Disable Panorama Policy and Objects and Import Panorama Policy and Objects before disabling.
      Import Panorama Policy and Objects before disabling to import the Panorama pushed policy and device group objects to the local firewall configuration. Otherwise, the firewall deletes these Panorama pushed policy and device settings from the managed firewall.
    5. Click OK.
    6. Disable Device and Network Templates and Import Device and Network Templates before disabling.
      Import Device and Network Templates before disabling to import the Panorama pushed device and template objects to the local firewall configuration. Otherwise, the firewall deletes these Panorama pushed device and template settings from the managed firewall.
    7. Click OK.
    8. Commit.
  5. Deploy the master key to managed firewalls.
    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. Select DeviceHigh AvailabilityGeneral and select the Template containing the managed firewall HA configuration.
      2. Edit the HA Pair Settings Setup.
      3. Disable (clear) Enable Config Sync and click OK.
      4. Commit and Commit and Push your configuration changes.
    2. Select PanoramaManaged DevicesSummary and Deploy Master Key.
    3. Select all devices and Change the master key.
    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. Specify the New Master Key and Confirm Master Key.
      3. Configure the master key Lifetime and Time for Reminder.
      4. Click OK.
    5. 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 Log Collectors.
    The master key configured for your Log Collectors must be identical to the master key configured for Panorama and managed devices.
    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.
    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. Deploy the master key to managed WildFire appliances.
    The master key configured for your WildFire appliances must be identical to the master key configured for Panorama and managed devices.
    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.
    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.
  8. Configure the master key on Panorama.
    The master key configured for Panorama must be identical to the master key configured for managed firewalls, Log Collectors, and WildFire appliances.
    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. Select PanoramaHigh AvailabilityGeneral and edit the HA Setup.
      2. Disable (uncheck) Enable HA and click OK.
      3. 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, 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.
    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.
  9. (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.
  10. (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.
  11. Enable Panorama to push configuration objects to the managed firewall.
    1. Log in to the firewall web interface.
    2. Select DeviceSetupManagement and edit the Panorama Settings.
    3. Enable Panorama Policy and Objects and click OK.
    4. Enable Device and Network Templates and click OK.
    5. Click OK.
    6. Commit.
  12. Push the Panorama configuration back to managed firewalls for which you localized the configuration.
    Perform this step with Palo Alto Networks Support and ensure you have a complete list of all local overrides on your managed firewalls. Failure to preserve important local firewall configurations or restore any local overrides or references can result in network disruptions.
    1. Log in to the Panorama Web Interface.
    2. Select CommitPush to Devices and Edit Selections.
    3. Check (enable) Include Device and Network Templates and Force Template Values.
      This is required to convert the localized Panorama configuration on the managed firewall back to a Panorama pushed configuration.
    4. Select Device Groups or Templates to select the managed firewall that required localizing the Panorama pushed configuration.
    5. Click OK.
    6. Push to the selected managed firewalls.
    7. Log in to the firewall web interface of the impacted managed firewalls to modify the local firewall configuration as needed.