Guide
NIS2 and DORA reporting deadlines compared in 2026
NIS2 and DORA use different deadline anchors. Compare initial, intermediate and final reports without starting the wrong timer.


24 hours, 72 hours, one month: similar numbers tempt teams to use the same reporting workflow for NIS2 and DORA. Their starting points differ, however. A shared incident process therefore needs separate legal deadline rules.
The table and example incident show which time counts. Use them to derive required time fields and responsibilities for your reporting process.
Which reporting route applies?
The NIS2 side of this comparison concerns general German obligations under section 32 BSIG. For DORA, it concerns major ICT-related incidents under the applicable financial supervisory rules. Assess sector provisions, exemptions and other duties, such as privacy obligations, separately. Not every organisation must automatically report the same incident through both procedures.
The main time anchors
| Step | Section 32 BSIG | DORA: Delegated Regulation 2025/301, Article 5 |
|---|---|---|
| Early warning or initial notification | Without undue delay, no later than 24 hours after awareness of the significant security incident | As early as possible; generally within four hours of classification as major and no later than 24 hours after awareness of the ICT incident |
| Subsequent or intermediate report | No later than 72 hours after awareness of the significant security incident | No later than 72 hours after submission of the initial notification; further updates under applicable rules |
| Final report | Generally no later than one month after the 72-hour notification | No later than one month after the intermediate report or its latest updated version |
Sources: section 32 BSIG and Article 5 of Regulation 2025/301. The table presents general rules, not every special situation.
Do not hide exceptions in the calendar
DORA Article 5 also addresses incidents classified as major later: where classification occurs after the first 24 hours, the specified four-hour period runs from classification. If a deadline is expected to be missed, inform the competent authority under the regulation’s rules. Do not assume weekend or public-holiday provisions apply equally to all financial entities.
Section 32(2) BSIG addresses incidents still ongoing when the final report is due. Define these cases in your procedure rather than handling them by manually moving a date.
A fictional case shows the difference
An incident is detected at 09:00 and classified as major under DORA at 11:00. The regular four-hour limit is therefore 15:00 that day, rather than the following morning. Under BSIG, awareness of a significant security incident is the relevant reference point.
Record detection, classification, awareness and actual submission separately. Legal assessment belongs to the responsible specialist function.
Reporting needs its own event history
For one case, maintain separate times for technical detection, substantive awareness or classification, actual initial notification, intermediate report and later updates. The legal basis determines which time anchors each deadline.
In the DORA example, with detection at 09:00 and classification at 11:00, the further 72-hour period generally depends on actual initial submission. If submitted at 14:00, that transmission time is the reference. Calculating every deadline from ticket creation would be wrong.
This explains the general rule; it does not suggest using statutory maximum periods in full. The obligation to report as early as possible or without undue delay remains relevant.
Two procedures do not automatically mean two reports
First establish which obligations apply to your entity and incident. For certain financial entities, BSIG contains a DORA-related distinction; other reporting obligations may need independent assessment alongside it.
A shared internal situation picture is useful. Responsibility, legal classification and transmission must still remain traceable for each applicable procedure. Preserve confirmed facts and the report version used rather than collapsing different authority requirements into one “reported” status.
Test the process practically
Work through an out-of-hours incident. Who classifies, who deputises and who confirms submission? A reminder is not proof of receipt. Distinguish reminder, acknowledged handling, submission and receipt internally.
In Kopexa, you can document internal workflows and measures. Transmission takes place through the designated regulatory route. Start with an understandable incident process and test it through an incident exercise.
Quick answers
Frequently Asked Questions
Still have a question? Find the answers here.
Do the 72 hours under NIS2 and DORA start at the same point?
No. Under the general BSIG procedure, awareness of the significant incident is decisive. For DORA’s intermediate report, the reference is generally submission of the initial notification.
Sources
- BSIG section 32: Reporting obligations — Bundesministerium der Justiz [Accessed ]
- Delegated Regulation (EU) 2025/301 — Europäische Union [Accessed ]