vendorapp logo

Docs

What changed between NIS and NIS2?


Short answer. NIS2 replaced member-state discretion over who was covered with an objective sector-plus-size rule, turned vague security duties into ten mandatory minimum measures, fixed incident reporting at 24 hours / 72 hours / one month, added management-body liability, harmonised fines — and made supply chain security an explicit named obligation for the first time.

Last reviewed: 31 July 2026.

What changed between NIS and NIS

Directive (EU) 2016/1148 — the original NIS Directive — was the EU's first cross-sector cybersecurity law. It worked as a proof of concept and failed as a harmonisation measure. NIS2, Directive (EU) 2022/2555, repealed it with effect from 18 October 2024.

Why the first directive was replaced

The Commission's own review identified three structural problems:

  • Inconsistent scope. Member states individually identified "operators of essential services", using different criteria. The same type of company was regulated in one country and unregulated next door.
  • Weak, unenforceable requirements. Security duties were expressed at high abstraction with little supervisory apparatus behind them.
  • Fragmented reporting and supervision. Thresholds, timelines and sanctions varied so widely that cross-border incident response was hampered.

Add a threat landscape that had shifted decisively toward supply chain and ransomware attacks, and a rewrite rather than an amendment was the natural conclusion.

The changes that matter most

NIS (2016/1148)NIS2 (2022/2555)
ScopeMember states identified operators of essential services individuallyObjective rule: Annex I/II sector plus medium-size threshold, with size-independent exceptions
CategoriesOperators of essential services; digital service providers (light-touch)Essential entities; important entities — same measures, different supervision
Sectors7 sectors plus 3 digital service types18 sectors across Annex I and Annex II
Security measuresHigh-level "appropriate and proportionate" dutyTen enumerated minimum measures in Article 21(2)
Supply chainNot namedExplicit measure (d), reinforced by Article 21(3) and Article 22
Incident reporting"Without undue delay", nationally defined24-hour early warning, 72-hour notification, one-month final report
GovernanceNot addressedArticle 20: management-body approval, oversight, training, liability
SanctionsNational discretionHarmonised minimum maxima: €10m/2% and €7m/1.4%
SupervisionVariedEx ante for essential entities, ex post for important entities
RegistrationVariedNational lists and entity registration duties
Cross-borderLimited cooperationStrengthened Cooperation Group, CSIRTs network, EU-CyCLONe for large-scale crisis

Scope — from national discretion to a size rule

Under NIS, being regulated depended on whether your national authority had designated you. Under NIS2 it depends on facts about your business: which sector you operate in, and how big you are.

The consequences are practical rather than philosophical. You can now determine your own status without waiting to be told, the same group is treated consistently across member states, and far more organisations — particularly mid-market manufacturers, food producers, waste operators and MSPs — are in scope for the first time. See Who does NIS2 apply to?

From vague measures to a minimum list

The original directive required "appropriate and proportionate technical and organisational measures". NIS2 keeps that standard but enumerates ten measures underneath it.

This changes the nature of a supervisory conversation. Previously the argument was about whether your overall posture was appropriate. Now the first question is whether each of the ten exists at all, and only then how deeply it is implemented. There is no longer a defensible answer that omits, for example, supply chain security.

From undue delay to a fixed clock

"Without undue delay" was interpreted in practice as anything from hours to weeks. Article 23's staged deadlines removed the ambiguity, and deliberately set the first stage low-content: a 24-hour early warning that says something significant is happening, not a root cause analysis.

The operational consequence is that detection-to-decision has to be fast, which is an organisational capability rather than a documentation one. See NIS2 incident reporting timelines.

The new supply chain obligation

The single largest addition for most organisations. NIS said nothing specific about suppliers. NIS2:

  • lists supply chain security as minimum measure (d), covering the security aspects of the relationship with each direct supplier and service provider;
  • requires entities in Article 21(3) to take account of each supplier's specific vulnerabilities, the quality of their products and cybersecurity practices, and their secure development procedures;
  • creates Article 22 coordinated Union-level risk assessments of critical supply chains, whose results entities must factor in;
  • brings MSPs and MSSPs into scope as regulated entities in their own right.

This is why supply chain work dominates most NIS2 programmes: it is the area with the least existing capability and the longest lead time, because progress depends on third parties responding to you. Start at Does NIS2 require vendor risk assessments?

What to do if you complied with the first directive

Former operators of essential services have a real head start, but four checks are worth doing deliberately:

  1. Re-verify scope and category. Old OES designation does not map cleanly to essential/important. Confirm per legal entity and per member state, and check whether other group entities are now caught.
  2. Gap the ten measures. Most former OES are strong on (a), (b) and (c) and weak on (d), (f) and (j).
  3. Close the governance gap. Management-body approval, oversight cadence, training records — these rarely exist in NIS-era programmes.
  4. Rebuild the reporting path against the clock. Test that you can file within 24 hours, including out of hours, and log timestamps.

Then work the supply chain measure as its own programme, because it is the one that cannot be delivered quickly. The NIS2 supply chain compliance checklist is a sequenced starting point.

Frequently asked questions

What is the difference between NIS and NIS2?
NIS2 replaced national discretion over scope with an objective sector-plus-size rule, listed ten mandatory security measures, fixed incident reporting at 24 hours, 72 hours and one month, added management liability, harmonised fines, and made supply chain security an explicit obligation.
Is the original NIS Directive still in force?
No. Directive (EU) 2016/1148 was repealed with effect from 18 October 2024, the day national measures transposing NIS2 became applicable.
If we complied with NIS, are we compliant with NIS2?
Not automatically. Former operators of essential services have a head start on measures and reporting, but need to re-verify scope and category, close the supply chain and governance gaps, and adapt to the fixed reporting deadlines.