Incidents
An incident is a security event your organisation is handling, from the moment it is detected to the post-incident review. QuantAssure keeps one record per incident with its status, a timeline of what happened, the findings and compliance controls it relates to, and the notification details you may owe under the Notifiable Data Breaches (NDB) scheme.
Find incidents under Risk → Incidents.
To raise an incident from a finding, open the finding and choose Raise incident in its Related card. The form starts with the finding's title, description and severity (the AI-adjusted one); pick the incident type and create it. The finding is linked as Triggered By, and the finding's page lists its Linked incidents.
Incidents are never deleted, so the record stays intact for audit. When one is over, set its status to Closed.
The incident list
Four tiles summarise the whole organisation, whatever filters are set:
- Open Incidents: every incident that is not yet Resolved or Closed.
- Critical / High: open incidents of those two severities.
- MTTR (90d): the average time from discovery to resolution, in days, for incidents discovered in the last 90 days that have a resolved date.
- NDB Pending: incidents marked as needing an NDB assessment whose outcome is not yet recorded.
Search with Search incidents... and filter by Status,
Severity, Type and Assignee
(anyone in the organisation, Assigned to me or Unassigned). The sort options are
Discovered (Newest), Discovered (Oldest), Severity (Highest), Status and
Code. Each row shows the code (for example INC-001) and title,
the severity, the type, the status and the date discovered.
Statuses
An incident moves through eight statuses, following the usual response stages:
| Status | Meaning |
|---|---|
| Detected | The incident has been noticed and recorded. New incidents start here. |
| Assessing | You are working out what happened and how serious it is. |
| Containing | You are stopping it from spreading. Moving to this status fills in the Contained date if it is empty. |
| Eradicating | You are removing the cause. |
| Recovering | You are restoring normal service. |
| Review | The incident is over and you are reviewing the response. |
| Resolved | The incident is dealt with. Moving to this status fills in the Resolved date if it is empty, which is what MTTR is measured from. |
| Closed | The record is complete. |
You can move to any status from any other; there is no enforced order.
Severity and type
Severity is Critical, High, Medium or Low. The type is one of Data Breach, Service Disruption, Supply Chain, Unauthorised Access, Malware, Phishing, Physical, Policy Violation or Other. You choose both. Incident severity is your own judgement and is separate from the AI-adjusted severity on findings.
Recording an incident
People who can make changes (owners, admins and members) see New Incident. Viewers can read incidents but not change them. The form asks for a Title, a Severity (starts as Medium), a Type and the Date Discovered (starts as today), plus an optional Description. Choose Create Incident and you go straight to the new incident, which is given the next code and starts as Detected.
An incident's page
The header shows the code, severity, status, type, who it is assigned to (or Unassigned) and, if an NDB assessment is due, a countdown. Fields on the page save as you change them: a dropdown or checkbox saves immediately, and a text box saves when you click away. Saving... shows while it happens.
Main column
- Description and Scope & Impact: free text you can edit in place.
- Timeline: the incident's history, oldest first. Every status change adds an entry automatically. Use Add Event to record anything else: pick a Phase (Detection, Containment, Eradication, Recovery, Review, Notification, Escalation or Other), a Date & Time and a Description, then choose Add Event. Each entry shows who recorded it.
- Lessons Learned: appears once you tick Review Completed under Post-Incident Review.
-
Three tabs:
- Controls: compliance controls the incident bears on. Link Control lets you pick a control from any framework you target (shown as framework, code and title) with optional Notes. The table shows the framework, control, title, the control's current status and your notes.
- Findings: Link Finding ties in findings from your systems. Choose the finding and a Relationship: Triggered By (the finding led to the incident), Resulted In (the incident led to the finding) or Related. The table shows the finding with its effective severity (and the original scanner severity when the AI or a person changed it), its status and the relationship. The title opens the finding.
- Audit Log: every change made to the incident, with who and when.
Removing a link
The cross on a control or finding link does not delete it. QuantAssure asks for a reason (Void this control mapping? or Void this finding link?), then marks the link as voided. It disappears from the lists, and the reason is kept against the link, in the timeline and in the audit log, so a mistaken link remains accounted for.
Side column
- Status, Severity and Type: change any of them here.
- Key Dates: Occurred, Discovered, Reported, Contained and Resolved.
- Assigned To: any member of your organisation, or Unassigned.
- Response Activation: tick CIRP Activated (your cyber incident response plan), CIRT Convened (your response team), External Assistance Required and External Parties Notified. Record who was notified, and when, as Notification events on the timeline.
- External Ticket: the incident's Ticket ID, URL (an https link, which then shows an Open ticket link) and System, such as Jira or ServiceNow.
- NDB Assessment and Post-Incident Review, below.
- Metadata: when the incident was created and last updated, and its ID.
NDB assessment
If an incident may involve a data breach that must be reported under the Notifiable Data Breaches scheme, open the NDB Assessment card and tick Assessment Required. QuantAssure does not decide this for you, not even for the Data Breach type. Once ticked:
- A 30-day clock starts from the date discovered. The header shows NDB 12d remaining style countdowns, turning amber under two weeks and red under one, and NDB overdue once the 30 days have passed. The clock stops when you enter an Assessment Completed date.
- Record the Assessment Outcome: Eligible (Notifiable) or Not Eligible. Until you do, the incident counts under NDB Pending on the list.
- If the outcome is eligible, you can also record Notification Required, Commissioner Notified and Individuals Notified dates, and the text of your NDB Statement.
Post-incident review
Tick Review Completed under Post-Incident Review when your lessons-learned session is done. The Lessons Learned box then appears in the main column for your notes.
How incidents connect to the rest of QuantAssure
- Findings. You link findings to an incident from the incident. The finding's own page does not list its incidents.
- Compliance. Controls linked to an incident are drawn from your compliance frameworks.
- Audit log. Creating an incident, changing it and linking or voiding links are all in the audit log.
- AI clients. Incidents can be recorded and updated through AI client access as well.
- AI triage. No AI agent decides anything about an incident. Severity, status and the NDB outcome are always set by people.