nano SIEM
Case Management

Case Workflow

Supported in:Self-hosted

How cases are created, investigated, assigned, moved through statuses and closed.

Create, assign, investigate, and resolve cases to track an incident from its first signal to closure. Use the case workspace and investigation notebook to keep evidence and decisions together.

Case lifecycle

1. Case creation

Cases are created in two ways.

Automatic creation

When a detection rule in Alerting mode fires, nano:

  1. Extracts entities (users, hosts, IPs and more) from the alert's matched events. See Entities.
  2. Evaluates the enabled grouping rules in priority order.
  3. Adds the alert to an open case with the same grouping key, or creates a new case.
Detection fires → Extract entities → Evaluate grouping rules → Add to open case
                                                              ↳ or create a new case

Manual creation

Analysts can also create cases by hand:

  • Click New Case.
  • Press C on the case list.

2. Investigation

Opening a case shows the case workspace:

  • Signal inbox (left): your queue of cases and incoming signals.
  • Thread (center): the primary investigation surface. It shows the case header, the investigation timeline (searches, notes, AI analysis and case events) and a composer for notes and @ commands.
  • Evidence drawer (right): tabs for the case Playbook, open Questions, Entities and SLA.

Every case with an assigned analyst gets an investigation notebook, and the thread shows its entries. Case lifecycle events are mirrored into the notebook (see Case event mirroring).

3. Assignment

Assign a case from the case header or the case list (single or bulk). Through the API:

POST /api/cases/{id}/assign
{
  "assigned_to": "<user-id>"
}

Best practices:

  • Assign by analyst expertise and current workload.
  • Use the My Cases dashboard widget to track your assigned cases.
  • Use queues and routing rules (Settings → Queues & Routing) to route cases to the right team.

4. Status transitions

The usual path is Open → In Progress → (Pending) → Resolved → Closed, but a case can move between any two statuses, with these exceptions:

  • A Closed case can't move back to Resolved. Reopen it first.
  • A case that is already Resolved or Closed can't be set to the same status again.

Moving a Resolved or Closed case to Open, In Progress or Pending reopens it.

Change status from the case header, by dragging a card on the kanban board, or through the API:

POST /api/cases/{id}/status
{
  "status": "resolved",
  "disposition": "true_positive"
}
StatusWhen to use
Open (open)Initial state, awaiting triage
In Progress (in_progress)An analyst is actively investigating
Pending (pending)Waiting for external input, such as a user response or a vendor ticket
Resolved (resolved)Investigation complete
Closed (closed)Case fully addressed, no further action needed

5. Resolution and closure

When closing a case, assign a disposition:

DispositionDescriptionExample
True Positive (true_positive)Confirmed security incidentMalware execution confirmed on an endpoint
False Positive (false_positive)The detection fired incorrectlyA legitimate admin tool was flagged
Benign (benign)Real activity, not maliciousA scheduled vulnerability scan
Inconclusive (inconclusive)Cannot determine with certaintyLogs are insufficient for analysis

A case merged into another case gets the disposition Merged (merged).

Case views

Table view (default)

The table lists cases with their number (for example CASE-1234), title, severity, status, alert count, assignee, SLA state and last activity. You can sort, filter by status, severity and assignee, search case titles, and select cases for bulk status changes or bulk assignment.

Kanban view

Press V to switch to the kanban board. Each column is a status. Drag a card to another column to change the case's status, or click a card to open the case.

Investigation notebooks

Every case with an assigned analyst has an investigation notebook: one timeline of the investigation. See the Investigation notebooks guide for details.

When a case is assigned (or created with an assignee), nano creates a notebook linked to the case. The notebook captures:

  • Searches: queries run, results and time ranges
  • Notes: analyst observations and hypotheses
  • Entity references: IOCs, hosts, users and IPs tagged during the investigation
  • AI analysis: pivt queries, pivot suggestions and summaries
  • Case lifecycle events: status changes, assignments and merges

Case event mirroring

Case lifecycle events are mirrored into the notebook, so the thread is a single timeline.

EventMirrored asExample
Status changecase_event (status_change)"Case status changed from Open to In Progress"
Assignment changecase_event (assignment_change)"Case assigned to user alice"
Case mergecase_event (case_merged)"Merged 2 case(s): 5 alerts, 3 entities moved"

Mirrored events are included when pivt generates a summary, so summaries reflect the case lifecycle as well as the searches and notes.

AI summaries

When pivt generates an investigation summary (with @summarize, or when a case closes), it receives the case title, number, severity, status, disposition and description, so the summary can describe the outcome as well as the queries.

Legacy case wall

Cases created before notebook integration still show the legacy case wall. Once a notebook is linked to a case, the wall entries are hidden in favor of the notebook timeline. Wall data is kept and remains available through GET /api/cases/{id}/wall.

Best practices

  • Use notebook @ commands for structured entries (entities, IOCs, timeline markers).
  • Add notes that record your reasoning and hypotheses.
  • Run @summarize periodically during long investigations.
  • Don't document status changes by hand; they appear automatically.

nano links cases that share entities:

  • Cases that share 2 or more entities are linked as related.
  • Confidence grows with the number of shared entities.
  • Analysts can also link cases by hand. A manual link has full confidence.

Typical uses:

  • Campaigns: several cases that target the same infrastructure
  • Compromised accounts: cases involving the same user
  • Lateral movement: cases linked by shared hosts

API reference

List cases

GET /api/cases?status=open&severity=high&assigned_to=<user-id>&limit=50

Get case details

GET /api/cases/{id}

Create a case

POST /api/cases
{
  "title": "Suspicious PowerShell Activity",
  "description": "Multiple encoded PowerShell commands detected",
  "severity": "high"
}

Update a case

PUT /api/cases/{id}
{
  "title": "Updated title",
  "description": "Updated description"
}

Add an alert to a case

POST /api/cases/{id}/alerts
{
  "alert_id": "<alert-id>"
}

Case statistics

GET /api/cases/stats

Returns case counts by status and severity and the average resolution time in hours.

Get the case wall

GET /api/cases/{id}/wall
GET /api/cases/{id}/related

Troubleshoot

Need help with these checks? Contact support with the request ID and time with timezone.

A Closed case cannot become Resolved

Reopen it to Open, In Progress, or Pending first. nano also rejects setting an already Resolved or Closed case to the same status.

Old wall entries are hidden

A linked notebook becomes the case timeline. Existing wall data remains available through GET /api/cases/{id}/wall.

What's next

On this page