Solution · NIS2 · EU-DORA · CRA · AI Act · Data Act

EU regulation for IT delivery: NIS2, EU DORA, CRA, AI Act and Data Act in one place

For IT leaders, CISOs and ICT providers to financial entities: who is in scope, which obligations apply, when they are due and how to report an incident – with legal references, review date and a briefing for management.

5regulations46core obligations23deadlines4reporting regimes

Applicability

Who is in scope?

For each regulation: the addressees named in the legal act, the number of core obligations in the cockpit and the next deadline from the calendar. Whether your organisation is actually in scope is what the applicability check in the cockpit establishes.

Who is in scope?
NIS2Directive (EU) 2022/2555; BSIG of 02.12.2025 (BGBl. 2025 I No. 301)Essential and important entities under Section 28 BSIG in the sectors listed in Annexes 1 and 2 BSIG.Core obligations: 14no future deadline in the calendar
EU DORARegulation (EU) 2022/2554Financial entities under Art. 2 of Regulation (EU) 2022/2554; ICT third-party providers through the contractual requirements (Art. 30), critical ICT third-party providers through EU oversight (Art. 31).Core obligations: 1531 Dec 2026 · Reference date register of information 2027
CRARegulation (EU) 2024/2847Manufacturers of products with digital elements, plus importers and distributors.Core obligations: 611 Dec 2027 · CRA: all remaining obligations apply
AI ActRegulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744Providers and deployers of AI systems (Art. 3(3) and (4)); obligations depend on role and risk class.Core obligations: 72 Dec 2026 · AI Act: new prohibitions (ba)/(bb); Art. 50(2) for legacy systems
Data ActRegulation (EU) 2023/2854Manufacturers of connected products, data holders and providers of data processing services (including cloud switching under Chapter VI).Core obligations: 412 Jan 2027 · Data Act: switching charges prohibited

Counted from the regulatory cockpit, as of 26 Oct 2026.

Deadlines

The next EU deadlines

Next up: 2 Dec 2026 – AI Act: new prohibitions (ba)/(bb); Art. 50(2) for legacy systems. Countdown in calendar days, every deadline with its legal reference.

EU deadlines with date, content, legal reference and days remaining
Wednesday
AI Act
AI Act: new prohibitions (ba)/(bb); Art. 50(2) for legacy systems
Regulation (EU) 2024/1689 Art. 113, third subparagraph, point (a), Art. 111(4)15 days to go
Thursday
EU DORA
Reference date register of information 2027
Regulation (EU) 2022/2554 Art. 28(3)44 days to go
Tuesday
Data Act
Data Act: switching charges prohibited
Regulation (EU) 2023/2854 Art. 29(1)56 days to go
Wednesday
EU DORAuncertain
BaFin: register submission 2027 (regular cycle; window to be announced)

Regular cycle per BaFin; the concrete 2027 window is announced at the start of the year.

Regulation (EU) 2022/2554 Art. 28(3)134 days to go
Monday
AI Act
AI Act: legacy GPAI models (before 2 Aug 2025)
Regulation (EU) 2024/1689 Art. 111(3)258 days to go
All 23 deadlines in the EU deadline calendar

Reporting

Reporting regimes compared

One incident can trigger several reporting duties in parallel. The table shows every stage with deadline, clock start, recipient and legal reference.

Reporting stages per regime with deadline, clock start and legal reference
NIS2NIS2 / § 32 BSIG – significant incident

Recipient: joint BSI/BBK reporting point

Early warning (suspected unlawful/malicious, cross-border?)within 24 hClock starts at: awarenessSection 32(1) no. 1 BSIG
Notification with initial assessment, severity, impact, IoCswithin 72 hClock starts at: awarenessSection 32(1) no. 2 BSIG
Intermediate report on BSI requestno fixed deadlineClock starts at: request by the authoritySection 32(1) no. 3 BSIG
Final report (progress report if ongoing, final after handling)within 1 monthClock starts at: notificationSection 32(1) no. 4, (2) BSIG
EU DORAEU-DORA Art. 19 – major ICT-related incident

Recipient: competent authority (DE: BaFin)

Classification per Del. Reg. 2024/1772no fixed deadlineClock starts at: awarenessArt. 18; Delegated Regulation (EU) 2024/1772 Art. 8
Initial notificationwithin 4 hno later than 24 h from awarenessClock starts at: classification as majorDelegated Regulation (EU) 2025/301 Art. 5(1)(a)
Intermediate report (even without status change); updated when regular activities are recoveredwithin 72 hClock starts at: initial notificationDelegated Regulation (EU) 2025/301 Art. 5(1)(b)
Final report after root cause analysiswithin 1 monthClock starts at: latest intermediate reportDelegated Regulation (EU) 2025/301 Art. 5(1)(c); Art. 19(4)(c)
Inform clients if their financial interests are affectedwithout undue delayClock starts at: awarenessArt. 19(3)
CRACRA Art. 14 – actively exploited vulnerability / severe incident

