Cohesity Agent keeps triggering powershell alarm in cortex xdr

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cohesity Agent keeps triggering powershell alarm in cortex xdr

L0 Member

I have witelistet choesity agent but i keeps  trigger 

 

PowerShell script executing with iex from suspicious script source - Behavioral threat detected (rule: dotnet_iex_suspicious_source)
Sep 30th 2022 16:04:40 SYSTEM powershell.exe 25384 29488 Process Start Process Start Command Line : powershell -nologo -noninteractive -executionpolicy bypass -encodedcommand

 

is ther anyway to whiteliste this to so cohesity agent do not keeps getting  blockt

 

moversk_0-1664788133676.png

 

1 ACCEPTED SOLUTION

Accepted Solutions

L5 Sessionator

Hi @moversk ,

 

The reason this alert is persistent is because you have whitelisted the Cohesity SHA256 to the allow list. Cortex XDR Hash verdict and hash exception is a pre-execution detection and prevention mechanism, while the alert generated is a Behavioral Threat which is a post execution module. In order to allow the execution for the BTP events, the recommendation is to create alert exceptions for the same. I am listing down the practice steps for you down below: 

  1. Right click on the alert> Manage Alert> Create Alert Exception
  2. Choose the exception field parameters of your choice
  3. Choose the exception scope(
  4. for specific endpoints, you should have a exception profile created and mapped to those policy rules for those endpoints and choose "Profile", for global endpoints, choose "Global"
  5. Once created, right click on the alert > Retrieve Additional Data> Retrieve alert data. Action will be listed in the action center
  6. Wait for the alert data to be uploaded and download it from the action center
  7. Open a TAC case and report the event as false positive to be whitelisted in content updated
  8. Upon confirmation from the engineering team for this event to be whitelisted in the content, wait for the content update to be fetched to the endpoints and then remove the alert exception created initially.

Hope this answers your question.

View solution in original post

2 REPLIES 2

L5 Sessionator

Hi @moversk ,

 

The reason this alert is persistent is because you have whitelisted the Cohesity SHA256 to the allow list. Cortex XDR Hash verdict and hash exception is a pre-execution detection and prevention mechanism, while the alert generated is a Behavioral Threat which is a post execution module. In order to allow the execution for the BTP events, the recommendation is to create alert exceptions for the same. I am listing down the practice steps for you down below: 

  1. Right click on the alert> Manage Alert> Create Alert Exception
  2. Choose the exception field parameters of your choice
  3. Choose the exception scope(
  4. for specific endpoints, you should have a exception profile created and mapped to those policy rules for those endpoints and choose "Profile", for global endpoints, choose "Global"
  5. Once created, right click on the alert > Retrieve Additional Data> Retrieve alert data. Action will be listed in the action center
  6. Wait for the alert data to be uploaded and download it from the action center
  7. Open a TAC case and report the event as false positive to be whitelisted in content updated
  8. Upon confirmation from the engineering team for this event to be whitelisted in the content, wait for the content update to be fetched to the endpoints and then remove the alert exception created initially.

Hope this answers your question.

L0 Member

look like it still triggers even with  exception profile 1.JPG2.JPG

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!