--- title: "Network requirements" slug: "network-requirements-2" tags: ["Helix Enterprise", "Integration", "Sec Ops and Analytics"] updated: 2026-09-07T06:50:12Z published: 2026-09-14T13:34:41Z canonical: "docs.trellix.com/network-requirements-2" stale: true --- > ## 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. # Network requirements - Standalone devices are prevented from automatically connecting to a cloud Helix Enterprise Central Management System appliance in the network (if any). See [Preventing connections to a cloud Central Management appliance](/network-and-platform/docs/preventing-connections-to-a-cloud-central-management-system-appliance-1). - Devices connected to a Helix Enterprise-enabled Central Management System appliance are configured to stream alerts and health statistics directly to Helix Enterprise, and the Central Management System appliance is prevented from streaming this data to Helix Enterprise on behalf of the connected devices. See [Sending alerts and health stats directly from appliances](/network-and-platform/docs/sending-alerts-and-health-stats-directly-from-appliances). - Connectivity with the DTI network. - Connectivity with the alert ingestion URI. Add the fully qualified domain name (FQDN) or Helix full URL to your Web proxy server and firewall. Your FQDN is in the `FQDN` field of the `show helix` command and the URL is in the `Helix Full URL` field of the `show datastreaming helix` command. The traffic uses HTTPS (port 443). - Connectivity with the Helix Enterprise Web UI URL. Add `https://apps.fireeye.com/helix/id/<helixID>` to your Web proxy server and firewall. Your `<helixID>` is displayed in the `Console URL` field in the `show helix` CLI command output. The traffic uses HTTPS (port 443).