>
    Strata Copilot
    Set Up Connectivity with an Entrust nShield HSM
    Focus
    Download PDF
    Focus
    1. Home
    2. Next-Generation Firewall
    3. Certificate Management
    4. Secure Keys with a Hardware Security Module
    5. Set Up Connectivity with an HSM (PAN-OS)
    6. Set Up Connectivity with an Entrust nShield HSM
    Download PDF
    Next-Generation Firewall

    Set Up Connectivity with an Entrust nShield HSM

    Table of Contents

    Set Up Connectivity with an Entrust nShield HSM

    Establish a secure connection between your NGFW and an Entrust nShield hardware security module (HSM).
    You must set up a remote file system (RFS) as a hub to synchronize key data for all firewalls (HSM clients) in your organization that use an Entrust nShield HSM. To ensure the nShield client version on your firewalls is compatible with your nShield server, see Set Up Connectivity with an HSM (PAN-OS).
    Before the hardware security module (HSM) and firewalls connect, the HSM authenticates the firewalls based on their IP addresses. Therefore, you must configure the firewalls to use static IP addresses—not dynamic addresses assigned through DHCP. (Operations on the HSM stop working if a firewall IP address changes during runtime).
    HSM configurations are not synchronized between high availability (HA) firewall peers. Consequently, you must configure the HSM separately on each peer. In active/passive HA configurations, you must manually perform one failover to individually configure and authenticate each HA peer to the HSM. After this initial manual failover, user interaction is not required for a failover to function properly.
    ECDSA certificates are not supported for Entrust nShield HSMs.
    1. Define connection settings for each nShield HSM.
      1. Log in to the firewall web interface and select DeviceSetupHSM.
      2. Edit the hardware security module provider settings and set the Provider Configured to Entrust nShield HSM.
      3. Add each HSM server as follows. An HA HSM configuration requires two servers:
        1. Enter a Module Name for the HSM server. This can be any ASCII string of up to 31 characters.
        2. Enter an IPv4 address for the HSM Server Address.
      4. Enter an IPv4 address for the Remote Filesystem Address.
      5. Click OK and Commit your changes.
    2. (Optional) Configure a service route to connect to the HSM if you don’t want the firewall to connect through the management interface (default).
      If you configure a service route for the HSM, running the clear session all CLI command clears all existing HSM sessions, which brings all HSM states down and then up again. During the several seconds required for HSM to recover, all SSL/TLS operations will fail.
      1. Select DeviceSetupServices and click Service Route Configuration.
      2. Customize a service route. The IPv4 tab is active by default.
      3. Click HSM in the Service column.
      4. Select a Source Interface for the HSM.
      5. Click OK and Commit your changes.
    3. Register the firewall as an HSM client with the HSM server.
      This step describes the procedure for using the front panel interface of an nShield HSM. For more details, refer to nShield documentation.
      1. Log in to the front panel display of the nShield HSM.
      2. Use the right-hand navigation button to select SystemSystem configurationClient configNew client.
      3. Enter the firewall IP address.
      4. Select SystemSystem configurationClient configRemote file system and enter the IP address of the client computer where you set up the RFS.
    4. Configure the RFS to accept connections from the firewall.
      1. Log in to the RFS from a Linux client.
      2. Obtain the electronic serial number (ESN) and the hash of the KNETI key, which authenticates the HSM to clients, by running the anonkneti <ip-address> CLI command, where <ip-address> is the HSM IP address.
        For example:
        anonkneti 192.0.2.1
        B1E2-2D4C-E6A2 5a2e5107e70d525615a903f6391ad72b1c03352c
        In this example, B1E2-2D4C-E6A2 is the ESN and 5a2e5107e70d525615a903f6391ad72b1c03352c is the hash of the KNETI key.
      3. Use the following command from a superuser account to set up the RFS:
        rfs-setup --force <ip-address> <ESN> <hash-Kneti-key>
        The <ip-address> is the IP address of the HSM, <ESN> is the electronic serial number, and <hash-Kneti-key> is the hash of the KNETI key.
        The following example uses the values obtained in this procedure:
        rfs-setup --force 192.0.2.1 B1E2-2D4C-E6A2 5a2e5107e70d525615a903f6391ad72b1c03352c
      4. Use the following command to permit HSM client submissions on the RFS:
        rfs-setup --gang-client --write-noauth <FW-IPaddress>
        where <FW-IPaddress> is the firewall IP address.
    5. Authenticate the firewall to the HSM.
      1. In the firewall web interface, select DeviceSetupHSM and Setup Hardware Security Module.
      2. Click OK.
        The firewall tries to authenticate to the HSM and displays a status message.
      3. Click OK.
    6. Synchronize the firewall with the RFS by selecting DeviceSetupHSM and Synchronize with Remote Filesystem.
    7. Verify firewall connectivity and authentication with the HSM.
      1. Select DeviceSetupHSM and check the authentication and connection Status:
        • Green—The firewall is successfully authenticated and connected to the HSM.
        • Red—The firewall failed to authenticate to the HSM or network connectivity to the HSM is down.
      2. Check the Hardware Security Module Status to determine the authentication status.
        • Name—The name of the HSM.
        • IP address—The IP address of the HSM.
        • Module State—The current state of the HSM connection: Authenticated or NotAuthenticated.

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