The incident clocks: DORA, NIS2, and GDPR side by side

Practitioner guide7 min readUpdated November 2026

When a serious incident lands, the hardest part often isn't the response; it's the paperwork racing a stopwatch. Different regimes start different clocks, in different formats, to different regulators, all at once. Here's how the major EU clocks line up.

When the clock starts

A common misconception is that the deadline runs from when the incident happened. In practice it runs from awareness or classification of a qualifying event, and the regimes do not share one start. Under GDPR the clock runs from becoming aware of a personal-data breach, and under NIS2 from 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 record both the awareness time and the classification time: each clock runs from its own trigger, which is why fast, accurate classification matters so much.

Regime
Headline deadlines
Reported to
DORA
4h initial72h intermediate1mo final
Competent financial authority
NIS2
24h warning72h notice1mo final
CSIRT / national authority
GDPR
72h notification
Supervisory authority (+ data subjects if high risk)
US SEC
4 business days
Form 8-K to the SEC
US Federal Banks
36 hours
FDIC / OCC / Fed
NYDFS
72 hours
NY Dept of Financial Services
US FTC
30 days
Federal Trade Commission
DORA and GDPR apply directly; NIS2 is set out in national law. See EUR-Lex for statutory text. Informational, not legal advice. EU rows last verified November 2026. US rows were last checked in July 2026.

The parallel-filing problem

The real difficulty is that one incident can trip more than one clock. A ransomware event at a bank can be a DORA major incident and a GDPR personal-data breach at the same time; NIS2 incident reporting does not apply to a financial entity covered by DORA. A non-financial essential entity faces NIS2 plus GDPR instead. Either way that is two clocks, two formats and two recipients, and the 4-hour DORA notification is running while your team is still confirming scope. Since 11 September 2026 the Cyber Resilience Act (Article 14) also puts manufacturers on a 24-hour early warning and 72-hour notification clock.

Handled manually, that means parallel drafting under time pressure, with real risk of a missed deadline or an inconsistent story across filings. The way out is to decide, once and in advance, which regimes bind you, and to let a system schedule each filing from its own trigger and pre-draft it as the incident is classified.

Running the clocks with CIIC

This is exactly what Polestead's CIIC (Critical Incident Intelligence Center) does. It maps your business profile to the regimes that apply, records the awareness time and the classification time, schedules each clock from its own trigger, produces the next-step plan, and drafts each regulator-ready report in parallel, so the deadline is a schedule, not a scramble. See the CIIC page for detail, or book a demo.

Quick answers.

When does the clock start?+

Not when the incident began, and not at one shared moment. GDPR and NIS2 run from awareness. The DORA initial notification is due within 4 hours of classification as major, and no later than 24 hours from awareness.

Can one incident trigger several regimes?+

Yes. A financial entity covered by DORA can face DORA plus GDPR, because NIS2 incident reporting does not apply to it. A non-financial essential entity can face NIS2 plus GDPR. Each has its own clock and format, so they must be tracked and filed in parallel.

What are the headline 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/72h/1-month from awareness. GDPR: without undue delay and, where feasible, within 72h to the supervisory authority. For NIS2, verify national specifics.