--- title: "exploitDetection Section Settings" slug: "exploitdetection-section-settings-1" updated: 2026-09-08T19:19:55Z published: 2026-09-08T19:19:55Z canonical: "docs.trellix.com/exploitdetection-section-settings-1" --- > ## 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. # exploitDetection Section Settings [Skip to main content](/docs/exploitdetection-section-settings-1#content-wrapper) The `exploitDetection` settings provide keys that define how Exploit Guard is configured. Select a setting from the table below to go to the edit methods Trellix supports. Some of the settings listed in this table can also be changed [manually](/docs/modifying-the-configuration-file-for-a-single-endpoint-1) for an individual host by modifying the agent configuration file. | Setting Key | Default | Supported Edit Methods | | --- | --- | --- | | Web UI | CLI | API | | [alertThreshold](/docs/exploitdetection-section-settings-1#UUID-de4d7972-94a8-ea91-d9f8-467b898ff731) | --- | No | No | No | | [appList](/docs/exploitdetection-section-settings-1#UUID-1dbc2b8d-be59-e522-70c2-6ccfff87ddd3) | --- | No | No | No | | [enable_notification](/docs/exploitdetection-section-settings-1#UUID-5b4720a2-65fa-df0e-69f1-c4b3cefa6337) | false | Yes | No | Yes | | [enable_pageguard](/docs/exploitdetection-section-settings-1#UUID-9e194073-91c4-7d8d-6f76-b106674bb9ce) | true | No | No | No | | [enable_prevent_known](/docs/exploitdetection-section-settings-1#UUID-67d62f44-c214-17f1-e963-0ef159a9821e) | false | Yes | No | Yes | | [enable_production](/docs/exploitdetection-section-settings-1#UUID-9c54327e-1328-776a-da84-dae44c065849) | true | Yes | No | Yes | | [enable_protection](/docs/exploitdetection-section-settings-1#UUID-c697cfa7-bbce-2c5b-1cb4-f4bfe658fa05) | false | Yes | No | Yes | | [enable_server_os](/docs/exploitdetection-section-settings-1#UUID-e7b31788-c87f-067a-1f39-d4ac60b3ff73) | false | No | No | No | | [enable_termination](/docs/exploitdetection-section-settings-1#UUID-0c7a3e4d-a814-e3ac-16b7-5da6747006fc) | false | Yes | No | Yes | | [excludedFiles](/docs/exploitdetection-section-settings-1#UUID-e4c0f17c-9d30-9d65-1d08-ffb92da7dfbc) | --- | Yes | No | Yes | | [excludedMD5s](/docs/exploitdetection-section-settings-1#UUID-24410fb6-0871-42d8-d23d-61395f0b1cf5) | --- | Yes | No | Yes | | [excludedPaths](/docs/exploitdetection-section-settings-1#UUID-609d40d0-d13f-7813-ef74-4f3b27b351e9) | --- | Yes | No | Yes | | [rules_uri](/docs/exploitdetection-section-settings-1#UUID-e8dc5473-8b4d-6a00-192d-474e8245b5ad) | `/content/v1/intel/exd/rules` | No | No | No | | [traceLevel](/docs/exploitdetection-section-settings-1#UUID-6602b561-51b8-9277-72ef-aa0434c2016b) | --- | Yes | No | Yes | | [whitelist_uri](/docs/exploitdetection-section-settings-1#UUID-86360fe7-387f-e081-e1bd-c35a3718aee4) | `/content/v1/intel/exd/whitelist` | No | No | No | ##### alertThreshold Key The `alertThreshold` key sets an alert threshold used internally by Exploit Guard processing. ### Caution Do not change the value of this setting without the advice of your Trellix support representative. ##### appList Key The `appList` key lists the applications that are monitored by Exploit Guard. The applications that are monitored are Adobe Reader, Adobe Flash, Internet Explorer, Firefox, Google Chrome, Java, Microsoft Outlook, Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Office 2010 files. ### Caution Do not change the value of this setting without the advice of your Trellix support representative. ##### enable_notification Key The `enable_notification` key indicates whether the exploit prevention option to notify users when exploits are blocked has been enabled or not. Valid values are `true` (enabled) or `false` (disabled). The default is `false`. If the `enable_notification` key value is `true`, set the following key values to `true`: - ` enable_prevent _known Key ` - ` enable_production Key ` - ` enable_protection Key ` Change this setting using one of the following methods: - Web UI (see ) - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### enable_pageguard key Exploit Guard uses special detection heuristics to detect shellcode in its early stages. The `enable_pageguard` key indicates whether these special detection heuristics should be enabled for use in Exploit Guard processing. Valid values are `true` (enabled) or `false` (disabled). The default is `true`. ### Important Trellix Endpoint Security (HX) xAgent version 25 and later automatically disables PageGuard when the Windows kernel debug option is enabled. ### Note Enabling the DEBUG option in Windows BCDEDIT interferes with this processing. Trellix recommends that you turn the DEBUG option off before you upgrade to Trellix Endpoint Security (HX) xAgent version 24 or later. If that is not possible, Trellix recommends that you disable the `enable_pageguard` setting. Change this setting using one of the following methods: - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ### Caution Do not change the value of this setting without the advice of your Trellix support representative. ##### enable_prevent _known Key The `enable_prevent_known` key indicates whether exploits should be blocked by exploit prevention. Valid values are `true` (block exploits) or `false` (do not block exploits). The default is `false`. If the `enable_prevent_known` key value is `true`, set the following key values to `true`: - ` enable_production Key ` - ` enable_protection Key ` Change this setting using one of the following methods: - Web UI (see ). - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### enable_production Key The `enable_production` key indicates whether exploit detection has been enabled or not. Valid values are `true` (enabled) or `false` (disabled). The default is `true`. Change this setting using one of the following methods: - Web UI ( ). - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### enable_protection Key The `enable_protection` key indicates whether exploit prevention has been enabled or not. Valid values are `true` (enabled) or `false` (disabled). The default is `false`. If the `enable_protection` key value is `true`, the ` enable_production Key ` key value must also be `true`. Change this setting using one of the following methods: - Web UI (see ). - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### enable_server_os Key Use the `enable_server_os` key to enable or disable Exploit Guard processing for Windows server operating systems. Valid values are `true` (enabled) or `false` (disabled). The default is `false`. Change this setting using one of the following methods: - Web UI ([Enabling and Disabling Exploit Guard](/docs/enabling-and-disabling-exploit-guard-1) ). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### enable_termination Key The `enable_termination` key indicates whether the exploit prevention option to terminate monitored applications when exploits are detected has been enabled or not. Valid values are `true` (enabled) or `false` (disabled). The default is `false`. If the `enable_termination` key value is `true`, set the following key values to `true`: - ` enable_prevent _known Key ` - ` enable_production Key ` - ` enable_protection Key ` Change this setting using one of the following methods: - Web UI (see [Terminating Exploited Processes](/docs/enabling-and-disabling-exploit-prevention-1) ). - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### excludedFiles Key The `excludedFiles` key lists the files and folders to be excluded from Exploit Guard processing. This list of files and folders is part of the Exploit Guard global policy. There is no default. If no files or folders are listed, all files and folders are included in Exploit Guard processing. Files and folders should be listed within quotation marks (") and separated by commas. The full list of files should be enclosed in brackets ([]). For example: ``` "excludedFiles": [    "\\system32\\",    "\\FireEye\\xagt\\events.*" ] ``` ###### Exclusion Guidelines Follow these guidelines when adding file or folder path exclusions to the Exploit Guard exclusion list: Change this setting using one of the following methods: - Web UI (see ) - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### excludedMD5s Key The `excludedMD5s` key lists the MD5 hashes to be excluded from Exploit Guard processing. This list of MD5 hashes is part of the Exploit Guard global policy. There is no default. If no MD5 hashes are listed, all MD5 hashes are included in Exploit Guard processing. MD5 hashes should be listed as a sequence of 32 hexadecimal digits, within quotation marks ("), and separated by commas. The full list of files should be enclosed in brackets ([]). For example: ``` "excludedMD5s": [    "c8a9dab8f7cdec707eba6deca3448ba8",    "c2f5bbc927532092da5bfbb5ef839308" ] ``` ### Important The Endpoint Security (HX) server does not validate the MD5 hash entries included in your Exploit Guard exclusion list. You must confirm your MD5 hash exclusions are represented by 32 hexadecimal digits. Change this setting using one of the following methods: - Web UI (see ) - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### excludedPaths Key The `excludedPaths` key lists the executable files of applications that are monitored by Exploit Guard that should be excluded from Exploit Guard processing. This list of monitored applications is part of the Exploit Guard global policy configured in the [Agent Default Policy](/docs/xagent-policy-types-1). Applications that are monitored by Exploit Guard are Adobe Reader, Adobe Flash, Internet Explorer, Firefox, Google Chrome, Java, Microsoft Outlook, Microsoft Word, Microsoft Excel, and Microsoft PowerPoint There is no default. If no executable files are listed, all monitored applications are included in Exploit Guard processing. ### Important The [excludedPaths](/docs/exploitdetection-section-settings-1#UUID-609d40d0-d13f-7813-ef74-4f3b27b351e9) is the only value that will completely exclude a specific process. File paths should not be included in the excludedPaths list. The Endpoint Security (HX) server does not validate monitored application entries included in your Exploit Guard exclusion list. You must confirm your application exclusions are correct. Executable files should be listed within quotation marks (") and separated by commas. The full list of files should be enclosed in brackets ([]). For example: ``` "excludedPaths": [    "chrome.exe",    "iexplore.exe",    "firefox.exe" ] ``` Change this setting using one of the following methods: - Web UI (see ) - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### rules_uri key ### Caution Do not change the value of this setting without the advice of your Trellix support representative. The `rules_uri` key identifies the location of the rules file used during Exploit Guard processing. The default is `/content/v1/intel/exd/rules`. If you attempt to modify this setting using an API custom configuration channel, the API will automatically override it with the setting set up during Endpoint Security (HX) server and agent deployment. ##### traceLevel Key The `traceLevel` key sets a trace level used internally by Exploit Guard processing. This setting is set the same way the [log_level](/docs/logging-section-settings-1) setting is set in the [logging section](/docs/logging-section-settings-1). Change this setting using one of the following methods: - Web UI (see ). - API custom configuration channels (see [Using API Custom Configuration Channels](/docs/using-api-custom-configuration-channels-1)). - Manually on individual endpoints using a text editor (see [Modifying the Configuration File for a Single Endpoint](/docs/modifying-the-configuration-file-for-a-single-endpoint-1)). ##### whitelist_uri Key ### Caution Do not change the value of this setting without the advice of your Trellixsupport representative. The `whitelist_uri` key identifies the location of the whitelist file used during Exploit Guard processing. The default is `/content/v1/intel/exd/whitelist`. If you attempt to modify this setting using an API custom configuration channel, the API will automatically override it with the setting set up during Endpoint Security (HX) server and agent deployment. :