--- title: "About host-key authentication" slug: "about-host-key-authentication-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/about-host-key-authentication-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. # About host-key authentication Host-key authentication can be used to prevent man-in-the middle attacks, in which another server poses as the managed appliance or the Central Management System appliance and intercepts the traffic between them. The connection between a Central Management System appliance and a managed appliance can be server-initiated or client-initiated. **Host-key authentication using a server-initiated connection** When the Central Management System appliance and the managed appliance connect the first time using a server-initiated connection, a key exchange takes place. The managed appliance sends a copy of its host key to the Central Management System appliance, where it is compared to the keys in the Central Management System host-keys database. If strict host-key checking is enabled, the connection can be established only if the key that is sent matches an entry in the local host-keys database for the Central Management System remote user. If global host-key checking is enabled, the connection can be established only if the key that is sent matches an entry in the Central Management System global host-keys database. **Host-key authentication using a client-initiated connection** When the managed appliance and the Central Management System appliance connect the first time using a client-initiated connection, a key exchange takes place. The Central Management System appliance sends a copy of its host key to the appliance, where it is compared to the keys in the appliance's host-keys database. If strict host-key checking is enabled, the connection can be established only if the key that is sent matches an entry in the local host-keys database for the managed appliance remote user. If global host-key checking is enabled, the connection can be established only if the key that is sent matches an entry in the managed appliance global host-keys database. You can enforce strict host-key checking, global host-key checking, or both. In compliance mode, both strict and global host-key checking is enforced. For details, see the *FIPS 140-2 and Common Criteria Addendum*. In the case of primary and secondary Central Management System platforms in a Central Management System High-Availability (HA) deployment, the two Central Management System platforms exchange keys, and the connection is established if the keys match. For details, see the *Central Management System High Availability Guide*. ### Important Host keys are stored in the configuration database, so they are included in the backup file. Prerequisites - Admin access to configure authentication and create keys. - Central Management System appliances only: - Monitor, Operator, or Admin access to obtain managed appliance host keys. - The private key remains on the Central Management System appliance and cannot be computed from the public key. - Managed appliances only: - Monitor, Operator, or Admin access to obtain Central Management System appliance host keys. - The private key remains on the managed appliance and cannot be computed from the public key. :