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.
| Surface | What you get | Permission |
|---|---|---|
| Settings → Audit Log | Filter by source, action, resource type, user, outcome and time range | audit:view |
GET /api/audit | The same records over the API (/api/audit/actions and /api/audit/resource-types list the filter values) | audit:view |
POST /api/audit/export | Export audit records, up to 100,000 rows | audit:view |
| Search | Audit events as OCSF API Activity with metadata.log_source=audit | audit: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:
| Action | When it's recorded |
|---|---|
case_created | A case was created, by hand or by auto-grouping |
case_updated, case_deleted | A case was edited or deleted |
case_assigned, case_escalated | A case was assigned or escalated |
case_status_changed, case_bulk_status_changed | Status changes, one case or many |
case_merged | Cases were merged |
case_alert_added, case_alert_removed | Alerts linked or unlinked |
case_updated | Case fields (title, description, severity and so on) changed |
case_deleted | A case was deleted |
case_status_changed | A case's status changed. Details include status, previous_status and disposition |
case_bulk_status_changed | Statuses were changed in bulk |
case_assigned | A case was assigned |
case_escalated | A case was escalated |
case_alert_added | An alert was added to a case (by hand or by auto-grouping) |
case_alert_removed | An alert was removed from a case |
case_merged | Cases were merged |
case_shared | A case's sharing changed |
case_handoff_sent, case_handoff_accepted, case_handoff_bounced, case_handoff_canceled | Case handoffs between analysts |
case_notebook_linked, case_notebook_unlinked, case_notebook_merged | Notebook link changes |
case_settings_updated, case_grouping_rule_created, case_grouping_rule_updated, case_grouping_rule_deleted | Case settings and grouping rules changed |
Searching case audit events
Audit events are OCSF API Activity (6003) events. A case action has:
| Field | Value |
|---|---|
metadata.log_source | audit |
api.service.name | case |
api.operation | The action, for example case_status_changed |
actor.user.name, actor.user.uid | Who did it |
status, status_id | Success (1) or Failure (2) |
src_endpoint.ip, http_request.user_agent | Client address and user agent, when known |
unmapped.resource_type | case |
unmapped.resource_id | The case ID |
unmapped.resource_name | The 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.ipStatus 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 -countDispositions 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/statsIt 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
- Baseline first. Measure for a few weeks before setting targets.
- Track trends, not absolutes. The direction of resolution time and backlog matters more than a single value.
- Segment by severity. Critical cases need different targets than low ones.
- Review regularly. Look at case volume, resolution time and analyst workload weekly.
- Export for reporting. Use
POST /api/audit/exportfor audit evidence andGET /api/cases/statsfor headline numbers.
Troubleshoot
Need help with these checks? Contact support with the request ID and time with timezone.
An action appears in Audit Log but not Search
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.