--- title: "Defining exploit guard protection exclusion policies" slug: "defining-exploit-guard-protection-exclusion-policies-1" updated: 2026-09-08T19:19:55Z published: 2026-09-08T19:19:55Z canonical: "docs.trellix.com/defining-exploit-guard-protection-exclusion-policies-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. # Defining exploit guard protection exclusion policies [Skip to main content](/docs/defining-exploit-guard-protection-exclusion-policies-1#content-wrapper) You may need to exclude specific files and folders, monitored applications (processes), and MD5 hashes from Exploit Guard processing on all of your host endpoints or selected host sets. You can use the Web UI or the API to define any of the following Exploit Guard policy exclusions: - Exclude all host sets or selected host sets from Exploit Guard processing, including both Exploit Guard detection and Exploit Guard prevention processing. - Exclude all host sets or selected host sets from Exploit Guard prevention processing only. - Exclude specific processes from Exploit Guard processing for all host endpoints or selected host sets. - Exclude specific file executables from Exploit Guard processing for all host endpoints or selected host sets. - Exclude specific MD5 hashes from Exploit Guard processing for all host endpoints or selected host sets. ### Important Exploit Guard process, file, folder, and MD5 hash exclusions are supported on Windows agents version 22 and later only. Excluding host sets, processes, files and folders, or MD5 hashes from Exploit Guard processing is not recommended because it restricts the items that Exploit Guard protects. Exploit Guard file, folder, or process exclusions defined in the xAgent default policy do not apply to host sets assigned to a custom policy, if the custom policy defines different Exploit Guard policy settings. To exclude files, folders, and processes for third-party antivirus software installed on your host endpoints, you must define these exclusions for all policies that include an Exploit Guard policy. Prerequisites - Admin access when using the Web UI - Endpoint Security (HX) xAgent version 22 or later installed on your Windows endpoint. If an xAgent for an earlier xAgent version is included in a host set that is managed by a policy, the policy is ignored for that xAgent . This section covers the following topics: - [Exploit Guard Exclusion Guidelines](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-e3970217-0108-55c2-dd96-559cf9ba0e83) - [Excluding Monitored Applications from Exploit Guard Processing](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-a3463922-0c0f-81a8-d4d6-16c1b583a975) - [Excluding Files and Folders from Exploit Guard Processing](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-2b63b6ce-1903-4b02-aed3-c9ed6bed1976) - [Excluding MD5 Hashes from Exploit Guard Processing](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-033f7bc0-785c-123a-7b24-0e77e5a9b349) ##### Exploit Guard exclusion guidelines Follow these guidelines when adding files and folders, applications (processes), and MD5 hashes to the Exploit Guard exclusion list: - There are three possible values that you can exclude from Exploit Guard processing: excludedFile, excludedPaths, and excludedMD5. | Exclusion Value | Description | | --- | --- | | excludedFile | This value excludes specific files or folders from Exploit Guard alerting and action. Exploit Guard still monitors listed files. File and folder exclusions apply to file write events only. | | excludedPaths | This value completely excludes the name of the binary file (.exe) from Exploit Guard monitoring. List the executable file associated with monitored application you want to exclude from Exploit Guard processing only. File paths should not be included in the excludedPaths list. ### Important The [excludedPaths](/docs/exploitdetection-section-settings-1) is the only value that will completely exclude a specific process. ### Note [excludedPaths](/docs/exploitdetection-section-settings-1) controls what is displayed in Monitored Applications. | | excludedMD5 | This value excludes MD5 hashes from Exploit Guard processing. MD5 hashes should be listed as a sequence of 32 hexadecimal digits. Exploit Guard will continue to monitor and detect malicious MD5 hashes but you will not receive alerts when the xAgent detects malicious actions. ### 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. | - Environment variables are not supported. - Wildcard characters are not supported. The following table lists examples for excluding files and folders from Exploit Guard processing. Reference these examples when adding your file and folders exclusion list. | Exclusion Method | Exclusion Example | | --- | --- | | Exclude a specific file name. | `myfile` | | Exclude a specific file name located in a specific directory. | `C:\Users\Admin\Documents\myfile.txt` | | Exclude all files in a specific directory. | `C:\Users\Admin\Documents` | | Exclude all files and sub directories in a specific directory. | `C:\Users\Admin\Documents\` | ##### Excluding monitored applications from Exploit Guard processing You can add and remove a list of monitored applications (processes) that you want to exclude from Exploit Guard processing. Excluding an application for Exploit Guard processing prevents Exploit Guard from monitoring the application or performing other Exploit Guard activities, including application termination. If an exploit occurs on the excluded application, you will not receive an alert. Applications that are monitored for exploits are Adobe Reader, Adobe Flash, Internet Explorer, Firefox, Google Chrome, Java, Microsoft Outlook, Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Office 2010 files. ### Important Exploit Guard monitored application exclusions are supported on Windows agents version 22 and later only. Excluding monitored applications from Exploit Guard processing is not recommended because it restricts the monitored applications that Exploit Guard protects. Exploit Guard process exclusions defined in the apply to all host endpoints in your enterprise except for host endpoints assigned to a custom policy that includes an Exploit Guard policy. This section covers how to use the Web UI to manage an monitored applications list for Exploit Guard processing. See the *Endpoint Security (HX) REST API Guide* for more information about managing monitored application exclusions using the API. - [Adding Monitored Application List Exclusions](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-35f421f4-8896-1f6d-d55a-92542d967ab6) - [Removing Monitored Application List Exclusions](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-9788343d-2fa9-47e3-e8dc-3844aee3d024) ###### Adding monitored application list exclusions You can add a list of monitored applications you want to exclude from Exploit Guard processing (both exploit detection and exploit prevention) using the Web UI or the API. ### Important The [excludedPaths](/docs/exploitdetection-section-settings-1) 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. To add monitored application exclusions for all host endpoints: 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the **Agent Default Policy** link to access the **Edit Policy** page. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, specify the executable file name of a monitored application (process) you want to exclude from Exploit Guard processing in the field under the **Exclude monitored applications from Exploit Guard**. For example, adding `chrome.exe` to the exclusion list will exclude Chrome from Exploit Guard processing. 6. Click **Add** to add the monitored application to the list. 7. Repeat Steps 5 and 6 until you have added all the monitored applications you want to the list. 8. Click **Save**. To add monitored application exclusions for selected host sets: ### Note [NOTE: See Creating a Custom Policy](/docs/creating-a-custom-policy-1) for more information about using the Web UI to create a custom policy. 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the link for the custom policy you want to modify. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, specify the name of a monitored application you want to exclude from Exploit Guard processing in the field under the **Exclude monitored applications from Exploit Guard**. 6. Click **Add** to add the monitored application to the list. 7. Repeat Steps 5 and 6 until you have added all the monitored applications you want to the list. 8. Click **Save**. Now you can assign host sets to the custom policy and set the policy priority level. See [Assigning Host Sets to Agent Policies](/docs/assigning-host-sets-to-xagent-policies-1) and [Configuring Policy Priority Using the Web UI](/docs/policy-prioritization-1) for more information. ###### Removing monitored application list exclusions To remove an application (process) from the Exploit Guard exclusions list for all host endpoints: 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the **Agent Default Policy** link to access the **Edit Policy** page. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, select the executable file of the application (process) you want to remove from the list below the **Exclude monitored applications from Exploit Guard** option. 6. Click the ![Policy_MalProtect_Delete_Icon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9626277d-76da-3e46-7af2-51162e685a56(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A03%3A16Z&se=2026-11-22T14%3A03%3A16Z&sr=c&sp=r&sig=v%2BXOkPEE5Khi5%2BGUL1fATiPQqR0bTR1O%2BxR3FHZS1s4%3D) icon next to the process you want to remove from the list. 7. Repeat Steps 5 and 6 until you have removed all of the monitored applications you want to delete from the list. 8. Click **Save**. To remove an application (process) from the Exploit Guard exclusions list for selected host sets: ### Note When you disable a setting in a custom policy, the setting is disabled for all host sets assigned to the policy. If you want select host sets to keep the original setting, you must create a new custom policy with the setting enabled and assign it to the selected host sets. [See Creating a Custom Policy](/docs/creating-a-custom-policy-1) for more information about using the Web UI to create a custom policy. 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the **Policies** table, click the link for the custom policy you want to modify. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, select the process you want to remove from the list below the **Exclude monitored applications from Exploit Guard** option. 6. Click the ![Policy_MalProtect_Delete_Icon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9626277d-76da-3e46-7af2-51162e685a56(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A03%3A16Z&se=2026-11-22T14%3A03%3A16Z&sr=c&sp=r&sig=v%2BXOkPEE5Khi5%2BGUL1fATiPQqR0bTR1O%2BxR3FHZS1s4%3D) icon next to the process you want to remove from the list. 7. Repeat Steps 5 and 6 until you have removed all of the monitored applications you want to delete from the list. 8. Click **Save**. ##### Excluding files and folders from Exploit Guard processing You can exclude a list of executable files and folders from Exploit Guard processing for all your host endpoints or selected host sets in your environment. Exploit Guard still monitors your excluded files and folders but you will not receive an alert if an exploit occurs on an excluded file or folder. In addition, Exploit Guard activities, including application termination, do not occur on the excluded file or folder. ### Important Exploit Guard file and folder exclusions are supported on Windows agents version 22 and later only. Excluding files and folders from Exploit Guard processing is not recommended because it restricts the items that Exploit Guard protects. Exploit Guard file and folder exclusions defined in the apply to all host endpoints in your enterprise except for host endpoints assigned to a custom policy that includes an Exploit Guard policy. This section covers how to use the Web UI to manage a file and folder exclusion list for Exploit Guard processing. See the *Endpoint Security (HX) REST API Guide* for more information about managing Exploit Guard file and folder exclusions. - [Adding File and Folder Exclusions](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-3727594f-4517-0ce6-30f5-80b47f723b22) - [Removing File and Folder Exclusions](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-fdb15037-2963-670f-78a5-7bbf80424cb0) ###### Adding file and folder exclusions - File and folder exclusions apply to file write events only. - Environment variables are not supported. - Wildcard characters are not supported. The following table lists examples for excluding files and folders from Exploit Guard processing. Reference these examples when adding files and folders to your Exploit Guard file and folder exclusion list. | Exclusion Method | Exclusion Example | | --- | --- | | Exclude a specific file name. | `myfile` | | Exclude a specific file name located in a specific directory. | `C:\Users\Admin\Documents\myfile.txt` | | Exclude all files in a specific directory. | `C:\Users\Admin\Documents` | | Exclude all files and sub directories in a specific directory. | `C:\Users\Admin\Documents\` | To add file and folder exclusion list for all of your host endpoints: 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the **Agent Default Policy** link to access the **Edit Policy** page. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, specify the file or folder path you want to exclude from Exploit Guard processing in the field under the **Exclude files and folders from Exploit Guard**. 6. Click **Add** to add the file or folder path to the list. 7. Repeat Steps 5 and 6 until you have added all the files and folders you want to the list. 8. Click **Save**. To add file and folder exclusions for selected host sets: ### Note [NOTE: See Creating a Custom Policy](/docs/creating-a-custom-policy-1) for more information about using the Web UI to create a custom policy. 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the link for the custom policy you want to modify. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, specify the file or folder path you want to exclude from Exploit Guard processing in the field under the **Exclude files and folders from Exploit Guard**. 6. Click **Add** to add the file or folder path to the list. 7. Repeat Steps 5 and 6 until you have added all the files and folders you want to the list. 8. Click **Save**. Now you can assign host sets to the custom policy and set the policy priority level. See [Assigning Host Sets to Agent Policies](/docs/assigning-host-sets-to-xagent-policies-1) and [Configuring Policy Priority Using the Web UI](/docs/policy-prioritization-1) for more information. ###### Removing file and folder exclusions ###### To remove file and folder exclusions for all host endpoints: 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the **Agent Default Policy** link to access the **Edit Policy** page. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, select the file and folder you want to remove from the list below the **Exclude files and folders from Exploit Guard** option. 6. Click the ![Policy_MalProtect_Delete_Icon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9626277d-76da-3e46-7af2-51162e685a56(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A03%3A16Z&se=2026-11-22T14%3A03%3A16Z&sr=c&sp=r&sig=v%2BXOkPEE5Khi5%2BGUL1fATiPQqR0bTR1O%2BxR3FHZS1s4%3D) icon next to the file and folder you want to remove from the list. 7. Repeat Steps 5 and 6 until you have removed all of the files and folders you want to delete from the list. 8. Click **Save**. To remove file and folder exclusions for selected host sets: ### Note When you disable a setting in a custom policy, the setting is disabled for all host sets assigned to the policy. If you want select host sets to keep the original setting, you must create a new custom policy with the setting enabled and assign it to the selected host sets. [See Creating a Custom Policy](/docs/creating-a-custom-policy-1) for more information about using the Web UI to create a custom policy. 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the link for the custom policy you want to modify. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, select the file and folder you want to remove from the list below the **Exclude files and folders from Exploit Guard** option. 6. Click the ![Policy_MalProtect_Delete_Icon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9626277d-76da-3e46-7af2-51162e685a56(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A03%3A16Z&se=2026-11-22T14%3A03%3A16Z&sr=c&sp=r&sig=v%2BXOkPEE5Khi5%2BGUL1fATiPQqR0bTR1O%2BxR3FHZS1s4%3D) icon next to the file and folder you want to remove from the list. 7. Repeat Steps 5 and 6 until you have removed all of the files and folders you want to delete from the list. 8. Click **Save**. ##### Excluding MD5 hashes from Exploit Guard processing You can add and remove a list of excluded MD5 hashes in the Exploit Guard global policy using the Web UI or the API. Excluding an MD5 hash from Exploit Guard processing does not prevent Exploit Guard from monitoring the MD5 hash. Monitoring still occurs but you will not receive any alerts or other Exploit Guard activities, including application termination, if an exploit does occur for the excluded MD5 hash. ### Important Exploit Guard MD5 hash exclusions are supported on Windows agents version 22 or later only. Excluding MD5 hashes from Exploit Guard processing is not recommended because it restricts the MD5 hashes that Exploit Guard protects. Exploit Guard MD5 hash exclusions defined in the apply to all host endpoints in your enterprise except for host endpoints assigned to a custom policy that includes an Exploit Guard policy. This section covers how to use the Web UI to manage an MD5 hash exclusion list for Exploit Guard processing. See the Endpoint Security (HX) REST API Guide for more information about managing MD5 hash exclusions. - [Adding MD5 Hash Exclusions](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-275ea2e6-fef9-a95e-df24-8c36478f3311) - [Removing MD5 Hash Exclusions](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-cc436852-8f72-61f1-a919-d57967f3c6df) - [Managing Exception Policy MD5 Hash Exclusions](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-c984120c-51bf-3c1d-b73a-b572614c8e50) - [Enabling and Disabling the Exception Policy Excluded MD5 Hash List](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-27e37ee4-e9f5-b46b-2425-56360f7952e7) - [Maintaining the Exception Policy Excluded MD5 Hash List](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-c66b76f0-52de-2a82-c026-77fd91d17179) ###### Adding MD5 hash exclusions You can add a list of MD5 hashes to exclude from Exploit Guard processing using the Web UI or the API. ### 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. To add MD5 hash exclusions for all host endpoints: 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the **Agent Default Policy** link to access the **Edit Policy** page. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, specify the MD5 hash you want to exclude from Exploit Guard processing in the field under the **Exclude MD5 hashes from Exploit Guard**. 6. Click **Add** to add the MD5 hash to the list. ### Important The Endpoint Security (HX) server and the xAgent do not validate the correct entry of the MD5 hashes included in your exclusion list. Confirm that your MD5 hash exclusions are represented by 32 hexadecimal digits. 7. Repeat Steps 5 and 6 until you have added all of the MD5 hash exclusions you want to the list. 8. Click **Save**. To add MD5 hash exclusions for selected host sets: ### Note [See Creating a Custom Policy](/docs/creating-a-custom-policy-1) for more information about using the Web UI to create a custom policy. 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the link for the custom policy you want to modify. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, specify the MD5 hash you want to exclude from Exploit Guard processing in the field under the **Exclude MD5 hashes from Exploit Guard**. 6. Click **Add** to add the MD5 hash to the list. ### Important The Endpoint Security (HX) server and the xAgent do not validate the correct entry of the MD5 hashes included in your exclusion list. Confirm that your MD5 hash exclusions are represented by 32 hexadecimal digits. 7. Repeat Steps 5 and 6 until you have added all of the MD hash exclusions you want to the list. 8. Click **Save**. Now you can assign host sets to the custom policy and set the policy priority level. See [Assigning Host Sets to Agent Policies](/docs/assigning-host-sets-to-xagent-policies-1) and [Configuring Policy Priority Using the Web UI](/docs/policy-prioritization-1) for more information. ###### Removing MD5 hash exclusions ###### To remove MD5 hash exclusions for all host endpoints: 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the **Agent Default Policy** link to access the **Edit Policy** page. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, select the MD5 hash you want to remove from the list below the **Exclude MD5 hashes from Exploit Guard** option. 6. Click the ![Policy_MalProtect_Delete_Icon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9626277d-76da-3e46-7af2-51162e685a56(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A03%3A16Z&se=2026-11-22T14%3A03%3A16Z&sr=c&sp=r&sig=v%2BXOkPEE5Khi5%2BGUL1fATiPQqR0bTR1O%2BxR3FHZS1s4%3D) icon next to the MD5 hash you want to remove from the list. 7. Repeat Steps 5 and 6 until you have removed all of the MD5 hash exclusions you want from the list. 8. Click **Save**. To remove MD5 hash exclusions for selected host sets: ### Note When you disable a setting in a custom policy, the setting is disabled for all host sets assigned to the policy. If you want select host sets to keep the original setting, you must create a new custom policy with the setting enabled and assign it to the selected host sets. [See Creating a Custom Policy](/docs/creating-a-custom-policy-1) for more information about using the Web UI to create a custom policy. 1. Log in to the Web UI as an administrator. 2. From the **Admin** menu, select **Policies** to access the **Policies** page. 3. In the Policies table, click the link for the custom policy you want to modify. 4. Select the **Exploit Guard Protection** tab. 5. In the **Policy Exclusions** section, select the MD5 hash you want to remove from the list below the **Exclude MD5 hashes from Exploit Guard** option. 6. Click the ![Policy_MalProtect_Delete_Icon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9626277d-76da-3e46-7af2-51162e685a56(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A03%3A16Z&se=2026-11-22T14%3A03%3A16Z&sr=c&sp=r&sig=v%2BXOkPEE5Khi5%2BGUL1fATiPQqR0bTR1O%2BxR3FHZS1s4%3D) icon next to the MD5 hash you want to remove from the list. 7. Repeat Steps 5 and 6 until you have removed all of the MD5 hash exclusions you want from the list. 8. Click **Save**. ###### Managing Exception Policy MD5 hash exclusions You can enable and maintain the list of excluded MD5 hashes in the Exploit Guard exception policy using the Web UI or the CLI. - [Enabling and Disabling the Exception Policy Excluded MD5 Hash List](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-27e37ee4-e9f5-b46b-2425-56360f7952e7) - [Maintaining the Exception Policy Excluded MD5 Hash List](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-c66b76f0-52de-2a82-c026-77fd91d17179) ### Note Excluding MD5 hashes from Exploit Guard processing is not recommended because it restricts the MD5 hashes that Exploit Guard protects. The MD5 hash exclusion is only supported on hosts using Trellix Endpoint Security (HX) xAgent version 22 or later. ###### Enabling and disabling the Exception Policy excluded MD5 hash list The list of excluded MD5 hashes in the Exploit Guard exception policy can be enabled and disabled using the Web UI or the CLI. When it is enabled, the MD5 hashes in the list are excluded from Exploit Guard processing (both exploit detection and exploit prevention) for the host sets selected in the exception policy. - [Enabling the List Using the Web UI](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-27e37ee4-e9f5-b46b-2425-56360f7952e7_id_enabling) - [Enabling the List Using the CLI](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-27e37ee4-e9f5-b46b-2425-56360f7952e7_id_enabling1) - [Disabling the List Using the Web UI](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-27e37ee4-e9f5-b46b-2425-56360f7952e7_id_disabling) - [Disabling the List Using the CLI](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-27e37ee4-e9f5-b46b-2425-56360f7952e7_id_disabling1) ###### Enabling the list using the web UI ###### To enable the exception policy excluded MD5 hash list using the Web UI: 1. Log in to the Web UI as an administrator. 2. Access the Policies page by selecting **Policies** on the **Admin** menu. 3. Select the **Exploit Guard** tab. 4. In the **Exceptions for Selected Host Sets** section, select the **Exclude MD5 hashes from Exploit Guard for the selected host sets** option. 5. In the field below this option, specify MD5 hashes that should be excluded from Exploit Guard processing for the exception policy. See [Maintaining the MD5 Hash List for the Exploit Guard Exception Policy](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-c66b76f0-52de-2a82-c026-77fd91d17179) . 6. Click **Save**. ###### Enabling the list using the CLI ###### To enable the exception policy excluded MD5 hash list using the CLI: 1. On the HX Server, enable CLI configuration mode: `hostname > enable` `hostname # configure terminal` 2. Enable the excluded MD5 hash list in the Exploit Guard exception policy: `hostname (config) # hx config agent exd exceptions whitelist MD5 enable` 3. Save your changes: ``` hostname (config) # write memory ``` ###### Disabling the list Using the web UI ###### To disable the exception policy excluded MD5 hash list using the Web UI: 1. Log in to the Web UI as an administrator. 2. Access the Policies page by selecting **Policies** on the **Admin** menu. 3. Select the **Exploit Guard** tab. 4. In the **Exceptions for Selected Host Sets** section, clear the **Exclude MD5 hashes from Exploit Guard for the selected host sets** option. 5. Click **Save**. ###### Disabling the list using the CLI ###### To disable the exception policy excluded MD5 hash list using the CLI: 1. On the HX Server, enable CLI configuration mode: `hostname > enable` `hostname # configure terminal` 2. Disable the excluded MD5 hash list in the Exploit Guard exception policy: `hostname (config) # no hx config agent exd exceptions whitelist MD5 enable` 3. Save your changes: ``` hostname (config) # write memory ``` ###### Maintaining the exception policy excluded MD5 hash list Using the Web UI or the CLI, you can add and remove MD5 hashes in the Exploit Guard exception policy exclusion list. - [Adding Excluded MD5 Hashes Using the Web UI](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-c66b76f0-52de-2a82-c026-77fd91d17179_id_adding) - [Adding Excluded MD5 Hashes Using the CLI](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-c66b76f0-52de-2a82-c026-77fd91d17179_id_adding2) - [Removing Excluded MD5 Hashes Using the Web UI](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-c66b76f0-52de-2a82-c026-77fd91d17179_id_removing) - [Removing Excluded MD5 Hashes Using the CLI](/docs/defining-exploit-guard-protection-exclusion-policies-1#UUID-c66b76f0-52de-2a82-c026-77fd91d17179_id_removing2) ### Note Use of an Exploit Guard exception policy is not recommended. ###### Adding excluded MD5 hashes using the web UI To add MD5 hashes to the exception policy exclusion list using the Web UI: ### Important The HX Server does not validate the correct entry of the MD5 hashes included in your exclusion list. Confirm that your MD5 hash exclusions are represented by 32 hexadecimal digits. 1. Log in to the Web UI as an administrator. 2. Access the Policies page by selecting **Policies** on the **Admin** menu. 3. Select the **Exploit Guard** tab. 4. In the **Exceptions for Selected Host Sets** section, verify that the **Exclude MD5 hashes from Exploit Guard for the selected host sets** option is selected. 5. In the field under the **Exclude MD5 hashes from Exploit Guard for the selected host sets** option, specify the MD5 hash of the file you want to exclude from Exploit Guard processing for the endpoints in the host sets selected for the exception policy. 6. Click **Add** to add the MD5 hash to the list. 7. Repeat Steps 5 and 6 until you have added all the MD5 hashes you want to the list. 8. Click **Save**. ###### Adding excluded MD5 hashes using the CLI To add MD5 hashes to the exception policy exclusion list using the CLI: 1. On the HX Server, enable CLI configuration mode: `hostname > enable` `hostname # configure terminal` 2. Add an MD5 hash to the Exploit Guard exception policy: `hostname (config) # hx config agent exd exceptions whitelist md5 values <hash>` For `<hash>`, specify the MD5 hash of the file you want to exclude from Exploit Guard processing for the endpoints in the host sets selected for the exception policy. 3. Repeat Step 2 until you have added all the MD5 hashes you want to the list. 4. Save your changes: ``` hostname (config) # write memory ``` ###### Removing excluded MD5 hashes using the web UI To remove MD5 hashes from the exception policy exclusion list using the Web UI: 1. Log in to the Web UI as an administrator. 2. Access the Policies page by selecting **Policies** on the **Admin** menu. 3. Select the **Exploit Guard** tab. 4. In the **Exceptions for Selected Host Sets** section, locate the MD5 hash you want to remove from the list below the **Exclude MD5 hashes from Exploit Guard for the selected host sets** option. 5. Click the ![HX_RemoveIcon.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-b0d7c9c3-9356-c648-13f4-1dd2a52bd2a6(2).png?sv=2026-02-06&spr=https&st=2026-11-22T13%3A03%3A16Z&se=2026-11-22T14%3A03%3A16Z&sr=c&sp=r&sig=v%2BXOkPEE5Khi5%2BGUL1fATiPQqR0bTR1O%2BxR3FHZS1s4%3D) icon next to the MD5 hash to remove it from the list. 6. Repeat Step 5 until you have removed all the MD5 hashes you want from the list. 7. Click **Save**. ###### Removing excluded MD5 hashes using the CLI To remove MD5 hashes from the exception policy exclusion list using the CLI: 1. On the HX Server, enable CLI configuration mode: `hostname > enable` `hostname # configure terminal` 2. List the MD5 hashes in the Exploit Guard exception policy: `show hx server exd` The MD5 hashes listed under **Exclude MD5 hashes from Exploit Guard** in the output of this command are the MD5 hashes included in the exception policy. 3. Remove an MD5 hash from the Exploit Guard exception policy: `hostname (config) # no hx config agent exd exceptions whitelist md5 values <index#>` For `<index#>`, specify the path number of the MD5 hash you want to remove. 4. Repeat Step 3 until you have removed all the MD5 hashes you want from the list. 5. Save your changes: ``` hostname (config) # write memory ``` :