NIS2 Compliance in 2026: Where the Directive Stands Two Years On

Four colleagues in conversation around a meeting table by a window with a large plant, one seen from behind in the foreground.

Two years on, the NIS2 framework finds its footing. NIS2 compliance in November 2026 is easier to plan for than it was two years ago. Most Member States have now transposed the Directive. The EU is simplifying the rules, starting with common incident-reporting templates and a proposed single reporting entry point. Enforcement has been measured so far, but that is a phase, not a promise. 

Key takeaways 

  • Transposition is well advanced. National rules are in place in most Member States, but they still differ across 27 countries. 
  • Simplification is the 2026 theme. In January 2026, the European Commission proposed targeted amendments that ease the load for an estimated 28,700 companies. 
  • Incident reporting is the pain point and the fix. Common templates were adopted in May 2026, and an implementing act will make them mandatory. 
  • Boards are now involved. Article 20 has made cybersecurity a leadership topic. 

Where does NIS2 stand two years after the deadline? 

The NIS2 Directive (EU) 2022/2555 had a transposition deadline of October 17, 2024. Two years on, it is an established part of the European regulatory landscape. The framework is largely in place, implementation is still maturing, and policy is moving towards simplification. 

This article walks you through what has changed, what the sector is saying, and what to do next. You will find: 

  • How far transposition has come, and where gaps remain 
  • What the 2026 simplification measures mean for you 
  • How to prepare your incident reporting and board reporting for 2027 

How far has NIS2 transposition come? 

Most Member States have now transposed NIS2, but the work is not finished. When the deadline passed in October 2024, only a limited number of Member States had fully transposed the Directive. By May 7, 2025, the European Commission had sent reasoned opinions to 19 Member States, from Germany, France, Spain and Estonia to Finland, Ireland and Sweden. Each had two months to comply or face referral to the Court of Justice. In infringement proceedings of this kind, referral is a last resort that typically follows extended dialogue, and the formal assessment of national measures is continuing. 

The result is a familiar EU pattern: national regimes ranging from early and comprehensive to still being refined. Areas still in motion include registration portals, sector lists and supervisory practice. 

Why this matters if you operate across borders 

One Directive means 27 national rulebooks. If you work in several countries, you still need to track each one. Start with a single internal baseline, then map the national differences on top of it. 

What has changed in NIS2 in 2026? 

The EU has moved from building the framework to streamlining it. In January 2026, as part of a new cybersecurity package, the Commission proposed targeted amendments to NIS2. The aim is more legal clarity and simpler compliance. The Commission estimates it will ease the burden for 28,700 companies, including 6,200 micro and small enterprises. 

Common incident-reporting templates 

In May 2026, the NIS Cooperation Group adopted common templates for incident reporting. The Commission calls them “a significant step towards simplifying compliance for companies.” An implementing act is planned to make them mandatory across the EU. 

A single entry point for incident reports 

The templates are designed to align with the proposed single entry point under the Digital Omnibus. The idea is simple: one notification channel instead of parallel reports to several authorities under several legal regimes. 

Taken together, these steps show the EU has listened to feedback from the first years. It is cutting administrative burden and keeping the substance of the framework. 

What does the sector think about NIS2? 

Support for the goal is broad. Few dispute that critical entities should manage cyber risk systematically. The discussion is about how it works in practice. The sectors in scope include energy, health, transport, digital infrastructure, ICT service management and public administration, among others. 

