Cyber incident management: the lifecycle and the clocks.

Resilience9 min readUpdated November 2026

When a serious cyber incident lands, the technical fix is only half the job. The other half is coordination under pressure: deciding what happened, who needs to know, and which regulators are now counting down. Cyber incident management is the discipline that holds both halves together. This guide covers the lifecycle, how management differs from response, and the statutory reporting clocks that start when you become aware of an incident or classify it.

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:

  1. 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.
  2. Detection & analysis. Recognize that something is happening and establish scope, entry point, and impact.
  3. Classification & triage. Decide whether this is a reportable major or significant incident. This is the pivot point; see below.
  4. Containment, eradication & recovery. The core response work: stop the spread, remove the cause, restore service safely.
  5. Notification & reporting. Inform the parties owed information (customers, data subjects, and regulators) each on their own deadline and in their own format.
  6. 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:

RegimeHeadline deadlinesReported to
DORA4h initial72h intermediate1mo finalCompetent financial authority
NIS224h warning72h notice1mo finalCSIRT / national authority
GDPR72h notificationSupervisory 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.

Common questions.

What is cyber incident management?

The coordinated end-to-end process of preparing for, detecting, containing, resolving, and learning from cybersecurity incidents, including the governance, communication, and regulatory reporting that technical response alone doesn't cover.

How is it different from incident response?

Incident response is the technical containment, eradication, and recovery work. Incident management is the wider coordination around it: decisions, communication, legal and regulatory reporting, and review. Response is one part of management.

What are the lifecycle phases?

A common six-phase model: preparation; detection and analysis; classification and triage; containment, eradication and recovery; notification and reporting; and post-incident review. NIST SP 800-61 and ISO/IEC 27035 describe similar cycles.

What are the DORA, NIS2, and GDPR deadlines?

DORA: 4h initial from classification (no later than 24h from awareness), intermediate within 72h of the initial, final within one month of the latest intermediate. NIS2: 24h warning and 72h notice from awareness, final one month after the notice. GDPR: without undue delay and, where feasible, within 72h to the supervisory authority. None runs from when the incident began. DORA and GDPR apply directly; NIS2 is set out in national law.