Case Management
Group related alerts into cases, investigate them in one workspace, and track every case action in the audit log.
Group related alerts into cases so you can investigate an incident in one workspace. Detection alerts flow into cases automatically, bringing alerts, entities, and context together for triage and response.
Key features
Case-centric workflow
- Alerts flow into cases. Detection alerts are grouped into cases by configurable grouping rules.
- One investigation workspace. Related alerts, entities, the investigation timeline and the case playbook are in one view.
- AI-assisted triage. pivt can investigate new cases and summarize them. See Investigation notebooks.
Automatic alert grouping
- Group alerts by host, user, IP or detection rule.
- A time window controls how long a case keeps accepting new alerts.
- Host and user grouping are on by default. IP and rule grouping ship disabled.
Entity extraction
- Users, hosts, IPs, domains, hashes, URLs, files, processes and email addresses are extracted from each alert's matched events, using OCSF 1.9 field paths.
- An entity graph shows the case's entities by type.
- Pivot from any entity to Search, scoped to the case's time window.
Integrated investigation notebooks
- Every assigned case gets an investigation notebook.
- Case lifecycle events (status changes, assignments, merges) are mirrored into the notebook.
- The case thread is one timeline: searches, notes, AI analysis and case events.
Audit trail
- Every case action is written to the platform audit log. See Case audit events.
Case lifecycle
Open ──▶ In Progress ──▶ Pending ──▶ Resolved ──▶ Closed
▲ │
└──────────────────── Reopen ──────────────────────┘Case statuses
| Status | API value | Description |
|---|---|---|
| Open | open | New case awaiting investigation |
| In Progress | in_progress | An analyst is actively investigating |
| Pending | pending | Waiting for external input or action |
| Resolved | resolved | Investigation complete, disposition assigned |
| Closed | closed | Case fully closed |
Dispositions
When resolving or closing a case, analysts assign a disposition:
| Disposition | API value | Description |
|---|---|---|
| True Positive | true_positive | Confirmed security incident |
| False Positive | false_positive | The detection fired incorrectly |
| Benign | benign | Real activity, but not malicious |
| Inconclusive | inconclusive | Unable to determine with certainty |
| Merged | merged | Set on a case that was merged into another case |
Quick start
- View cases. Open Cases in the sidebar.
- Create a case. Click New Case or press
C. - Assign. Assign the case to an analyst. A notebook is created for the investigation.
- Investigate. Search, add notes and work the case's entities from the case workspace.
- Resolve. Set a disposition and close the case.
Keyboard shortcuts
On the case list:
| Shortcut | Action |
|---|---|
C | Create a new case |
V | Toggle table and kanban view |
R | Refresh cases |
/ | Focus search |
Esc | Clear the current selection |
Troubleshoot
Need help with these checks? Contact support with the request ID and time with timezone.
Related alerts create separate cases
Check the enabled grouping rules, entity fields, priority, time window, and alert cap. Follow the auto-grouping troubleshooting steps.
What's next
- Case workflow: lifecycle, status transitions and investigation notebooks
- Auto-grouping: configure automatic alert grouping rules
- Entities: entity extraction and the entity graph
- Case audit events: where case actions are recorded and how to review them
- Investigation notebooks: pivt notebooks,
@commands and case integration