EU security laws: which apply to you and what is due when?

Check which of your legal entities fall under NIS2 or DORA and which products under the CRA, since all three require a first report within 24 hours123. Then resolve overlaps by role: DORA replaces NIS2's risk and reporting rules for financial entities1 and the CRA adds product duties, so one group can face all three.

Reviewed
Next review
Version
1.2
Written for
IT, security and compliance leads in EU organizations, especially in Germany

If you only do five things

This is guidance, not legal advice.

  1. Decide scope per legal entity and product.

    NIS2 and DORA apply to entities14, the CRA to products with digital elements and their manufacturers, importers and distributors3. Record the sector and size figures you used.

  2. Run one incident process with several clocks.

    NIS2 and the CRA require an early warning within 24 hours13 and DORA an initial notification within 4 hours of classification as major2. Name who classifies incidents and who sends each report.

  3. Have management sign off and take training.

    Management bodies must approve and oversee the NIS2 risk management measures and take training, and they can be held liable1. Put both on the board calendar.

  4. Map your controls to the NIS2 measures.

    Article 21 requires measures in at least ten areas, from incident handling and backups to supply chain security and multi-factor authentication1. Give each gap an owner and a date.

  5. Put the duties into supplier contracts.

    DORA requires a register of information on all ICT service contracts4 and NIS2 requires supply chain security1. Add security update, incident notification and audit clauses at renewal.

Find out which laws apply to you

  1. Do you supply connected products in the EU?

    If you make, import or distribute hardware or software that connects to a device or network, the CRA applies to those products3. Medical devices, motor vehicles and certified aviation products are excluded, as are cloud services that aren't remote data processing for a product3.

  2. Are you a financial entity under DORA?

    DORA lists 20 types, including credit institutions, payment and e-money institutions, investment firms, crypto-asset service providers, insurers and fund managers4. For them it replaces NIS2's risk management, reporting and supervision1.

  3. Is your sector in NIS2 Annex I or II?

    NIS2 covers 18 sectors, among them energy, transport, health, finance, digital infrastructure, digital services, critical product manufacturing, waste, postal services and public administration5. If no annex lists your type of entity, NIS2 generally doesn't apply1.

  4. How big is the entity?

    An Annex I or II entity is in scope with 50 or more employees, or with turnover and balance sheet both above €10 million. An Annex I entity is essential with 250 or more employees, or with turnover above €50 million and a balance sheet above €43 million61. Telecom, trust service and DNS providers and TLD registries are in scope at any size1.

The three laws side by side

NIS2

  • Who. Medium and large entities in the Annex I and II sectors, plus telecom, trust service and DNS providers and TLD registries at any size1.
  • Duties. Management-approved risk management measures in at least ten areas, incident reporting and registration with the national authority1.
  • Dates. Member States had to apply it from 18 October 20241.
  • Penalties. Maximum fines of at least €10 million or 2% of worldwide turnover, whichever is higher, for essential entities and €7 million or 1.4% for important ones1. Managers of essential entities can be temporarily barred1.

DORA

  • Who. 20 types of financial entity4, plus critical ICT providers: 19 designated in November 2025, including AWS, Microsoft and SAP7.
  • Duties. An ICT risk management framework owned by the management body, major incident reporting, resilience testing and a register of information on all ICT service contracts4. Threat-led penetration tests at least every 3 years for entities their supervisor selects4.
  • Dates. Applies since 17 January 20254.
  • Penalties. Set by Member States, also for management body members4. Daily penalties of up to 1% of average daily worldwide turnover for critical ICT providers4.

CRA

  • Who. Manufacturers, importers and distributors of connected hardware and software in the EU3.
  • Duties. The Annex I security requirements, a software bill of materials, CE marking and vulnerability handling for a support period of at least 5 years, or the expected use time if shorter3.
  • Dates. In force since 10 December 20248. Reporting applies from 11 September 2026 and the remaining duties from 11 December 20273.
  • Penalties. Up to €15 million or 2.5% of worldwide turnover for breaches of Annex I or Articles 13 and 143.

What you can skip

  • Waiting for the proposed changes. Neither the reporting rules in the general Digital Omnibus nor the NIS2 amendments are law yet910, and the proposed single entry point would keep today's reporting duties and recipients11.
  • A separate compliance program for each law. Keep one risk register for all three and add law-specific steps only where the duties differ.
  • Reporting every alert. NIS2 requires reports only for incidents that cause or could cause severe operational disruption, financial loss or considerable damage to others1. Give the on-call team written thresholds.

Mistakes that cost the most

  • Leaving group companies out of the size test. The EU test adds the figures of linked and partner enterprises6.
  • Waiting for the full picture to report. The NIS2 early warning only has to say whether you suspect unlawful or malicious acts or cross-border impact1.
  • Forgetting products already on the market. CRA reporting also covers products placed on the market before December 20273.
  • Missing the implementing regulation. Cloud, data center, managed service and other digital providers must also meet the detailed requirements of Implementing Regulation (EU) 2024/269012.

Reporting clocks

Each clock starts when you become aware, unless noted.

NIS2

Significant incidents, to the CSIRT or competent authority; in Germany, the BSI13. The final report is due 1 month after the notification1.

  1. 24 hoursEarly warning
  2. 72 hoursIncident notification
  3. 1 monthFinal report

DORA

Major ICT-related incidents, to the competent authority. The 4 hours run from classification, capped at 24 hours after awareness unless you classify later; later clocks run from the previous report2.

  1. 4 hoursInitial notification
  2. 72 hoursIntermediate report
  3. 1 monthFinal report

CRA

Manufacturers, through ENISA's platform15. The final report is due 14 days after a fix for actively exploited vulnerabilities and 1 month after the notification for severe incidents3.

  1. 24 hoursEarly warning
  2. 72 hoursNotification
  3. 14 daysFinal report

Germany: the NIS2 Implementation Act

  • The law took effect on 6 December 2025. The act was published in the Bundesgesetzblatt on 5 December 2025, with no general transition period1617. It applies to about 29,500 companies and federal institutions18.
  • The registration deadline has passed. Entities must register within 3 months of falling under the law, so the first deadline passed in March 20261319. If you haven't registered, get an ELSTER organization certificate through Mein Unternehmenskonto, then register in the BSI portal19, open since 6 January 202618. Report changes within 2 weeks13.
  • DORA entities must register too. They are exempt from the BSIG's risk management, reporting and management body duties, and the BSIG rules out reporting the same incident under both laws17.
  • Energy operators follow the EnWG. Grid and energy plant operators meet their security and management duties through the Federal Network Agency's IT security catalogs under §§ 5c and 5e EnWG, but still register with and report to the BSI1314.
  • Group figures can be left out. The BSIG excludes linked and partner enterprises from the size test if your IT systems run independently of theirs13.
  • Management is liable to the entity. It must implement and oversee the risk management measures and attend regular training, and it is liable for culpable damage under company law13.

What changed in 2026

  • CRA reporting started. Since 11 September 2026 manufacturers must report actively exploited vulnerabilities and severe incidents3.
  • The Commission proposed NIS2 amendments. Its proposal of 20 January 2026 would clarify the scope to ease compliance for 28,700 companies, add a small mid-cap category and simplify jurisdiction rules20. It still awaits a committee decision in Parliament10.
  • The Council wants national reporting entry points. The general Digital Omnibus, separate from the one on AI, would let you file NIS2, DORA, GDPR and other reports through one ENISA entry point11. The Council's position of 21 October 2026 swaps it for one national entry point per Member State and backs a longer GDPR breach deadline; Parliament has not adopted its position yet9.