Management vs response
The two terms get used interchangeably, but the distinction matters when an incident is live. Incident response is the technical work: detect, contain, eradicate, recover. It's what your SOC or IR team does at the keyboard. Incident management is the wider coordination wrapped around it: command and decision-making, internal and board communication, customer and legal notification, regulatory reporting, and the post-incident review that feeds back into preparation. Response is a component of management. A team can execute flawless containment and still fail management by missing a 72-hour regulatory deadline.
The six-phase lifecycle
Frameworks including NIST SP 800-61 and ISO/IEC 27035 describe similar cycles. A practical six-phase version:
- Preparation. Plans, roles, runbooks, and the profile work that tells you in advance which regulators bind you. The best time to learn your reporting obligations is not during the incident.
- Detection & analysis. Recognize that something is happening and establish scope, entry point, and impact.
- Classification & triage. Decide whether this is a reportable major or significant incident. This is the pivot point; see below.
- Containment, eradication & recovery. The core response work: stop the spread, remove the cause, restore service safely.
- Notification & reporting. Inform the parties owed information (customers, data subjects, and regulators) each on their own deadline and in their own format.
- Post-incident review. A blameless review that turns the event into improved preparation. Regulators increasingly expect a documented final report anyway.
What starts each clock
A common and costly misconception is that reporting deadlines run from when the incident began. In practice they run from awareness or classification of a qualifying event, and not all from one start. Under GDPR the trigger is becoming aware of a personal-data breach, and under NIS2 it is becoming aware of a significant incident. Under DORA the initial notification is due within 4 hours of classifying the incident as major, and no later than 24 hours from becoming aware of it. So log both the awareness time and the classification time, because each clock runs from its own trigger. That is exactly why fast, accurate classification is worth investing in: time lost deciding whether an event qualifies runs down the 24-hour backstop, and once you classify, 4 hours is all you have.
DORA, NIS2, and GDPR deadlines
One incident can trip more than one regime. A ransomware event at a bank can be a DORA major incident and a GDPR personal-data breach at the same time: two clocks, two formats, two recipients. NIS2 incident reporting does not apply to a financial entity covered by DORA; a non-financial essential entity faces NIS2 plus GDPR instead. The headline deadlines:
| Regime | Headline deadlines | Reported to |
|---|---|---|
| DORA | Competent financial authority | |
| NIS2 | CSIRT / national authority | |
| GDPR | 72h notification | Supervisory authority (+ data subjects if high risk) |
DORA and GDPR apply directly; NIS2 is set out in national law. Informational, not legal advice. Last verified November 2026. Our incident clocks guide works through each in detail.
When the incident is a third party's
Increasingly, the incident you have to manage didn't happen on your systems at all; it happened at a vendor. That changes the mechanics: your visibility is second-hand, your containment options are contractual rather than technical, and the reporting clocks may still apply to you because it's your data or your service that's affected. Managing a third-party incident well depends on work done long before it: knowing which vendors hold what, and having notification terms already in the contract. We cover that in the companion guide on cyber risk response, and it starts upstream with sound third-party risk management.