--- title: "Integrating with Trellix Helix" slug: "integrating-with-trellix-helix" updated: 2026-11-17T09:22:59Z published: 2026-11-17T09:22:59Z canonical: "docs.trellix.com/integrating-with-trellix-helix" --- > ## 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. # Integrating with Trellix Helix Trellix NDR integrates with Trellix Helix to forward security alerts for centralized threat correlation, searching, and Security Operations Center (SOC) visibility. In NDR 4.2, alert forwarding to Helix is mediated using standard Syslog via a dedicated Trellix Communication Broker (Comm Broker). Forwarding alerts in standard Syslog framing allows Helix to properly classify and map incoming NDR events under the `class=trellix_ndrc` schema. **Note:** This version supports Comm Broker-mediated Syslog integration with Trellix Helix. Direct API-based integration with Helix is planned for a future release. ## How the integration works 1. **Alert generation:** NDR generates security alerts and formats them into standard Syslog framing. 2. **Dedicated forwarding:** The alert payload is sent to a dedicated, standalone Comm Broker instance handling the NDR data stream. 3. **Helix parsing:** Comm Broker relays the log stream to Trellix Helix over HTTPS (port 443), where the NDR parser classifies and maps the event fields (including MITRE ATT&CK mappings, attacker/victim IPs, risk scores, and alert URLs). **IMPORTANT:** NDR Engineering recommends using a dedicated standalone Comm Broker for NDR data streams rather than routing through an existing NX or NDR sensor Comm Broker. Using a dedicated Comm Broker isolates the data stream, prevents data loops, and avoids performance degradation under high alert volumes. ## Integration prerequisites Before configuring Trellix Helix integration, ensure the following prerequisites are met: - **License requirement:** You must have a valid NDR Core or Enterprise license. - **Dedicated Comm Broker host:** A standalone Linux server (Ubuntu 20.04+ or CentOS 7+) with the Trellix Comm Broker software installed. - **Network connectivity:** - Network access from NDR to the Comm Broker IP and configured listening port (e.g., port 1025). - Outbound HTTPS access (port 443) from the Comm Broker host to the Trellix Helix receiver endpoint. - **NDR administrative privileges:** `npadmin` CLI access to the NDR appliance. ## Configure the standalone Comm Broker 1. Install the Comm Broker package on your dedicated Ubuntu or CentOS Linux host. For details, see the [Trellix Helix Comm Broker Installation Guide](https://docs.trellix.com/network-and-platform/docs/install-and-configure-the-comm-broker). 2. Configure the Comm Broker LOGSENDER SETUP parameters: - **Sender Type:** Select *Unmanaged Comm. Broker* or *Managed Comm. Broker*. - **Receiver URL:** Specify your tenant's Helix receiver URL. - **Receiver Port:** 443 - **Routes / Ingress:** Define the inbound protocol, IP, and listening port for receiving NDR logs using JSON format, UDP protocol, and a user-configured port (for example, 1025). 3. Verify that the Comm Broker registers successfully and appears under **Sensors** in your Trellix Helix Web UI. ## Configure Helix alert export on NDR CLI 1. Using SSH, log in to the NDR appliance as `npadmin` : ```plaintext ssh npadmin@ ``` 2. Enter privileged mode and configuration mode: ```plaintext npadmin@hostname> enable npadmin@hostname# configure system ``` 3. Enter the syslog configuration menu: ```plaintext npadmin@hostname(config)# syslog ``` 4. The Syslog configuration menu appears: ```plaintext 1: Enable log shipping = False 2: Logging level = info 3: Logging target(s) = 4: Logging export protocol = udp 5: Enable TLS = False 6: Enable audit log shipping = False 7: Alert export ------------------------ Q: Save changes and exit C: Cancel changes and exit ``` 5. Select option **7** (Alert export). 6. In the Alert export sub-menu, configure the following settings: - Select option **1** (Enable alert export) and set it to **True**. - Select option **3** (Helix export target) and enter the IP address and listening port of your dedicated Comm Broker host. 7. Type **Q** to save changes and exit the menu. ## Verify alert forwarding and ingestion ### On the NDR CLI - Re-enter syslog configuration mode to confirm `Enable alert export = True` and that the `Helix export target` is set correctly. ### On the Comm Broker host - Verify that the Comm Broker service is active and running. - Run `tcpdump` on the listening port to verify that Syslog packets are arriving from the NDR (use the port configured in your Comm Broker Routes setup): `sudo tcpdump -i any port <configured_port> -nn` ### On the Trellix Helix UI 1. Log in to your Trellix Helix console and navigate to **Configure > Sensors**. 2. Verify that your Comm Broker host is listed with status **Ok** and a recent **Last Check In** timestamp. 3. Navigate to **Search**. There can be multiple search queries to view ingested NDR alerts. Examples: - `meta_cbid=<Comm Broker ID>` : Returns results specific to alerts from that particular Comm Broker. - `class=trellix_ndrc`: Provides all NDR-related alerts from multiple Comm Brokers. 4. Expand an event record to verify that alert fields (such as `alertUuid,` `alertSeverity,` `mitre-mapping,` `attackerIP,` `victimIP,` and `ndrAlertUrl` are correctly parsed.