--- title: "Configure Interset" slug: "configure-interset" tags: ["ESM", "Reference"] updated: 2026-10-27T15:50:33Z published: 2026-10-27T15:50:33Z canonical: "docs.trellix.com/configure-interset" --- > ## 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. # Configure Interset With a fully configured and working Interset and Trellix ESM solution, this information is required. - Familiarity with configuring Flume using Ambari. See the Configure Data Ingest documentation. - The tenant ID in Interset that contains the data to send to the Trellix Event Receiver Trellix ESM (for example, 0). - The name (FQDN or IP address) and port of the Trellix Event Receiver. 1. In Apache Ambari, create the Flume Export Configuration Group. 2. Configure the system so that events are sent as Syslog to the Trellix Event Receiver. 3. Copy the `esmSyslog.conf` file from the `/opt/interest/export/conf-templates` folder to a local system, and make these substitutions: - On each line, change the tenant ID **** to the appropriate tenant ID (for example, 0). - Change the Trellix ESM Event Receiver location **** with the port number of the Trellix Event Receiver. - Replace any other system variables, such as ****, with appropriate values. 4. Upload and save the new `esmSyslog.conf` file to Ambari for processing. 5. Repeat Step 2 with `esmStorySyslog.conf`, located in the same template folder, to also send high risk stories to the Trellix Event Receiver. By default, only stories with a risk score greater than 75 are sent. To change this behavior, change the value in the following line as needed: ``` interset_auth_events__esm.sources.kafkaSource.interceptors.scoreChecker.toCompare = riskScore:greaterThan:75 ``` :