In short
NIS2 (§ 32 BSIG in Germany) and the CRA require an initial report within 24 hours and a notification within 72 hours of awareness. EU DORA requires the initial notification four hours after classification as major, and no later than 24 hours after awareness. The AI Act counts in days: 15, two for critical infrastructure, ten after a death.
One incident, up to four reporting clocks
A single security event can trigger several reporting duties in the same organisation at once. A software manufacturer that is also an important entity under NIS2 reports an attack on its own network under § 32 BSIG and an actively exploited vulnerability in its product under Article 14 of the Cyber Resilience Act (CRA). A financial entity reports a major ICT-related incident under EU DORA. A provider of a high-risk AI system reports a serious incident under Article 73 of the AI Act. Each of these duties has its own deadlines, its own recipients and, above all, its own starting events.
Throughout, this article means EU DORA, Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. It has nothing to do with the DORA metrics from software delivery (deployment frequency, lead time and the others); the article DORA vs. NIS2 explains the difference between the two terms and how the scope of EU DORA relates to NIS2.
This article sets the four regimes side by side in one table, explains the starting events and works through a concrete example. For deadlines based on your own timestamp, use the free reporting deadline calculator: you enter the moment of awareness and it returns every deadline with time of day and legal source.
The number of hours is rarely the problem. Mistakes happen at the starting event: awareness, classification, submission of the previous report or availability of a patch each start a different clock.
The comparison table: reporting deadlines under NIS2, EU DORA, CRA and the AI Act
The table summarises the duties according to the wording of the primary sources. “Awareness” means the moment at which the party subject to the duty becomes aware of the incident; the exact wording differs between the acts and is quoted in the sections that follow.
| Regime | Trigger | Initial report | Follow-up report | Final report | Recipient | Legal source |
|---|---|---|---|---|---|---|
| NIS2 (DE: BSIG) | Significant incident at an essential or important entity | Early warning without undue delay, no later than 24 h after awareness | Notification no later than 72 h after awareness; intermediate report on BSI request | No later than 1 month after submitting the 72 h notification; if ongoing, progress report, final report once handled | Joint reporting point of BSI and BBK | § 32(1) nos. 1–4, (2) BSIG; Art. 23(4) Directive (EU) 2022/2555 |
| EU DORA | Major ICT-related incident at a financial entity | 4 h after classification as major, no later than 24 h after awareness; if classified later, 4 h from classification | Intermediate report no later than 72 h after submitting the initial notification; update once regular activities have been recovered | No later than 1 month after the (latest updated) intermediate report | Competent authority; in Germany BaFin via the MVP portal | Art. 19(1), (4) Regulation (EU) 2022/2554; Art. 5 Delegated Regulation (EU) 2025/301 |
| CRA – vulnerability | Actively exploited vulnerability in a product with digital elements | Early warning without undue delay, no later than 24 h after awareness | Vulnerability notification no later than 72 h after awareness; intermediate report at the CSIRT’s request | No later than 14 days after a corrective or mitigating measure is available | CSIRT designated as coordinator and ENISA via the single reporting platform | Art. 14(1), (2), (6) Regulation (EU) 2024/2847 |
| CRA – incident | Severe incident having an impact on the security of the product | Early warning without undue delay, no later than 24 h after awareness | Incident notification no later than 72 h after awareness; intermediate report at the CSIRT’s request | Within 1 month after submitting the 72 h notification | CSIRT designated as coordinator and ENISA via the single reporting platform | Art. 14(3)–(6) Regulation (EU) 2024/2847 |
| AI Act | Serious incident involving a high-risk AI system (provider) | Immediately after establishing the causal link, no later than 15 days after awareness; 2 days for a widespread infringement or critical infrastructure; 10 days for the death of a person | Incomplete initial report permitted, followed by a complete report | No separate final deadline; investigation and corrective action without delay | Market surveillance authority of the Member State where the incident occurred | Art. 73(1)–(6) Regulation (EU) 2024/1689 |
NIS2 in Germany: the 24/72-hour cascade under § 32 BSIG
In Germany, § 32 BSIG transposes the reporting duty from Article 23 of the NIS2 Directive. Essential and important entities report to a joint reporting point set up by the BSI and the Federal Office of Civil Protection and Disaster Assistance (BBK). The early warning is due without undue delay and no later than 24 hours after the entity becomes aware of the incident, and states whether the incident is suspected of being caused by unlawful or malicious acts or could have a cross-border impact (§ 32(1) first sentence no. 1 BSIG).
No later than 72 hours after becoming aware, the notification follows with an initial assessment, severity, impact and, where available, indicators of compromise (no. 2). An intermediate report is only due at the BSI’s request (no. 3). The final report does not run from awareness but from submission of the 72-hour notification: no later than one month afterwards (no. 4). If the incident is still ongoing at that point, a progress report is submitted instead; the final report follows once the incident has been fully handled (§ 32(2) BSIG).
Two details matter for planning. First, under § 32(1) second sentence BSIG the duty applies at the earliest once the reporting channel has been set up. Second, the German text departs from the Directive for ongoing incidents: Article 23(4)(e) of Directive (EU) 2022/2555 requires the final report “within one month of their handling of the incident”, whereas the BSIG sets no one-month limit for this case. For entities active in several Member States, that is a reason to check each national transposition rather than relying on the Directive alone.
Financial entities within the meaning of Article 2(2) EU DORA are exempt from § 32 BSIG (§ 28(6) no. 1 BSIG). BaFin puts it this way on its incident-handling page: financial entities covered by DORA are exempt from the reporting duty under § 32 BSIG that would otherwise apply. Whether an organisation falls under NIS2 at all is what the NIS2 readiness check shows.
EU DORA: four hours from classification, 24 hours from awareness
In Article 19(4) of Regulation (EU) 2022/2554, EU DORA only sets the sequence of reports: initial notification, intermediate report, final report. The deadlines are in Article 5 of Delegated Regulation (EU) 2025/301. The initial notification is due “as early as possible, but in any case, within four hours from the classification of the ICT-related incident as a major ICT-related incident and no later than 24 hours from the moment the financial entity has become aware” of it (Article 5(1)(a)). Which incidents count as major is set out in Delegated Regulation (EU) 2024/1772; under its Article 8(1), this requires that critical services are affected and that certain materiality thresholds are met.
EU DORA is therefore the only one of the four regimes in which two fixed deadlines with different starting events apply to the same report. The earlier of the two limits is decisive. If the financial entity classifies the incident as major only after 24 hours from awareness have passed, the deadline runs from classification alone: initial notification within four hours of it (Article 5(2)).
The intermediate report is due no later than 72 hours after submission of the initial notification, “even where the status or the handling of the incident have not changed”; an updated intermediate report follows once regular activities have been recovered (Article 5(1)(b)). The final report is due no later than one month after the intermediate report or the latest updated intermediate report (point (c)). An entity that cannot meet a deadline informs the authority before it expires and gives reasons (Article 5(3)).
EU DORA is the only regime with a weekend rule. Where a deadline falls on a weekend day or a bank holiday in the Member State of the reporting financial entity, the report may be submitted by noon of the next working day (Article 5(4)). For initial notifications and intermediate reports this does not apply to credit institutions, central counterparties, operators of trading venues and financial entities identified as essential or important entities under Article 3 of the NIS2 Directive (paragraph 5); the competent authority may exclude further significant or systemic financial entities (paragraph 6).
The recipient is the competent authority under Article 46. In Germany that is BaFin; according to BaFin, reports are submitted via its reporting and publication platform (MVP). Independently of the report to the authority, the financial entity informs its clients without undue delay where their financial interests are affected (Article 19(3)).
CRA: two triggers, two different final-report deadlines
Article 14 CRA has applied since 11 September 2026 (Article 71(2) Regulation (EU) 2024/2847), including for products placed on the market before 11 December 2027 (Article 69(3)). The duty lies with the manufacturer, not the operator. There are two triggers: an actively exploited vulnerability in the product (paragraphs 1 and 2) and a severe incident having an impact on the security of the product (paragraphs 3 and 4). Under paragraph 5, an incident is severe where it negatively affects, or is capable of negatively affecting, the product’s ability to protect sensitive or important data or functions, or where it has led or is capable of leading to the introduction or execution of malicious code.
Both triggers share the first two stages: an early warning without undue delay and no later than 24 hours after awareness, and a notification no later than 72 hours after awareness. The difference lies in the final report. For a vulnerability it is due “no later than 14 days after a corrective or mitigating measure is available” (Article 14(2)(c)). The clock therefore starts with the available patch or workaround, not with awareness. For an incident the deadline is one month after submission of the 72-hour notification (paragraph 4(c)).
Notifications go through the single reporting platform under Article 16, using the end-point of the CSIRT designated as coordinator in the Member State of the main establishment; they are simultaneously accessible to ENISA (Article 14(7)). The coordinating CSIRT may request an intermediate report (paragraph 6). The manufacturer also informs the impacted users (paragraph 8). Paragraph 8 sets no fixed deadline for this; its second sentence refers to informing users “in a timely manner”. More on the CRA reporting process in a delivery context is in the article on the CRA reporting duty.
AI Act: deadlines in days rather than hours
Article 73 of the AI Act requires providers of high-risk AI systems to report serious incidents to the market surveillance authorities of the Member States where the incident occurred. The report is made “immediately after the provider has established a causal link”, and in any event no later than 15 days after the provider or, where applicable, the deployer becomes aware of it (Article 73(2)). The 15 days are therefore a ceiling, not a target.
Two shorter deadlines apply regardless: two days for a widespread infringement or a serious incident under Article 3(49)(b), meaning a serious and irreversible disruption of the management or operation of critical infrastructure (Article 73(3)), and ten days for the death of a person (paragraph 4). To meet the deadline, an incomplete initial report may be submitted, followed by a complete one (paragraph 5). The provider then investigates without delay, assesses the risk and takes corrective action (paragraph 6). For Annex III systems placed on the market by providers subject to equivalent reporting duties under other Union law, only incidents under Article 3(49)(c) have to be reported (paragraph 9).
On timing: under Article 113 of the consolidated text (as of 27 July 2026, amended by Regulation (EU) 2026/1744), the regulation applies in principle from 2 August 2026. The rules for high-risk AI systems in Chapter III, Sections 1 to 3, however, apply only from 2 December 2027 for Annex III systems and from 2 August 2028 for Annex I systems. In practice, the Article 73 reporting duty therefore becomes relevant from those two dates.
When does the clock start? The five starting events
For the reporting process it matters more to know which event starts a clock than to remember the number of hours. Five different starting events occur across the four regimes. Each should be recorded with date and time in the incident log, because later deadlines refer back to it.
- Awareness of the incident: starts the 24- and 72-hour deadlines under § 32 BSIG and Article 14 CRA, the 24-hour ceiling under EU DORA and the day-based deadlines under Article 73 AI Act.
- Classification as major: starts the four-hour deadline for the EU DORA initial notification (Article 5(1)(a) and (2) Delegated Regulation (EU) 2025/301).
- Submission of a previous report: starts the final-report deadline under § 32(1) no. 4 BSIG and Article 14(4)(c) CRA (each from the 72-hour notification) as well as the EU DORA intermediate and final reports (from the initial and latest intermediate report respectively).
- Availability of a corrective or mitigating measure: starts the 14-day deadline for the CRA final report on vulnerabilities (Article 14(2)(c)).
- Request by the authority: triggers the intermediate report under § 32(1) no. 3 BSIG and Article 14(6) CRA.
Worked example: awareness on Friday at 6 pm
Suppose the organisation becomes aware of an incident on Friday, 6 November 2026, at 18:00 that touches all four regimes. For EU DORA, assume in addition that the incident is classified as major the same evening at 22:00; for the CRA, that a patch becomes available on Thursday, 19 November 2026. The table shows the latest permissible times (German time). Follow-up deadlines that depend on a submission assume that the previous report is filed exactly at the time stated.
Two effects stand out. First, the 24-hour deadlines fall on the Saturday; the BSIG and the CRA have no weekend rule for their hour-based deadlines. Second, the EU DORA initial notification is due during the night, because four hours from classification expire before the 24-hour ceiling. The weekend rule in Article 5(4) Delegated Regulation (EU) 2025/301 would extend the deadline to Monday, 9 November 2026, at 12:00, but does not apply to credit institutions and the other entities listed in paragraph 5.
The reporting deadline calculator works out your own case with time of day and legal source for each deadline. Running deadlines across all regulations are shown in the deadline calendar.
| Regime | Step | Latest | Basis |
|---|---|---|---|
| NIS2 (BSIG) | Early warning | Sat 07/11/2026, 18:00 | 24 h from awareness, § 32(1) no. 1 |
| NIS2 (BSIG) | Notification | Mon 09/11/2026, 18:00 | 72 h from awareness, § 32(1) no. 2 |
| NIS2 (BSIG) | Final report | Wed 09/12/2026 | 1 month from notification (submitted Mon 09/11/2026), § 32(1) no. 4 |
| EU DORA | Initial notification | Sat 07/11/2026, 02:00 | 4 h from classification (Fri 22:00), Art. 5(1)(a) Del. Reg. 2025/301 |
| EU DORA | Intermediate report | Tue 10/11/2026, 02:00 | 72 h from initial notification (submitted Sat 02:00), Art. 5(1)(b) |
| CRA | Early warning | Sat 07/11/2026, 18:00 | 24 h from awareness, Art. 14(2)(a) |
| CRA | Vulnerability notification | Mon 09/11/2026, 18:00 | 72 h from awareness, Art. 14(2)(b) |
| CRA | Final report | Thu 03/12/2026 | 14 days from patch (Thu 19/11/2026), Art. 14(2)(c) |
| AI Act | Report (general case) | Sat 21/11/2026 | 15 days from awareness, Art. 73(2) |
| AI Act | Report (critical infrastructure) | Sun 08/11/2026 | 2 days from awareness, Art. 73(3) |
| AI Act | Report (death of a person) | Mon 16/11/2026 | 10 days from awareness, Art. 73(4) |
Hour-based deadlines run in absolute time: clock changes, weekends, bank holidays
A 24-hour deadline counts hours, not clock times. Across a clock change it therefore ends at a different wall-clock time from the one it started at. Take the end of summer time on Sunday, 25 October 2026: with awareness on Saturday, 24 October 2026, at 10:00, the 24-hour deadline ends on Sunday at 09:00 and the 72-hour deadline on Tuesday, 27 October 2026, at 09:00. The reverse applies at the start of summer time on Sunday, 28 March 2027: awareness on Saturday, 27 March 2027, at 10:00 leads to a deadline ending on Sunday at 11:00.
Day- and month-based deadlines (CRA 14 days and one month, AI Act 2, 10 and 15 days, NIS2 and EU DORA one month), by contrast, run on the calendar. Periods in acts of the Council and the Commission are calculated under Regulation (EEC, Euratom) No 1182/71. Under its Article 3(1), the hour or day during which the starting event occurs is not counted. Under Article 3(4), a period not expressed in hours whose last day is a Saturday, Sunday or public holiday ends only with the expiry of the following working day; this shift expressly does not apply to periods expressed in hours.
Whether and how these rules extend the deadlines discussed here in a given case is a question of interpretation that should be settled before an incident, not during one. For the reporting process, the conservative calculation is advisable: from the minute of awareness, day-based deadlines at the same time of day, without any shift. That is how the example above and the reporting deadline calculator calculate.
The only express weekend rule is in Article 5(4) Delegated Regulation (EU) 2025/301 for EU DORA, with the exceptions in paragraphs 5 and 6. For the 24- and 72-hour deadlines under the BSIG and the CRA, a Saturday counts like a Tuesday.
Reporting in parallel: one process, several outputs
Because the starting events overlap, a shared reporting process with regime-specific outputs pays off more than four separate runbooks. The core is the same for every regime: detect the event, record the moment of awareness, check which regimes apply, start the clocks, submit the reports through the relevant channel and log every submission with a timestamp, because it starts the next deadline.
Three organisational points decide whether the deadlines can be met. First, the reporting channel for each applicable regime must be set up before it is needed: access to the BSI/BBK reporting point, to BaFin’s MVP and to the single CRA reporting platform. Second, an on-call rota with deputies is needed that can run a four-hour or 24-hour clock at weekends too; the Handover & Deputy Plan records deputies and handovers. Third, the chain should be rehearsed, ideally with a start time on a Friday evening.
For the exercise, the EU Regulatory Evidence Cockpit offers a “simulate incident” mode that starts a separate clock for each applicable regime. An overview of scope and key dates for all EU regulations is on the EU regulation page. How NIS2 and EU DORA differ in scope is covered in DORA vs. NIS2.
Sources and status
All deadlines were checked against the wording of the following primary sources on 30 October 2026. This overview is for orientation and does not replace legal advice; the published text is authoritative.
- German BSI Act (BSIG) of 2 December 2025, last amended by Art. 8 of the Act of 22 October 2026 (BGBl. 2026 I No. 318), § 28(6), § 32 – https://www.gesetze-im-internet.de/bsig_2025/__32.html (accessed 30/10/2026)
- Directive (EU) 2022/2555 (NIS2), Art. 23(4) – https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555 (accessed 30/10/2026)
- Regulation (EU) 2022/2554 (EU DORA), Art. 19, Art. 64 – https://eur-lex.europa.eu/eli/reg/2022/2554/oj (accessed 30/10/2026)
- Delegated Regulation (EU) 2025/301, Art. 5 – https://eur-lex.europa.eu/eli/reg_del/2025/301/oj (accessed 30/10/2026)
- Delegated Regulation (EU) 2024/1772, Art. 8 – https://eur-lex.europa.eu/eli/reg_del/2024/1772/oj (accessed 30/10/2026)
- BaFin, handling and classification of ICT-related incidents (German) – https://www.bafin.de/DE/unternehmen-maerkte/aufsicht/alle-unternehmen/it-cybersicherheit/ikt-bezogene-vorfaelle/behandlung-klassifizierung/behandlung-klassifizierung_node.html (accessed 30/10/2026)
- Regulation (EU) 2024/2847 (CRA), Art. 14, Art. 69(3), Art. 71(2) – https://eur-lex.europa.eu/eli/reg/2024/2847/oj (accessed 30/10/2026)
- Regulation (EU) 2024/1689 (AI Act), consolidated text of 27 July 2026, Art. 3(49), Art. 73, Art. 113 – https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02024R1689-20260727 (accessed 30/10/2026)
- Regulation (EEC, Euratom) No 1182/71, Art. 1, Art. 3 – https://eur-lex.europa.eu/eli/reg/1971/1182/oj (accessed 30/10/2026)
Key Takeaways
- NIS2 (§ 32 BSIG) and the CRA use 24 hours for the initial report and 72 hours for the notification, both counted from awareness.
- EU DORA requires the initial notification four hours after classification as major, no later than 24 hours after awareness (Art. 5 Delegated Regulation (EU) 2025/301).
- The CRA has two final-report deadlines: 14 days from an available fix for vulnerabilities, one month from the notification for incidents.
- The AI Act counts in days: 15 as a rule, two for a widespread infringement or critical infrastructure, ten after the death of a person.
- Hour-based deadlines run in absolute time across weekends and clock changes; only EU DORA has an express weekend rule, with exceptions.
- DORA financial entities are exempt from § 32 BSIG (§ 28(6) no. 1 BSIG) and in Germany report via BaFin’s MVP.
Frequently Asked Questions
The EU DORA initial notification: four hours after an ICT-related incident is classified as major, and no later than 24 hours after awareness (Art. 5(1)(a) Delegated Regulation (EU) 2025/301). Under NIS2 and the CRA the first report is due no later than 24 hours after awareness; under the AI Act the shortest deadline is two days.
Not in Germany. Financial entities under Article 2(2) EU DORA are exempt from § 32 BSIG (§ 28(6) no. 1 BSIG) and report major ICT-related incidents to BaFin via the MVP. An organisation that is also a manufacturer under the CRA may still report twice: the CRA notification goes to the coordinating CSIRT and ENISA.
Not for hour-based deadlines under the BSIG and the CRA. EU DORA allows submission by noon of the next working day when a deadline falls on a weekend or bank holiday, except for initial and intermediate reports from credit institutions, central counterparties, trading venue operators and NIS2 entities (Art. 5(4) and (5) Delegated Regulation (EU) 2025/301). For day-based deadlines, Article 3(4) of Regulation 1182/71 contains a shifting rule; conservative planning assumes no shift.
From the moment a corrective or mitigating measure is available, not from awareness (Art. 14(2)(c) Regulation (EU) 2024/2847). It applies only to actively exploited vulnerabilities. For severe incidents, the final report is due within one month after the 72-hour notification.
Article 113 makes the regulation applicable in principle from 2 August 2026. The rules for high-risk AI systems in Chapter III, Sections 1 to 3, however, apply only from 2 December 2027 (Annex III) and 2 August 2028 (Annex I) respectively. In practice, the reporting duty for providers of high-risk AI systems becomes relevant from those dates.
With the free reporting deadline calculator at /meldefristen: you enter the moment of awareness and it returns every deadline with time of day and legal source. For a rehearsed reporting chain with a separate clock per regime, the EU Regulatory Evidence Cockpit offers an exercise mode.