You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have started seeing false positives for this rule, by crashpad_handler.exe where target.process.entity_id is the same as process.entity_id - We experience this from different software, on different hosts. I don't know why we suddenly started seeing these, nor do I know if this is normal behavior of crashpad_handler.exe
I have attached the alert.json output of one of the alerts
Desktop (please complete the following information):
OS: Windows
Version: Windows 10 Pro 22H2 (10.0.19045.4780), Windows 11 Pro 23H2 (10.0.22631.4037)
The text was updated successfully, but these errors were encountered:
@FideliusFalcon thank you for reporting this, we are already aware of this false positive (and others related to 3rd party crash handlers that causes the remote suspension of a thread or process in order to handle the crash). we have planned updates next week (Sep 17 Tuesday), for now you can create an endpoint exception : process.thread.Ext.call_stack_final_user_module.hash.sha256 == 76d338198d607ac1432157b18f85367f402b5404983a2c9ca071062e4dcdba33 (and any other hashes if there are many for crashpad_handler.exe):
Describe the bug
We have started seeing false positives for this rule, by crashpad_handler.exe where target.process.entity_id is the same as process.entity_id - We experience this from different software, on different hosts. I don't know why we suddenly started seeing these, nor do I know if this is normal behavior of crashpad_handler.exe
I have attached the alert.json output of one of the alerts
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: