--- title: "Allowing or preventing a Central Management System peer to use a proxy server" slug: "allowing-or-preventing-a-central-management-system-peer-to-use-a-proxy-server-2" updated: 2026-08-25T20:25:34Z published: 2026-08-25T21:18:40Z canonical: "docs.trellix.com/allowing-or-preventing-a-central-management-system-peer-to-use-a-proxy-server-2" --- > ## 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. # Allowing or preventing a Central Management System peer to use a proxy server Use the CLI commands to allow or prevent a Central Management System peer to use a proxy server to connect to other remote Central Management System peers. If you allow a Central Management System peer to use a proxy server, the proxy settings will be the same as those configured for DTI interaction to connect to other remote Central Management System peers. By default, a Central Management System peer does not use a proxy server to connect to other remote peers. ### Note You can allow or prevent a Central Management System peer to use a proxy server only using the CLI. Prerequisites - Admin access to the Central Management System appliance. - A connection to the Dynamic Threat Intelligence (DTI) Cloud. - Network connectivity over SSH (port 22) and HTTPS (port 443) must be allowed on each of the participating Central Management System appliances. - CM Peer Service must be enabled on each of the participating Central Management System appliances. - Authentication tokens must be exchanged for communication between the CM peers. :