--- title: "Global host-key authentication on a managed appliance in a NAT deployment" slug: "global-host-key-authentication-on-a-managed-appliance-in-a-nat-deployment-1" tags: ["File Protect (FX)", "Malware Analysis (AX)", "IAM", "Email Security - Cloud", "Network Security (NX)", "Email Security — Server", "Central Management System", "Helix Enterprise", "Endpoint Security (HX)", "Product Usage", "Install and Get Started", "Helix", "Intelligent Virtual Execution "] updated: 2026-09-01T19:03:12Z published: 2026-09-01T19:03:12Z canonical: "docs.trellix.com/global-host-key-authentication-on-a-managed-appliance-in-a-nat-deployment-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Global host-key authentication on a managed appliance in a NAT deployment When global host-key authentication is enforced on a managed appliance, you must obtain the public host-key from the Central Management System appliance and import it into the managed appliance global host-keys database. This is described in [Host-key authentication](/docs/secure-shell-ssh-authentication). The Central Management System appliance host-key string includes its IP address. If the Central Management System appliance in an internal network behind a NAT gateway, the IP address in the key string you obtain from the Central Management System appliance Web UI or CLI must be replaced with the virtual IP address that is mapped to the Central Management System appliance on the NAT gateway. ### Example In this example, the Central Management System appliance is behind the NAT gateway. Its IP address is 1.1.1.5, and its virtual IP address is 3.3.3.5. ### Note This example is from an Email Security — Server appliance, but it is representative of other managed appliances as well. ![CM_Int_EX_Initiates_sp_v2.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-5e5c6de5-f209-572a-c3e7-a9018141edc3.jpg?sv=2026-02-06&spr=https&st=2026-11-19T21%3A32%3A26Z&se=2026-11-19T22%3A32%3A26Z&sr=c&sp=r&sig=M0otHgixg97cusCwCpIH7OsMLBNWtdqeui%2BMywQZkQo%3D) The host-key string you obtain from the Central Management System appliance Web UI or CLI starts with "1.1.1.5". For example: ``` 1.1.1.5 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCzd5JwKBjHLe/jxkF0JzWcXOTw9l0 bz2SctkQrihkqg/zXqrmxAfgbzYulDSIxOKZTh2VBnKsy0qRWrCps64Itlh6iRlr7Jxa+jAtTAGsy ... ``` Before you import the host-key into the Email Security — Server appliance global host-keys database, you must replace "1.1.1.5" with "3.3.3.5." For example: ``` 3.3.3.5 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCzd5JwKBjHLe/jxkF0JzWcXOTw9l0 bz2SctkQrihkqg/zXqrmxAfgbzYulDSIxOKZTh2VBnKsy0qRWrCps64Itlh6iRlr7Jxa+jAtTAGsy ... ``` :