Review a detection
Filter detections, understand why each one fired, and decide what to do. Give a verdict, create a case, dismiss it, or add an exception.
A detection is what a rule fires. ARGUNIS groups repetitions by rule, asset, and entity, so you see one row with how many times it occurred instead of a hundred identical rows. High and critical severity detections open a case automatically.
Before you start
View permission in Security (SIEM) to review; Operate to give verdicts, create cases, or dismiss; Administer to add exceptions.
Filter the list
Go to Security (SIEM) → Detections.
Use the filters: severity, status (Open, New, In case, Dismissed, Closed), rule origin (SigmaHQ, ARGUNIS, or Custom), period (Last 24 h, Last 7 days, Last 30 days), and the title search.
Check Only in observation to see what was fired by rules that don't notify yet, or Only retroactive to see what was found when searching past days.
In the sort order, choose Most recent or Cerebro priority.
Cerebro priority only sorts the inbox based on your company's experience: it never closes or hides a detection.
Read a detection
Click a row to open its details:
Why did it fire?: the rule's condition and the event source.
Why this severity?: the rule's base severity and what raised or lowered it (for example, the asset's criticality).
Times, Asset, Entities (user, IP, process…), and the ATT&CK techniques.
Known false positives declared by the rule's author.
Sample events: the real events that fired it.
If the detection is retroactive, it came from searching a rule or an indicator in the stored days: it didn't notify or open a case, so create one yourself if appropriate.
Decide what to do
Button | When to use it |
|---|---|
Create case | It deserves investigation and doesn't have a case yet |
Open the case | It's already in a case: takes you to it |
Verdict… | You already know what it was: Real (true positive), Real but expected (benign), or False positive, with an optional note |
Dismiss | Close it without a verdict. It doesn't feed Cerebro: if it was a false positive, better give the verdict |
Add exception… | Prevent that situation from firing the rule again, with a reason and expiration |
Suggest exception | Appears after a false positive verdict: builds the exception from the detection |
View in Explore | Open the event search around the detection |
The False positive verdict is valuable: with enough verdicts, Cerebro proposes exceptions so the rule stops bothering you on that asset. See Rule exceptions.