I'm running into this issue where some personnel do not want to add malicious hashes to the XDR block list as it will isolate the machine. As far as I can tell, adding a hash to the block list will only remove the file on execution or scan, leaving the rest of the machine completely alone.
Is anyone able to confirm or deny either arguments?
Hi @AhmedImran ,
Thank you for writing to live community!
Blocking the malicious hash will not isolate the endpoint unless you are leveraging Cortex XDR with some SIEM/SOAR tools which has a automated playbook/rule written to isolate the endpoint upon the trigger hit. By default Cortex XDR does not isolate endpoints on blocking hashes.
Also on the understanding for the removal of hashes executables upon detection, we do not remove/delete the file SHA256 added to block list(or otherwise as Wildfire malware verdict or Local Analysis malware verdict or both) upon detection, but only quarantine it. The quarantine will also happen if it has been configured on the malware profile in the endpoint prevention policy.
Hope this helps.
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!