--- title: "Streaming policy" slug: "streaming-policy" tags: ["EDR with Forensics (EDRF)", "Endpoint Security", "Incident Responder", "IT Admin"] updated: 2026-10-12T20:11:18Z published: 2026-10-12T20:11:18Z canonical: "docs.trellix.com/streaming-policy" 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. # Streaming policy The **Streaming** policy controls the flow of endpoint activity data for threat analysis. It allows you to configure the Trace plug-in to send security event information to the Trellix EDR cloud or an external S3 bucket. ### Event Streamer module The Event Streamer module is a telemetry component in the **Streaming** policy. The Event Streamer captures endpoint activity and event telemetry to DXL brokers, Helix, and Syslog servers. Enable the Event Streamer checkbox in the Streaming Policy to configure these settings: - [Windows event logs](/v1/docs/streaming-policy#windows-event-logs) - [Windows file events](/v1/docs/streaming-policy#windows-file-events) - [OS events](/v1/docs/streaming-policy#os-events-configuration) - [Event filters](/v1/docs/streaming-policy#event-filters) - [Module Settings](/v1/docs/streaming-policy#module-settings) #### Windows event logs The Windows event logs are enabled by default and stream via local buffering and batch transmission to configured destinations. You can manage these default logs in the table, or select Add Event Log to configure the custom parameters. Use these fields to add and manage the Windows event logs: - Enabled: Activates or deactivates the collection for this event log channel. - **Event Name:** Specifies the display name for the event log channel entry. - Source name: Specifies the Windows event log channel path to monitor. - Event IDs: Specifies a comma-separated list of exact event identifiers to capture. - Action: Specifies an option to Remove or Edit the log configuration. The following table defines the default Windows event log channels available for the Event Streamer module. | Option | Definition | | --- | --- | | Security | Captures Windows security and audit events, such as logon attempts and privilege usage. | | System | Captures events logged by Windows operating system components. | | TerminalServicesLocalSessionManager | Monitors local terminal services session activity and user connections. | | TerminalServicesRemoteConnectionManager | Monitors Remote Desktop Protocol (RDP) connection activity and remote sessions. | | TaskScheduler | Tracks scheduled task activity, including task registration, execution and completion. | | PowerShell | Captures PowerShell execution events and script block logging. | | Windows Defender | Monitors Microsoft Defender threat detections, signature updates, and engine health events. | | **Application Experience** | Tracks new applications and software detected during Windows inventory scans. | | Application | Captures events logged by installed applications and services that write to the Windows Application log. | | AppLocker EXE and DLL | Monitors application control policies for executable and DLL files. | | AppLocker MSI and Script | Monitors application control policies for Windows Installer and script files. | | PrintService | Tracks print spooler operations and document printing activity. | #### Add an event log Follow these steps to configure a new Windows event log channel entry: - **Display Name**: Enter the name to identify the event log channel entry. - **Event Source Name**: Enter the Windows event log channel path to monitor. - **Event ID List**: Enter the comma-separated list of event IDs to collect from the event log channel. #### Windows file events Windows file events monitor and capture new entries written to specific log files on Windows endpoints. Once configured, new log entries are buffered locally and streamed in batches to your configured destinations. You can manage existing file streams in the table, or select Add File Stream to add a new log file to monitor. The following configuration fields are available to add and manage Windows file events: - Enabled: Activates or deactivates the logging rule for the file stream. - **Display Name:** Specifies the display name to identify the file stream entry. - File Type: Specifies the application or protocol that generates the log data. - **File path:** Specifies the full path to the log file to monitor. #### Add a file stream To monitor a new log file, click Add File Stream and configure these settings: - Display Name: Enter a name for the file stream. - **Type**: Select the file type of log file to monitor. The available options include DHCP, DNS, Exchange, IIS, and Net Logon. - File path: Enter the path to the target log file. You can use wildcard characters to monitor multiple logs within a directory. For example, `C:\Windows\System32\dhcp\*.log`. #### OS events configuration The OS events module collects real-time endpoint activity directly from the endpoint operating system. The Event Streamer forwards this data to the configured syslog server. OS events support Windows, macOS, and Linux endpoints. Real-time event streaming routes events only to the syslog server. Enable the toggle to capture telemetry based on these platform compatibilities: - All operating systems: Captures process events and IPv4 or IPv6 network events. - Windows and macOS: Captures network address notification events, network DNS events, file write events, image load events, and URLs visited. - Windows only: Captures registry events. #### Event filters Filters control which endpoint events stream to external destinations. You can manage existing filters directly in the Event Filters table, or select Add Filters to configure a new filter for a specific event source. The following configuration fields are available to add and manage event filters: - Enabled: Activates or deactivates the filter. - Name: Specifies the custom name for the filter. - Source: Specifies the event source category. For example, Event log, DHCP and OS events. - OS: Specifies the target operating system. - **Default Behavior:** Specifies the default behavior (**Allow** or **Drop**) applied to selected events in the source. - Action: Modifies or removes the filter configuration. ### Create filter conditions To refine your filters, you can apply specific criteria using match criteria. Select + Add Condition to define these criteria using the following fields: The Create Filter dialog box appears. It allows you to specify the filter settings to control which endpoint events are processed The primary configuration fields include: - Filter Name: Enter the filter name. - Source: Select the source. The available options are DHCP, DNS, Event Log, Exchange, IIS, Net Logon, and OS Events. - OS: Select the target operating system. Default value: Windows - **Default Behavior:** Select the default behavior of the filter. The available options are Drop and Allow. The Conditions section specifies the logic of the filter. Select + Add Condition to introduce multiple criteria to a single filter using the following inputs: - Fieldname: Enter the fieldname. - Value: Enter the target value. - Condition: Select the condition on how the rule processes the data. The available options are Include and Exclude. #### Module settings The Module Settings controls how the telemetry data buffers on the local endpoint and transmits to configured destinations. The following table defines the configuration fields and default values available to manage module settings. | Option | Definition | | --- | --- | | Delete batch size | Specifies the number of event records removed per purge operation when the database reaches its maximum capacity. Default value: `100` | | Data Transmission frequency (seconds) | Specifies the recurring time interval for dispatching data batches. Default value: `20` | | Maximum number of events sent in a batch | Specifies the maximum number of events included in a single outbound batch. Default value: `250` | | Database vacuum frequency | Sets the number of deleted records that triggers a database vacuum to reclaim disk space. This setting applies only when memory mode is disabled. Default value: `1000` | | Maximum number of events stored in database | Sets the maximum number of events the local database retains before it purges the oldest records. Default value: `10000` | | Store events in memory only | Buffers event telemetry in endpoint memory instead of writing to disk. This option is enabled by default. | | Send on number of events in memory AND on time | Transmits data in batches when the event count threshold or the transmission time interval is reached. This option is enabled by default. | | Number of events to send on | Specifies the number of buffered events required to trigger an immediate batch transmission. Default value: `100` | | Reset | Discards custom modifications and restores factory defaults. | #### Telemetry destinations configuration The Streaming policy configures upstream destinations for trace data (managed by the Trace plug-in) and event data (managed by the Event Streamer module). #### Destinations for trace data > [!NOTE] > Note > > This section applies only to trace data collected by the Trace plug-in. You can select the following destinations for trace events: - DXL broker: Select the checkbox to send trace events to a DXL broker. - S3 bucket: Select the checkbox to send traces to an S3 bucket. This feature supports only Windows environments. #### Destinations for event data The Event Streamer module routes event data to three primary destinations: DXL broker, Helix, and Syslog server. - DXL broker: Select **Send event data to DXL Broker**. This destination requires an active DXL broker connection configured on the endpoint. - Trellix Helix: Select **Send event data to Trellix Helix**. This destination requires you to enter the following details: - Helix ID: Enter the unique identifier for the Helix instance. - Helix server: Enter the domain of the target ingestion server. For example: `<helixid>.ingest.apps.fireeye.com` - Helix event path: Enter the specific API path for ingestion. - For example: `/ingest/<helixid>` - Syslog Server: Select Send event data to Syslog Server to route Windows event logs to a syslog server. The Server Log table lists configured destinations. It displays the Enabled status, Name, Priority, Server (IP), TCP Port, SSL, and Action columns. To configure a new syslog destination, select Add Syslog Server and enter the following details: - Name: Enter a name for the syslog server. - IP Address: Enter the IP address for the syslog server - TCP Port: Enter the TCP port number. - Priority: Select the priority from the drop-down menu. - Enable TLS: Select this option to secure the transmission. You must configure a valid certificate and key to use TLS. - ### Trace - **Trace Scanning** — Configures the **Trace** plug-in on managed devices to analyze system activity and identify the root cause of security incidents. For all exclusions, use a semicolon (;) to separate items; the maximum character limit is 200,000. | Option | Definition | | --- | --- | | **Enable Trace** | Enables the **Trace** plug-in on the endpoints. This is enabled by default. | | **Log Level** | Sets the level of detail for **Trace** log files (Debug, Trace, Info, Warning, Error). Each level includes its own information and all levels below it. Use the lowest log level possible, or disable this feature if you do not need log information. - **Debug** — Detailed debug information. - **Trace** — Contains most variable value dumps. This can be too verbose to debug problems on production systems. - **Info** — Logs messages that highlight the progress of the **Trace** plug-in. - **Warning** — Information about potentially harmful situations. - **Error** — Error events that might prevent the **Trace** plug-in from running. The **Trace** log file is located at the following location: - Windows — `C:\ProgramData\Trellix\XClient\exts\plugin\UnifiedEdr\data\trace.log` - Linux — `/opt/Trellix/XClient/bin/xclient -g /tmp/xclient.log` - mac — `/Library/Application\ Support/Trellix/xclient/exts/plugin/UnifiedEdr/data/trace.log` | | **Report internal reputation failures to** **Trellix** **ePO** | Reports a threat event to ePO - SaaS if the **Trace** plug-in has internal connection issues. This is disabled by default. | | **Enable deep inspection of Windows API calls** | Activates the agent's code injection detection plug-in to monitor and inspect Windows API usage for threat detection. This is enabled by default. | | **Enable ETW-TI inspection of Windows API calls** | Enables the use of Event Tracing for Windows - Threat Intelligence (ETW-TI) to inspect Windows API calls for advanced threat detection. This is enabled by default. | | **Maximum size (MB) of the device storage that can be used by the Traces** | Sets the size limit for the **Trace** database on the device. When this limit is reached, the oldest records are discarded. **Default**: 80 MB **Range**: 0–8192 MB | | **Interval to send trace events to Trellix EDR cloud** | Specifies how often, in seconds, to send trace event notifications to the EDR cloud. **Default**: 30 seconds **Range**: 30–1800 seconds | - **Trace Destination** — Collects detailed endpoint activity data and sends it to the cloud for in-depth analysis and threat investigation. > [!NOTE] > Note > > This feature is enabled only for Windows endpoints. | Option | Definition | | --- | --- | | **Send traces to Trellix EDR cloud** | Sends traces collected on the endpoint to the Trellix EDR cloud. This is enabled by default. | | **Send traces to S3 bucket (Windows only)** | Sends traces collected on the Windows endpoint to a compatible external cloud storage S3 bucket, such as Amazon Web Services (AWS) or Google Cloud Platform (GCP). This is disabled by default. When enabled, add valid details in the fields displayed: - **Access Key ID** — Enter the access key ID for your S3 bucket.. - **S3 bucket Secret Access Key** — Enter the secret access key associated with the Access Key ID. - **S3 default Region Name** — Enter the region where your S3 bucket is hosted (for example, us-east-1). - **S3 bucket Name** — Enter the exact name of your S3 bucket. - **Interval (in seconds) to send trace events to S3 bucket** — Specifies how often, in seconds, to send trace events. **Default**: 30 seconds **Range**: 10–1800 seconds - **Specify (optional) S3 endpoint** — Use this field to define a custom endpoint URL. This is required for certain S3-compatible services such as GCP Storage (for example, [https://storage.googleapis.com](https://storage.googleapis.com)). For standard AWS S3 buckets, this field can usually be left blank. - **Verifying the Configuration** — After you have entered your S3 bucket details, click the **Verify configuration** button to validate the settings. This check ensures that the EDR cloud can successfully connect to your bucket. You will receive one of the following messages: - **Success**: Indicates a valid connection. No issues were found with the bucket name, credentials, or permissions. - **Warning**: The connection is successful, but the provided credentials have excessive permissions. For this feature to function, the only required permission is the ability to create objects. This warning flags unnecessary permissions such as Get, List, or Delete. You can still save the configuration, but we recommend you limit the permissions to only what is required. | - **Exclusion** — Configure exclusions to prevent the monitoring of trusted files, processes, or folders. This option is available when collectors are enabled and supports a character limit of 200,000. Separate multiple items using a semicolon (;). | Option | Definition | | --- | --- | | **Exclude process(es) by full path on Windows** | Excludes specified processes from being traced. The supported paths are: - Full paths - `FOLDERID_*` paths - Paths with System environment variables. User environment variables are not supported. - Wildcards The path `<Folder>\*` includes all processes in `<Folder>` and its subdirectories. | | **Disabled trace rules on Windows** | Enter a configuration code to disable specific trace rules by ID. Use this option only when working with Technical Support on the [Trellix Thrive Portal](https://thrive.trellix.com/) | | **Exclude process(es) by full path on Linux** | Enter the configuration code that can enable or disable trace rules by ID. We recommend that you enter information in this text box only when working with a Technical Support representative. The supported paths are: - Full path - `FOLDERID_*` paths - Paths with System environment variables. User environment variables are not supported. Wildcards are also supported. - `<Folder>/*` would include all processes within the folder and all its subdirectories. | | **Disabled trace rules on Linux** | Enter the configuration code that can enable or disable trace rules by ID. We recommend that you enter information in this text box only when working with a Technical Support representative. | | **Exclude file(s) on Linux** | Excludes specified files from being traced. Wildcards are not supported. Example — `/var/spool/cron/testfile.txt` | | **Exclude folder(s) on Linux** | Excludes specified folders from being traced. Wildcards are not supported. Example — `/var/spool/cron/testdir1;/var/spool/cron/testdir2/dir3` > [!NOTE] > Note > > Folder exclusions apply only to folders that exist on the endpoint when the policy is enforced. Exclusions do not apply to folders created later, even if they match the defined path. | | **Exclude process(es) by full path on Mac** | Excludes a list of full paths (using folder id). If the path matches the one on a binary, the binary being executed will not be traced. The supported paths are: - Full path - `FOLDERID_*` paths - Paths with System environment variables. User environment variables are not supported. Wildcards are also supported. - `<Folder>/*` would include all processes within the folder and all its subdirectories. | | **Disabled trace rules on Mac** | Enter configuration code that can enable or disable trace rules by ID. We recommend you to enter information in this text box only when working with a Technical Support representative. | Trace Scanner exclusions prevent the EDRF Client from tracing benign process and file activities. This section describes how process exclusions and wildcards work in the Trace Scanner across Windows, macOS, and Linux. ### Windows exclusion rules Process(es) and path(s) are case-insensitive on Windows. | Wildcard | Regex equivalent | Description | | --- | --- | --- | | `*` | `[^\\/:*?"<>\|]*` | Matches one segment and except for path-separator and Windows-forbidden chars such as a drive letter. If it is placed at the end of a trailing path separator it is treated as a match for all processes recursively. | | `**` | `.*` | Matches anything, and can span path segments and separators. | | `?` | N/A | Matches any single character, except for path-separator and Windows-forbidden chars such as a drive letter. | #### Windows examples | Exclusion path | Matches `C:\foo\bar.exe` | Matches `C:\foo\sub\bar.exe` | | --- | --- | --- | | `C:\foo` | Yes | Yes | | `C:\foo\*` | Yes | Yes | | `C:\foo\**` | Yes | Yes | | `C:\**\bar.exe` | Yes | Yes | | `C:\foo\?ar.exe` | Yes | No | | `C:\foo\bar.exe` | Yes (exact) | No | | `C:\FOO\bar.exe` | Yes (case-insensitive) | No | | `*:\foo\bar.exe` | No | No | | `?:\foo\bar.exe` | No | No | ### Linux exclusion rules Process(es) and path(s) are case-sensitive on Linux. Wildcards are currently not supported on Linux. #### Linux examples | Exclusion path | Matches `/foo/bar` | Matches `/foo/sub/bar` | Matches `/Foo/bar` | | --- | --- | --- | --- | | `/foo/bar` | Yes | No | No | | `/foo/sub/bar` | No | Yes | No | | `/Foo/bar` | No | No | Yes | File exclusion path(s) are case-sensitive on Linux. Wildcards are currently not supported on Linux. | Exclusion path | Matches `touch/var/spool/cron/junk` | | --- | --- | | `/var/spool/cron/junk` | Yes | Folder exclusion path(s) are case-sensitive on Linux. Wildcards are currently not supported on Linux. | Exclusion path | Matches `touch/var/spool/cron/junk` | | --- | --- | | `/var/spool/cron` | Yes | ### macOS exclusion rules Process(es) and path(s) are case-sensitive on macOS. The single character `?` wildcard match is not supported on macOS. | Wildcard | Regex equivalent | Description | | --- | --- | --- | | `*` | `[^/:]*` | Matches one segment, excludes forward slash and colon. If it is placed at the end of a trailing path separator it is treated as a match for all processes recursively. | | `**` | `.*` | Matches anything, and can span path segments and separators. | #### macOS examples | Exclusion path | Matches `/foo/bar` | Matches `/foo/sub/bar` | Matches `/Foo/bar` | | --- | --- | --- | --- | | `/foo` | Yes | Yes | No | | `/foo/*` | Yes | Yes (via `/.*`) | No | | `/foo/**` | Yes | Yes | No | | `/foo/bar` | Yes | No | No | ### Alerts | Option | Definition | | --- | --- | | **Alerts Streamed to EDR Cloud** | Streams Indicator of Compromise (IOC) detections to the Trellix EDR Cloud, along with other Trace data. You can disable this if you do not want IOC alerts sent to the cloud. | ### Process Tracker Configure the Process Tracker server component on the HX server before enabling the Process Tracker client component in ePO. | Option | Definition | | --- | --- | | **Enable Process Tracking on the host** | Enables the tracking of process events on the host. | ### Logon Tracker - Configure the Logon Tracker server component on the HX server before enabling the Logon Tracker client component in ePO. | Option | Definition | | --- | --- | | **Enable Logon Tracker for hosts** | Enables or disables the Logon tracker module on endpoints. When enabled, the agent monitors and collects the logon and logoff events. | | **Backfill events** | Instructs the agent to retrieve historical logon events from the endpoint's system logs upon initialization. This helps establish a baseline of logon activity that occurred before the module was activated. | | **Logon timeout** | Specifies the duration in minutes after which an active logon session is considered timed out due to inactivity. **Default**: 1440 minutes | | **Disable event enrichment** | Prevents the agent from adding supplementary contextual data (such as user details or group memberships) to the raw logon events. Disabling enrichment can reduce the size of the event data but provides less detailed information for analysis. | | **Maximum number of events** | Defines the maximum number of logon events the agent stores in its local cache. This setting helps manage memory and resource consumption on the endpoint. **Default**: 5000000 | - **Logon Tracker Exclusions** — Exclusions allow you to filter which logon events are tracked. Separate multiple items with a semicolon (;). | Option | Definition | | --- | --- | | **Addresses** | Excludes logon events associated with specified IPv4 or IPv6 addresses. | | **Hosts** | Excludes logon events from specified hostnames. | | **Accounts** | Excludes logon events from specified user or system accounts. | | **Categories** | Excludes specific logon categories. | | **Status** | Excludes specific logon statuses. | - **Filtering Options** | Option | Definition | | --- | --- | | **Filter Tunneled Logons** | Excludes logons that occur through a tunnel. |