--- title: "Mappings used when the Endpoint Security (HX) appliance initiates the connection" slug: "mappings-used-when-the-endpoint-security-hx-appliance-initiates-the-connection" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-09-23T17:24:36Z published: 2026-09-23T17:24:36Z canonical: "docs.trellix.com/mappings-used-when-the-endpoint-security-hx-appliance-initiates-the-connection" --- > ## 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. # Mappings used when the Endpoint Security (HX) appliance initiates the connection This section shows the NAT address mapping required for each supported topology in which the Endpoint Security (HX) appliance initiates the connection with the Central Management System appliance: - [Central Management System appliance Is behind a NAT gateway](/docs/mappings-used-when-the-endpoint-security-hx-appliance-initiates-the-connection#UUID-9d83050d-e54d-8c21-26e3-8aecdab6634a_id_applinitext) - [Endpoint Security (HX) appliance is behind a NAT gateway](/docs/mappings-used-when-the-endpoint-security-hx-appliance-initiates-the-connection#UUID-9d83050d-e54d-8c21-26e3-8aecdab6634a_id_applinitint) - [Central Management System and Endpoint Security (HX) appliance are behind different NAT gateways](/docs/mappings-used-when-the-endpoint-security-hx-appliance-initiates-the-connection#UUID-9d83050d-e54d-8c21-26e3-8aecdab6634a_id_applinit2nat) - [Central Management System and Endpoint Security (HX) appliance are in external networks](/docs/mappings-used-when-the-endpoint-security-hx-appliance-initiates-the-connection#UUID-9d83050d-e54d-8c21-26e3-8aecdab6634a_id_cm) Some topologies use virtual IP addresses. These addresses are mapped on the NAT gateway to reach a Central Management System appliance or managed device that is in an internal network behind the gateway. ### Note Only those addresses that need mapping are shown. If no mapping is indicated, the default IP addresses and default ports (22, or 22 and 443) will be used. ### Central Management System appliance is behind a NAT gateway NAT address mappings are required for deployments in which the Endpoint Security (HX) appliance initiates a connection to the Central Management System appliance behind a NAT gateway. The mapping details depend on whether the Endpoint Security (HX) appliance is configured for single-port or dual-port communication. ###### Single-port Communication If the Endpoint Security (HX) appliance is configured for single-point communication and initiates a connection with the Central Management System appliance behind a NAT gateway, a virtual NAT IP address and port must be mapped to the internal Central Management System IP address and port 22. The Endpoint Security (HX) appliance uses the mapping to send a request to be added to the Central Management System appliance for management and also to request software updates. ![CM_Int_EX_Initiates_sp_v2.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-c55b9a1e-85ee-6cb7-43f4-73332edf9fbd(12).jpg?sv=2026-02-06&spr=https&st=2026-11-19T21%3A56%3A35Z&se=2026-11-19T22%3A56%3A35Z&sr=c&sp=r&sig=6h82K8f64%2BiImc4zbXYaN20cSRJYSZ%2Bn%2FkJWD4Par4A%3D) ###### Dual-port communication If the Endpoint Security (HX) appliance is configured for dual-port communication and initiates a connection with the Central Management System appliance behind a NAT gateway, a virtual NAT IP address and port must be mapped to the internal Central Management System IP address and port 22. The Endpoint Security (HX) appliance uses the mapping in order to send a request to be added to the Central Management System appliance for management and also to request software updates. However, because the Central Management System appliance is in an internal network, the accessible DTI server IP address and HTTPS port must be mapped to the Central Management System internal IP address and port 443 so that the Endpoint Security (HX) appliance can request software updates. ![CM_IntNXInitiates_fig.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-546e73b9-5689-ee35-0569-396d6b80a592(12).jpg?sv=2026-02-06&spr=https&st=2026-11-19T21%3A56%3A35Z&se=2026-11-19T22%3A56%3A35Z&sr=c&sp=r&sig=6h82K8f64%2BiImc4zbXYaN20cSRJYSZ%2Bn%2FkJWD4Par4A%3D) ### Endpoint Security (HX) appliance is behind a NAT gateway No mapping is required because the Central Management System appliance is in an external network and the Endpoint Security (HX) appliance can access it. ### Central Management System and Endpoint Security (HX) appliance are behind different NAT gateways NAT address mappings are required for deployments in which the Endpoint Security (HX) appliance initiates a connection to the Central Management System appliance and where the two devices are behind different NAT gateways. The mapping details depend on whether the Endpoint Security (HX) appliance is configured for single-port or dual-port communication. ###### Single-port communication If the Endpoint Security (HX) appliance is configured for single-port communication and if the Endpoint Security (HX) appliance and the Central Management System appliance are behind different NAT gateways, the virtual NAT gateway 1 IP address and port must be mapped to the Central Management System internal IP address and port 22. The Central Management System appliance uses the mapping to configure and monitor the Endpoint Security (HX) appliance. The Endpoint Security (HX) appliance uses the mapping to send a request to be added to the Central Management System appliance for management and also to request software updates. ![EX_Initiates_2NAT_sp_v2.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-05223ca0-f673-eb10-260a-9830d7888909(12).jpg?sv=2026-02-06&spr=https&st=2026-11-19T21%3A56%3A35Z&se=2026-11-19T22%3A56%3A35Z&sr=c&sp=r&sig=6h82K8f64%2BiImc4zbXYaN20cSRJYSZ%2Bn%2FkJWD4Par4A%3D) ###### Dual-port communication If the Endpoint Security (HX) appliance is configured for dual-port communication and if the Endpoint Security (HX) appliance and the Central Management System appliance are behind different NAT gateways, the following NAT address mappings are required: - The virtual NAT gateway 1 IP address and port must be mapped to the Central Management System internal IP address and port 22. The mapping enables the Endpoint Security (HX) appliance to send a request to be added to the Central Management System appliance for management and for the Central Management System appliance to configure and manage the appliance. - The Endpoint Security (HX) appliance internal IP address and port 443 must be mapped to a virtual NAT gateway 2 IP address and port. The virtual NAT gateway 1 IP address and port must be mapped to the Central Management System internal IP address and port 443 for the Endpoint Security (HX) appliance. The mappings enable the appliance to request software updates. ![CM_NXInitiates2NAT_fig.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-99bcc91a-4028-81b2-c847-e8a4fa1e8557(12).jpg?sv=2026-02-06&spr=https&st=2026-11-19T21%3A56%3A35Z&se=2026-11-19T22%3A56%3A35Z&sr=c&sp=r&sig=6h82K8f64%2BiImc4zbXYaN20cSRJYSZ%2Bn%2FkJWD4Par4A%3D) ### Central Management System and Endpoint Security (HX) appliance are in external networks No NAT address mapping is required if the two devices are in external networks and the Endpoint Security (HX) appliance initiates the connection. :