Four themes come up again and again: 

  • A developing framework. National transpositions arrived at different times and in different forms, and supervisory guidance followed. Companies that invested early can now align with the 2026 measures. Many see the amendments as a refinement, not a disruption. 
  • Incident reporting. The rhythm under Article 23 is a 24-hour early warning, a 72-hour notification and a final report after one month. Applied across national regimes and parallel EU rules (the General Data Protection Regulation, the Digital Operational Resilience Act (DORA) and the Cyber Resilience Act (CRA, whose reporting obligations become applicable in December 2026)  it created a heavy workload. The new templates and single entry point target exactly that friction. 
  • Board accountability. Management responsibility under Article 20 has moved cybersecurity from a technical topic to a board-level one. Security leaders generally report that this helps secure budget and attention, which is what the drafters intended. 
  • A learning curve for mid-sized entities. The scope brought thousands of medium-sized companies into sectoral supervision for the first time. Easing the burden for micro and small entities keeps obligations for larger ones and right-sizes them at the smaller end. 

Is NIS2 being enforced yet? 

Enforcement has been measured. Supervisory authorities have focused on registering entities, issuing guidance and carrying out inspections. Large headline fines under NIS2 have so far been rare in publicly reported cases. Most companies see this as a transitional phase and plan accordingly. 

How to prepare your NIS2 compliance program for 2027 

Use this phase to mature your program before fuller enforcement arrives. Three steps help most. 

  1. Keep incident-reporting processes flexible. Build one internal process that can feed several national and EU regimes. When templates become mandatory, you adapt the output, not the process. 
  2. Follow the implementing act and the Digital Omnibus. Track the act on common templates and the progress of the single entry point. These two will shape how you report. 
  3. Treat today’s supervision as your runway. Test your processes, close gaps and document decisions while supervision is constructive. 

Common challenges and how to meet them 

Challenge  Practical solution  Where to focus 
27 national rulebooks  Keep one internal baseline, map national differences on top  Registration, sector lists, supervisory practice 
Parallel reporting under NIS2, GDPR, DORA and CRA (applicable from December 2026)  Design one reporting process with several outputs  The 24-hour, 72-hour and one-month steps under Article 23 
Board expectations under Article 20  Give leadership regular, plain-language risk reporting  Budget, ownership and decision records 

Looking ahead: WithSecure’s outlook for NIS2 

What comes next is not yet written, but the direction looks clear to us. The January 2026 amendments read like the opening move of a wider consolidation. If simplification works, we would expect: 

  • Discussion of a single reporting architecture across NIS2, DORA and the CRA 
  • A shift from constructive to fuller enforcement as supervision matures 
  • In time, a deeper revision informed by the first generation of compliance experience 

Our outlook for 2027: less a new directive, more the quiet maturing of this one. Expect mandatory common templates, a working single entry point and growing practice that shapes what “NIS2, refined” looks like. Flexible, harmonized reporting processes are, in our view, the closest thing to future-proofing you can build today. 

Build a reporting process that lasts 

NIS2 is settling in, and the direction is clear: more harmonisation, proportionate burden. You do not need to wait for the final rules to get ready. We are happy to talk through your reporting setup, starting with a conversation, not a sales pitch. 

Contact us 

 

Sources 

  1. European Commission: NIS2 Directive, securing network and information systems (updated July 2, 2026) 
  2. European Commission: NIS2 Directive transposition in EU countries 
  3. European Commission: NIS2 Cooperation Group adopts common templates for incident reporting (May 26, 2026) 

 

Frequently asked questions about NIS2 in 2026 

What is NIS2? NIS2 is the EU Directive (EU) 2022/2555 on network and information security. It sets cybersecurity risk management and incident reporting duties for entities in sectors such as energy, health, transport, digital infrastructure and public administration. 

Have all EU countries transposed NIS2? Most have, but not all work is complete. The Commission sent reasoned opinions to 19 Member States in May 2025, and its formal assessment of national measures continues. Some countries are still refining registration portals, sector lists and supervisory practice. 

What are the NIS2 incident reporting deadlines? Article 23 sets a 24-hour early warning, a 72-hour incident notification and a final report after one month. Common EU templates adopted in May 2026 are meant to make these reports simpler. 

What is the Digital Omnibus single entry point? It is a proposed single channel for incident reporting. It would replace parallel reports to multiple authorities under multiple legal regimes. The common NIS2 templates are designed to align with it. 

Who is responsible for NIS2 compliance in an organisation? Under Article 20, management carries responsibility. Cybersecurity is a board-level topic, not only a technical one. 

Blog post

Read our latest blogs

AI Security hero image with iceberg

Blog

AI AI Security MSP

Managed AI Security services: A roadmap for MSPs

AI Security hero image with iceberg

Blog

AI AI Security MSP

Shadow AI Security: A four-step framework for MSPs

Overhead view down a wooden staircase of two people working on laptops in a casual seating nook below.

Blog

Exposure Management MSP

Why Endpoint Protection is no longer enough