nano SIEM
Case Management

Case Audit Events & SOC Metrics

Where case actions are recorded, how to review and search them, and where to get case metrics.

Review case audit events to find who created, assigned, updated, or merged a case. nano records the actor, case, and change in the platform audit log, which you can review, export, and search as OCSF events.

Where case audit lives

Case actions are recorded in the same audit log as every other platform action, stored in ClickHouse as OCSF API Activity (6003) events so you can search them.

SurfaceWhat you getPermission
Settings → Audit LogFilter by source, action, resource type, user, outcome and time rangeaudit:view
GET /api/auditThe same records over the API (/api/audit/actions and /api/audit/resource-types list the filter values)audit:view
POST /api/audit/exportExport audit records, up to 100,000 rowsaudit:view
SearchAudit events as OCSF API Activity with metadata.log_source=auditaudit:view

For platform-wide audit (settings, users, roles, API keys), see Platform audit logging.

Case audit actions

Case actions are recorded under the audit source case with these actions:

ActionWhen it's recorded
case_createdA case was created, by hand or by auto-grouping
case_updated, case_deletedA case was edited or deleted
case_assigned, case_escalatedA case was assigned or escalated
case_status_changed, case_bulk_status_changedStatus changes, one case or many
case_mergedCases were merged
case_alert_added, case_alert_removedAlerts linked or unlinked
case_updatedCase fields (title, description, severity and so on) changed
case_deletedA case was deleted
case_status_changedA case's status changed. Details include status, previous_status and disposition
case_bulk_status_changedStatuses were changed in bulk
case_assignedA case was assigned
case_escalatedA case was escalated
case_alert_addedAn alert was added to a case (by hand or by auto-grouping)
case_alert_removedAn alert was removed from a case
case_mergedCases were merged
case_sharedA case's sharing changed
case_handoff_sent, case_handoff_accepted, case_handoff_bounced, case_handoff_canceledCase handoffs between analysts
case_notebook_linked, case_notebook_unlinked, case_notebook_mergedNotebook link changes
case_settings_updated, case_grouping_rule_created, case_grouping_rule_updated, case_grouping_rule_deletedCase settings and grouping rules changed

Searching case audit events

Audit events are OCSF API Activity (6003) events. A case action has:

FieldValue
metadata.log_sourceaudit
api.service.namecase
api.operationThe action, for example case_status_changed
actor.user.name, actor.user.uidWho did it
status, status_idSuccess (1) or Failure (2)
src_endpoint.ip, http_request.user_agentClient address and user agent, when known
unmapped.resource_typecase
unmapped.resource_idThe case ID
unmapped.resource_nameThe case title, when recorded
unmapped.details.*The action's details. For case_status_changed: unmapped.details.status, unmapped.details.previous_status and unmapped.details.disposition

In order: case activity by action, who changed case statuses, everything that happened to one case, cases created per day, and failed case operations.

metadata.log_source=audit api.service.name="case" | stats count by api.operation | sort -count
metadata.log_source=audit api.operation="case_status_changed" | stats count by actor.user.name | sort -count
metadata.log_source=audit unmapped.resource_type="case" unmapped.resource_id="<case-id>" | table time, actor.user.name, api.operation, status
metadata.log_source=audit api.operation="case_created" | timechart span=1d count
metadata.log_source=audit api.service.name="case" status_id=2 | table time, actor.user.name, api.operation, src_endpoint.ip

Status transitions and dispositions are in the details. Values compare case-insensitively, so status="closed" also matches Closed. In order: status transitions by count, dispositions of closed cases, and who closed cases as false positives.

metadata.log_source=audit api.operation="case_status_changed" | stats count by unmapped.details.previous_status, unmapped.details.status | sort -count
metadata.log_source=audit api.operation="case_status_changed" unmapped.details.status="closed" | stats count by unmapped.details.disposition | sort -count
metadata.log_source=audit api.operation="case_status_changed" unmapped.details.disposition="FalsePositive" | stats count by actor.user.name | sort -count

Dispositions are recorded as TruePositive, FalsePositive, Benign, Inconclusive or Merged.

You need audit:view to see audit events in Search. Without it, metadata.log_source=audit returns no rows.

SOC metrics

For case metrics, use the case statistics endpoint:

GET /api/cases/stats

It returns the number of cases in each status, the number by severity, and the average resolution time in hours (avg_resolution_time_hours).

Case SLA targets (response, triage and resolution time per severity) are set in Settings → Case Management → SLA. The case list shows each case's SLA state.

From audit search you can also chart operational trends, such as case creations per day, status changes per analyst, or merges over time (see the queries above). To get notified on these trends, save a query as a detection rule or a scheduled report.

Best practices

  1. Baseline first. Measure for a few weeks before setting targets.
  2. Track trends, not absolutes. The direction of resolution time and backlog matters more than a single value.
  3. Segment by severity. Critical cases need different targets than low ones.
  4. Review regularly. Look at case volume, resolution time and analyst workload weekly.
  5. Export for reporting. Use POST /api/audit/export for audit evidence and GET /api/cases/stats for headline numbers.

Troubleshoot

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

Check the time range. A security-critical event whose ClickHouse write failed is retried in the background; SIEM Health reports the backlog.

Audit Search returns no rows

Check audit:view. Scheduled reports lack interactive audit-view context and return no rows for the internal audit source; review it interactively.

What's next

On this page