Articles

Incident response: roles, escalation and communication

Who answers for an incident, what triggers escalation, and who is told what.

Reading: 5 minCybersecurity Governance

Article cover: Incident response: roles, escalation and communication

An incident is a sequence of decisions under time pressure, and almost every one has a governance precondition: who is accountable, who may shut a service down, what makes a busy day an escalation, what makes it an elevation, and who is told what. None of it is created while the incident runs — the authority lives in a policy written beforehand, and the people who hold it are named there. This sheet covers that layer, and the record it leaves behind.

The life cycle is six Functions, not four phases

SP 800-61 Rev. 3 (April 2025) supersedes Rev. 2 and is written as a CSF 2.0 Community Profile (lines 90, 345, 244–248). Its §2.1 first shows the previous edition’s circular life cycle — Preparation; Detection & Analysis; Containment, Eradication & Recovery; Post-Incident Activity — as the earlier model (Table 1, lines 454–471). The model it uses instead is built on the six CSF 2.0 Functions: Govern, Identify, Protect, Detect, Respond, Recover (line 406). The figure separates them: “The bottom level reflects that the preparation activities of Govern, Identify, and Protect are not part of the incident response itself” (lines 431–433). Incident response is the top level — Detect, Respond, Recover — with continuous improvement in the middle (lines 433–437).

The roles are wider than the incident response team

§2.2 records the shift: incident response was once performed “almost exclusively by incident handlers”, and now depends on “the participation of many internal and external parties” (lines 483–489). Leadership “oversees incident response, allocates funding, and may have decision-making authority on high-impact response actions, such as shutting down or rebuilding critical services” (lines 499–501); asset owners hold priorities for affected systems and must be “kept up to date on the status of response and recovery efforts” (lines 560–563). A provider engaged for response makes it “a shared responsibility model” whose division must be “clearly defined in a contract”, including “authority to act on behalf of the organization” (lines 569–574).

The policy names the authority before it is needed

§2.3 lists what an incident response policy contains, and one item is this sheet’s centre: “Roles, responsibilities, and authorities, such as which roles have the authority to confiscate, disconnect, or shut down technology assets” (lines 602–603), alongside guidelines for prioritising incidents (lines 605–606) and performance measures (line 608). The Community Profile adds that roles and responsibilities “should include incident response” and be “documented in an organization’s policies” (Table 2, GV.RR block, lines 799–816). SP 800-53 Rev. 5 carries the same duty: IR-1 requires the policy to address roles and responsibilities and an official to be designated to manage it (lines 10366, 10375–10376); IR-8 requires the plan to “Explicitly designates responsibility for incident response” (line 10996).

Escalation and elevation are two different moves

CSF 2.0’s RS.MA-04 reads “Incidents are escalated or elevated as needed” (line 1057), and r3 defines the pair, which are routinely confused: “Escalation generally refers to increasing resources or time frames, while elevation usually indicates involving a higher level of management in the response efforts” (lines 1636–1638). Neither is improvised: triage, “escalation, and elevation … should all be based on a set of risk evaluation factors” (lines 1554–1558), and because of resource limitations “incidents should not be handled on a first-come, first-served basis” (lines 1551–1553). The factors r3 offers as examples are asset criticality, functional impact, data impact, stage of observed activity, threat actor characterization and recoverability (lines 1568–1572).

   a detected incident
          |
   triage and prioritise  <----  risk evaluation factors
          |                      (asset criticality, functional impact,
          |                       data impact, stage of activity,
          |                       threat actor, recoverability)
     +----+----+
     |         |
 escalate   elevate
 + more     + a higher level of
 resources    management joins
 + or time    the response
     |         |
     +----+----+
          |
   manage -> recover -> after-action report -> ID.IM improvements

Communication is four categories and a timetable

The category RS.CO covers response activities “coordinated with internal and external stakeholders as required by laws, regulations, or policies” (CSF 2.0, lines 1071–1072). r3 splits the work into four categories — incident coordination, incident notification, public communication and incident information sharing (lines 1741–1760). Its coordination procedure makes the plan testable: “Follow established procedures concerning incident coordination that include what must be reported to whom and at what times (e.g., initial notification, regular status updates)” (lines 1771–1775). Law enforcement and regulatory bodies are notified “based on criteria in the incident response plan and management approval”, and notifications must comply with the laws pertaining to the organisation’s sectors and locations (lines 1776–1782, 1796–1799).

The record is what turns an incident into a change

RC.RP-06 ends recovery on two conditions at once: the end “is declared based on criteria, and incident-related documentation is completed” (CSF 2.0, lines 1103–1104). The recommendation is explicit — “Prepare an after-action report that documents the incident itself, the response and recovery actions taken, and lessons learned” (lines 2005–2008) — and RS.AN-06 requires the actions of an investigation to be recorded with their integrity and provenance preserved (CSF 2.0, lines 1064–1065). r3 notes that “Improvements are often identified when creating follow-up reports for incidents or holding ‘lessons learned’ meetings when an incident’s recovery efforts are concluding, especially if the incident was major” (lines 1163–1168), and IR-4(c) makes the loop a control: “Incorporate lessons learned … into incident response procedures, training, and testing, and implement the resulting changes accordingly” (lines 10553–10555).

Level and prerequisites

L3 — governance of a process: the sheet names who holds which authority and states the escalation and reporting rules; it does not run a response or select controls for it. It assumes the L1 accountability vocabulary and the L2 roles material. Technical handling belongs to the technical areas, and continuity and RPO/RTO to their own sheets.

Where to go next

References

  • NIST — SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile (April 2025) — https://doi.org/10.6028/NIST.SP.800-61r3 — the life-cycle model (§2.1, lines 379–471), roles and responsibilities (§2.2, lines 483–575), policies, processes and procedures (§2.3, lines 586–620), and the Community Profile rows quoted here (escalation and elevation at lines 1551–1558 and 1636–1638; communication at lines 1741–1799; improvement and the after-action report at lines 1163–1168 and 2005–2008).
  • NIST — The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 (26 February 2024) — https://doi.org/10.6028/NIST.CSWP.29 — RS.MA-04 (line 1057), the RS.CO category statement (lines 1071–1072), RS.AN-06 (lines 1064–1065) and RC.RP-06 (lines 1103–1104).
  • NIST — SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations — https://doi.org/10.6028/NIST.SP.800-53r5 — IR-1 (lines 10366, 10375–10376), IR-4(c) (lines 10553–10555), IR-8(a)(10) and IR-8(b) (lines 10996, 10999).
Nodrius Field Kit — cover

Get the Nodrius Field Kit

Enter your email and we'll send you the complete Field Kit: eight technical resources in one download.

Your email address is sent to Nodrius and used to deliver the Field Kit to you by email. Marketing messages are separate and optional: the checkbox does not affect your download, and you are only added to our updates list if you tick it. Privacy Policy.

Privacy & cookies

This site does not use cookies, analytics or tracking, and it does not profile you. There is nothing technical to switch off, so Accept and Reject change nothing about how the site works: either choice lets you browse everything normally.

The only difference is what your browser remembers: two entries in local storage — your choice here, so this notice is not shown again, and a marker that the Field Kit offer has already been made — so the offer is presented once and not on every page. They contain no identifier, they are not shared with anyone, and the site sets no cookie for either.

What we do with your data
How your email address is used when you ask for a Resource, how long it is kept and which rights you have — in the Privacy Policy.
What the site stores in your browser
Two entries in local storage — your choice on this notice and whether the Field Kit offer has been shown — and no cookies, no session storage, no third-party content: in the Cookie Policy.