Exclusion process cortex?!

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Exclusion process cortex?!

L3 Networker

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?

Best regards
Tiago Marques
1 accepted solution

Accepted Solutions

L4 Transporter

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.

 

jmazzeo_0-1709558611756.png

 

You can also go to Detecion Rules - IOC and add an IOC with the application path and/or executable hash (ni the "Type" field):

 

jmazzeo_1-1709559311916.png

 

Let me know how it goes.

 

If this post solved your question, please mark it as the solution.

 

JM

View solution in original post

1 REPLY 1

L4 Transporter

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.

 

jmazzeo_0-1709558611756.png

 

You can also go to Detecion Rules - IOC and add an IOC with the application path and/or executable hash (ni the "Type" field):

 

jmazzeo_1-1709559311916.png

 

Let me know how it goes.

 

If this post solved your question, please mark it as the solution.

 

JM
  • 1 accepted solution
  • 301 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!