- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-04-2024 05:04 AM
Hi,
How can I create an exclusion in
Cortex XDR
to stop it from scanning a specific executable??
We have a critical software in our company, and we've noticed that Cortex is constantly analyzing it, causing the machine high CPU and MEM.
How can we exclude this file from the analysis? We want to maintain protections such as Ransomware, just excluding the process monitoring.
It's possible?
03-04-2024 05:36 AM
Hi @tlmarques, thanks for reaching us using the Live Community.
You need to create a Disable Prevention Rule.
Go to Settings - Exceptions Configuration - Disable Prevention Rules, create a new one, set the name and fill the parameters:
- Set the target properties, folder location and executable name, command line, or you can use the signer. Only one is enough.
- Module: try with the Local Analysis and check how it goes, if it is an in-house software it is probably "Unknown" for Wildfire and the agent tries to analyze it locally, consuming CPU and RAM to do it.
- Scope: select the applied profile to the Endpoints with the issue.
You can also go to Detecion Rules - IOC and add an IOC with the application path and/or executable hash (ni the "Type" field):
Let me know how it goes.
If this post solved your question, please mark it as the solution.
03-04-2024 05:36 AM
Hi @tlmarques, thanks for reaching us using the Live Community.
You need to create a Disable Prevention Rule.
Go to Settings - Exceptions Configuration - Disable Prevention Rules, create a new one, set the name and fill the parameters:
- Set the target properties, folder location and executable name, command line, or you can use the signer. Only one is enough.
- Module: try with the Local Analysis and check how it goes, if it is an in-house software it is probably "Unknown" for Wildfire and the agent tries to analyze it locally, consuming CPU and RAM to do it.
- Scope: select the applied profile to the Endpoints with the issue.
You can also go to Detecion Rules - IOC and add an IOC with the application path and/or executable hash (ni the "Type" field):
Let me know how it goes.
If this post solved your question, please mark it as the solution.
03-14-2025 01:19 AM
Hi,
I found your response very insightful and helpful. I just have a question. How can I know which module to select when creating that prevention profile? In my case, it's also an in-house developed software which its developer reported performance issues. For example, should I select "Wildfire" and "Behavioral Threat Protection" together, or just one of them suffices? How can I find which module(s) is/are more relevant to this performance issue?
BR,
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!