31 October came and went, and in many companies nothing happened. No certified email, no inspection, no form to send. It is tempting to conclude that NIS2 can wait a little longer.
It can’t, and the numbers from Italy’s National Cybersecurity Agency (ACN) say why. On 18 September 2026 ACN announced it had updated the list of NIS entities after reviewing, between May and July, more than 2,000 late registrations and about 2,000 revision cases. The list is being checked and corrected one company at a time. And on 1 January 2027 the registration window opens again.
This article is for companies that passed the NIS2 deadline with work still open. It lays out a six-week plan: start in mid-November and you reach the end of December with your paperwork in order, in time for January.
In short
For entities added to the Italian NIS list in 2025, the deadline for the NIS2 baseline security measures expired in October 2026: 18 months from the notice of inclusion, so the exact date differs from company to company. There is no NIS2 certificate to file. What exists is the possibility that ACN asks you to show what you have done. If you are late, don’t stop: find out how much is missing, close what matters first and keep a record of everything. The next fixed date is the registration window, from 1 January to 28 February 2027.
NIS2: what actually expired on 31 October
31 October is the date you read everywhere, but the rule is different. ACN’s page on the baseline specifications says the measures must be adopted within 18 months of receiving the notice of inclusion in the national NIS list. The first notices went out in mid-April 2025, so for many companies the deadline fell in mid-October, before the 31st.
The measures are those in ACN Determination 379907/2025. Important entities apply Annex 1: 37 measures, broken down into 87 requirements. Essential entities apply Annex 2: 43 measures and 116 requirements. The duty to report significant incidents to CSIRT Italia has been in force since January 2026: early warning within 24 hours, notification within 72 hours, final report within one month.
Two clarifications. Entities added to the list for the first time in 2026 follow a different calendar, set by ACN Determination 127434/2026: incident reporting from 1 January 2027 and baseline measures by 31 July 2027. And at the time of writing ACN has granted no extension to the 2025 group.
What ACN can ask a NIS2 entity for
Legislative Decree 138/2024 gives the Agency powers of verification and inspection. For essential entities, checks can also be preventive. For important entities they normally follow an incident or a report. Either way the question is the same: show me.
A statement is not enough. You need documents with a date and a signature, and proof that what they say really happens. In practice:
- the resolution by which the management body approves how the measures are implemented, and the record of the training it attended (Article 23 of the decree);
- an up-to-date risk analysis, with the name of its owner;
- the inventory of systems, networks and services;
- the incident handling procedure, with the names of whoever sends the early warning and their deputies;
- the result of the last backup restore test, with date and measured times;
- the list of critical suppliers and the checks carried out on them;
- logs showing who accesses what, and multi-factor authentication where required.
The maximum NIS2 fines are well known: up to 10 million euros or 2% of worldwide annual turnover for essential entities, up to 7 million or 1.4% for important ones. Failing to register carries a fine of up to 0.1% of turnover, as ACN’s registration page points out. That said, for an SME the first NIS2 check is rarely an inspection. More often it is a questionnaire from a customer who has to answer for its own supply chain.
The six-week NIS2 plan
Six weeks are not enough to build everything from scratch. They are enough to know where you stand, close what can be closed quickly and put the rest in writing with dates and owners. In front of a check, a delay that is documented and managed weighs far less than one nobody has measured.
Week 1: your date and your data
Find the notice of inclusion in the list and count the 18 months. Check whether you are an important or an essential entity. Then log in to the ACN services portal and make sure the point of contact, the deputy and the CSIRT contact are people who still work for you and pick up the phone.
Week 2: the gap, requirement by requirement
Take the annex that applies to you and write one label next to each requirement: done with evidence, done without evidence, not done. The second column almost always surprises. Many SMEs have backups, managed antivirus and a patched firewall, and no document that proves it.
Week 3: what closes in a few days
Multi-factor authentication on administrative and remote access. A real backup restore test, with a stopwatch. An updated inventory. The incident procedure on one page, with names and phone numbers. These are short jobs and they are among the first things a check looks at.
Week 4: the board
NIS2 places responsibility on the management bodies, not on the IT manager. You need a meeting with an agenda, a resolution approving the measures and the plan, and the directors’ training on record. Without this week, everything else stays a technical job the board has never seen.
Week 5: test the notification and count your suppliers
Run a tabletop exercise: ransomware on a Friday evening. Who notices, who decides, who sends the early warning within 24 hours, and from which computer if the network is down. Write down what did not work. In the same week, prepare the list of relevant suppliers, which since 2026 has to be reported in the annual information update, from 15 April to 31 May.
Week 6: the file and the remediation plan
Put everything in one folder, ordered by measure. For each requirement still open, write four things: who owns it, by when, how you will know it is closed, what evidence will remain. Have this plan approved too. It is the document that makes the difference if someone asks.
January and February: the 2027 NIS2 registration
From 1 January to 28 February each year, NIS entities register or update their registration on the ACN platform. The rules in force are those of ACN Determination 314287/2026. According to early readings of the text, entities already on the list will find a pre-filled declaration and will need to act only if something has changed: offices, contacts, services, size. It pays to arrive with the data already checked in week 1.
Then the calendar repeats: annual information update from 15 April to 31 May, listing and categorisation of activities and services from 1 May to 30 June. Meanwhile ACN has opened the consultation on enhanced security measures, which will supplement and replace the baseline ones. They have no date yet, but the direction is clear enough: companies with documented baseline measures start from there, the others will have to catch up twice.
What you can delegate and what you can’t
An IT provider can do much of the technical work NIS2 requires: monitoring, patching, backup, log collection, the periodic security test. It can also help you gather evidence and prepare a notification. Responsibility towards ACN, though, stays with the company and its directors. Be wary of anyone selling NIS2 compliance as a package you buy and forget.
That is how we work. We start with a two-to-three-week gap analysis on the annex that applies to you, hand over the list of requirements with status and priorities, and you decide what to keep in-house. The full method is on our NIS2 compliance for SMEs page.
If you have passed the deadline and don’t know how much is missing, write to us: we will tell you which week of the plan you are in and what to close first.
Sources: ACN, pages on baseline specifications and registration, and the note “Le novità per i soggetti NIS” (18 September 2026); ACN Determinations 379907/2025, 127434/2026 and 314287/2026; Legislative Decree no. 138 of 4 September 2024.