Recipient: CSIRT coordinator and ENISA via the single reporting platform

Vulnerability: early warningwithin 24 hClock starts at: awarenessArt. 14(2)(a)
Vulnerability: notificationwithin 72 hClock starts at: awarenessArt. 14(2)(b)
Vulnerability: final reportwithin 14 daysClock starts at: corrective measure availableArt. 14(2)(c)
Incident: early warningwithin 24 hClock starts at: awarenessArt. 14(4)(a)
Incident: notificationwithin 72 hClock starts at: awarenessArt. 14(4)(b)
Incident: final reportwithin 1 monthClock starts at: incident notificationArt. 14(4)(c)
Intermediate report at the request of the coordinating CSIRTno fixed deadlineClock starts at: request by the authorityArt. 14(6)
Inform affected usersuncertainwithout undue delayClock starts at: awarenessArt. 14(8)
AI ActAI Act Art. 73 – serious incident (high-risk providers)uncertain

Recipient: market surveillance authority of the Member State where it occurred

Serious incident reportwithin 15 daysClock starts at: awarenessArt. 73(2)
widespread infringement / critical infrastructure (Art. 3(49)(b))within 2 daysClock starts at: awarenessArt. 73(3)
death of a personwithin 10 daysClock starts at: awarenessArt. 73(4)
incomplete initial report permittedno fixed deadlineClock starts at: awarenessArt. 73(5)
Calculate the reporting deadlines for a specific point in time

How it works

From applicability to the briefing

Start by clarifying which regulations apply: 18 questions across 5 legal acts, each answer with its legal reference. Then the obligation matrix shows who owns what, which evidence exists and when it expires. The reporting drill walks through an incident – with the 24-hour, 72-hour and one-month clocks. The result is a briefing for management.

  1. 01

    Applicability

    18 questions classify each regulation; every rule names its legal reference.

  2. 02

    Obligation matrix

    46 core obligations with owner, status and deadline; obligations that do not apply are hidden automatically.

  3. 03

    Evidence

    One piece of evidence per obligation, with a date; outdated evidence stands out.

  4. 04

    Reporting drill

    One incident, 4 reporting regimes, one timeline: the clocks per regime from the moment of awareness.

  5. 05

    Briefing

    The management briefing as a PDF of at most 4 pages, plus the obligation matrix in Excel.

Real product view · sample data
Regulatory cockpit with sample data
Explore the regulatory cockpit

Registers

Registers for evidence and reporting

The cockpit links to registers that hold the detailed work.

Real product view · sample data
ICT third-party register with sample data

No sign-up

A first assessment in a few minutes

The free readiness checks give a non-binding first assessment, without an account.

FAQ

Frequently asked questions on EU regulation

Does NIS2 apply to us?

That depends on sector and size. The German BSIG covers essential and important entities under Section 28 BSIG in the sectors of Annexes 1 and 2. The free NIS2 check and the applicability check in the cockpit give a first assessment with legal references; they are not legal advice.

What is the difference between EU DORA and DORA metrics?

EU DORA is Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. DORA metrics are software delivery metrics from the DevOps Research and Assessment programme (dora.dev). The two are unrelated, which is why Alev-B always says “EU DORA” or “DORA metrics”.

When is the reference date for the register of information?

According to BaFin, the register must reflect the position as at 31 December of the previous year; for the 2027 submission that is 31 Dec 2026. It is submitted by 31 March at the latest; BaFin announces the exact 2027 window at the start of the year, so the deadline calendar shows 31 Mar 2027 as uncertain.

What does the Digital Omnibus change?

Regulation (EU) 2026/1744 amends the AI Act. Under Art. 113 of the consolidated text, the new prohibitions in Art. 5(1), points (ba) and (bb), apply from 2 Dec 2026, the high-risk obligations for Annex III from 2 Dec 2027 and for Annex I from 2 Aug 2028.

Does this replace legal advice?

No. The cockpit, registers and calculators provide orientation and support self-assessment based on the cited primary sources (as of 26 Oct 2026). The published legal text prevails.

Can I use this without a subscription?

In part. The deadline calendar, the reporting deadline calculator and the readiness checks are free without sign-up. The regulatory cockpit, the ICT third-party register and the AI inventory are part of the Professional plan; the vendor assessment is included in the Free plan.

Further reading

Articles on deadlines and obligations

Obligations, deadlines and evidence in one place

Start for free. The regulatory cockpit is part of Professional; the deadline calendar and the reporting deadline calculator stay free.

Orientation based on the cited primary sources (as of 26 Oct 2026) – not legal advice; the text published in the Official Journal or Federal Law Gazette prevails.