NIS2 timeline: which deadline actually applies to you
Short answer. There is no single NIS2 deadline, which is why the dates seem contradictory. NIS2 has applied across the EU since 18 October 2024. Everything after that runs on national timetables — registration, reporting and security-measure deadlines all differ by member state. The widely quoted "October 2026" is Italy's deadline, not the EU's.
Last reviewed: 31 July 2026.
Which deadline applies to you
Work through it in this order. It takes about five minutes and settles the question properly.
- Which member states do you have in-scope entities in? The analysis is per legal entity, per country — not per group.
- For each, is the transposing law in force? If yes, that law's commencement dates bind you. If not, you have no directly enforceable NIS2 duties there yet.
- Have you been notified or registered? Several states run a registration step that starts a clock personal to you — your deadline is measured from your notification date, not from a national announcement.
- What did that notification give you time to do, and by when? Registration, incident reporting and full security measures usually have different dates.
- Separately: what are your customers contractually requiring, and when? This is frequently the earliest real deadline you face, and it is unaffected by your own state's progress.
Three clocks not one
Nearly all the confusion comes from three different clocks being quoted as if they were the same one.
A headline saying "the NIS2 deadline is X" has almost always collapsed one of these into another.
The EU level dates
These are fixed in the directive and are the same everywhere:
Note what is not on this list: any date in 2026. There is no EU-level NIS2 milestone in 2026 at all.
Where the October date comes from
"October 2026" is a genuine, hard deadline — for Italy.
Italy transposed NIS2 through Legislative Decree No. 138 of 4 September 2024, in force from 16 October 2024. Its national authority, the ACN (Agenzia per la Cybersicurezza Nazionale), built the Italian NIS list and notified entities of their inclusion by 15 April 2025. Those entities were then given 18 months to have the basic security measures fully implemented — which lands in October 2026.
So the date is real, it is legally binding, and it is national. What it is not is an EU-wide "full enforcement" deadline. If you have no Italian in-scope entity, October 2026 has no particular significance for you — and if you are in a member state that is already supervising, treating it as your deadline would leave you late by well over a year.
This one is worth watching for, because it has propagated widely into vendor marketing and compliance blogs as though it applied everywhere.
The Italian timetable
Italy is worth walking through in full, both because it is the source of the October 2026 figure and because it is a clear illustration of how a national clock actually works:
Two things to take from it. First, the security-measure deadline is measured from the notification, so an entity added in a later cycle gets a later deadline — this is a "your clock" date, not a national one. Second, the obligations arrived staged: registration, then reporting, then measures. Several member states have used the same shape, so if you are looking for your own dates, look for that pattern rather than a single cliff edge.
Why the clocks drifted apart
NIS2 is a directive, not a regulation. It obliges member states to achieve a result and leaves them to legislate. GDPR and DORA are regulations — one text, one date, everywhere. NIS2 is deliberately not that.
Add to it that a substantial number of member states missed the 17 October 2024 transposition deadline, prompting Commission infringement proceedings. Their laws arrived later, with their own commencement dates and their own phase-in periods. The result is a genuine patchwork, and a group operating in eight member states can be facing eight different timetables under one directive.
Article 5 also lets member states go further than the directive. So national law can be stricter as well as later.
What if your member state was late
Late transposition is not breathing room, for three reasons:
- Lead times compress rather than disappear. Late national laws have tended to commence quickly after adoption, sometimes with registration due within weeks. The underlying work — scoping, supplier assessment, contract remediation, evidence — takes months either way.
- Your customers are already bound. If you supply an entity in an early-transposing state, its Article 21(2)(d) supply chain duties reach you through contract now. See Who counts as a direct supplier under NIS2?
- The scarce resource is other people's time. Supplier assessments and contract changes depend on third parties responding to you. That queue does not shorten because your government was slow.
How to find your own dates
Do not rely on a summary — including this one — for the dates that bind you:
- Go to your national competent authority's site for each member state where you have an in-scope entity. That is the authoritative source for commencement, registration and phase-in.
- Find your registration status and notification date. If a clock runs from notification, that date is the single most important one you hold.
- Separate the three deadlines — registration, incident reporting, security measures — because they rarely coincide.
- Write it down per entity, per country, with the authority, the portal, the contact and the dates. A group-level "NIS2 deadline" is not a real thing.
- Re-check periodically. Transposition and secondary guidance are still moving in several states.
Then work backwards from the earliest date, and start with supplier work — it has the longest lead time. The NIS2 supply chain compliance checklist sequences it.
Related: What is NIS2? · Who does NIS2 apply to? · NIS2 incident reporting timelines
Frequently asked questions
- What is the NIS2 deadline?
- There is no single one. NIS2 has applied across the EU since 18 October 2024, but the dates that bind you come from your member state’s transposing law, which sets its own registration, reporting and security-measure deadlines.
- Is October 2026 a NIS2 deadline?
- It is Italy’s, not the EU’s. Entities on the ACN’s Italian NIS list were notified by 15 April 2025 and given 18 months to fully implement the basic security measures, which lands in October 2026. The date appears in no EU-level provision.
- Did NIS2 already come into force?
- Yes. It entered into force on 16 January 2023, member states had to transpose it by 17 October 2024, and national measures have applied since 18 October 2024, when the original NIS Directive was repealed.
- What happens if my member state transposed NIS2 late?
- You have no directly enforceable NIS2 obligations until national law is in force, but late laws have tended to commence quickly with short lead times. Your customers’ supply chain duties reach you by contract in the meantime, regardless of your own state’s progress.