GuideChecked 16 November 2026
Incident response severity levels
What severity levels should an incident response plan use?
Use four levels: low, medium, high and critical. Define each by business impact, name who is called, and set a response target. Re-rate when facts change. NIST CSF outcome RS.MA-03 reads: incidents are categorized and prioritized, and DE.AE-04 says the estimated impact and scope of adverse events are understood.
| Level | Criteria | Who is called |
|---|---|---|
| 1 Low | One user or device; no sensitive data exposed; no service affected | Incident lead |
| 2 Medium | More than one user or device, or a non-critical service affected | Incident lead, technical lead |
| 3 High | A critical service down, or sensitive data may be exposed | All roles and legal counsel |
| 4 Critical | Wide loss of service, confirmed regulated data exposure, or a safety threat | All roles, executive sponsor, outside responders |
How does impact set the level?
The SANS Incident Handler's Handbook gives an example: a single workstation being non-functional can be considered minor, a server being down could be moderate if there are backups for failover, and data stolen directly from human resources that contains privileged information could be high. It adds that ranking incident types by organizational impact helps build the case for management support.
Add data sensitivity and legal duties to the criteria; a small breach of regulated data can be higher severity than a large outage.
When should severity trigger escalation?
NIST CSF outcome RS.MA-04 reads "Incidents are escalated or elevated as needed". The NCSC advises establishing criteria for escalation to senior management and for scaling up the response, based on what matters most to your organization.
The template section 4 carries the table; the roles page shows who is called.
Related pages
- Incident response plan: what it contains and how to build one
- Free incident response plan template
- Incident response policy: what it is and who approves it
- Incident response roles and responsibilities
- What is an incident response plan?
- How to create an incident response plan
- Incident response steps: the order and who does what
- Incident response playbook: what it is and how to build a library
Sources
- NIST CSF 2.0 Reference Tool download, with ISO/IEC 27001:2022 informative references
- SANS Institute, Incident Handler's Handbook (21 February 2012)
- NCSC, 10 Steps to Cyber Security: Incident management (11 May 2021)
- NIST SP 800-61 Rev. 3, full text (April 2025)
Last reviewed 16 November 2026. Each source above was read that day.