Back to Articles

NIS2

Italy's NIS2 Deadline of 31 October 2026: the ACN Baseline Measures, Who It Applied To and the Evidence to Keep

13 min read

For the first cohort of Italian NIS entities, 31 October 2026 closed the 18-month window to adopt ACN's baseline measures: 37 measures and 87 requirements for important entities, 43 and 116 for essential ones. Which deadline applies to you, what evidence an inspector asks for, and what to prioritise if you are late.

nis2
acn

For most Italian organisations that ACN placed on the NIS list in 2025, 31 October 2026 was the operative deadline to have the baseline security measures in place. The date has now passed, and the question has changed from "how many days are left" to "did it apply to us, and can we prove what we did". This article explains how the deadline is calculated, what the baseline measures cover, which evidence an inspector is likely to ask for and what to prioritise if you are behind. For the wider framework, start from our complete NIS2 guide; for what happens next, see NIS2 after 31 October.

Key Takeaways

  • The deadline is personal. It runs 18 months from each entity's own notice of inclusion in the NIS list; 31 October 2026 is the date for the 2025 cohort, not for everyone.
  • The rules are in ACN Determination 379907/2025, published on 24 December 2025 and applicable from 15 January 2026.
  • Important entities have 37 measures and 87 requirements; essential entities 43 measures and 116 requirements.
  • Inspections look for evidence, not intentions: approved documents plus records showing the measures actually run.
  • If you are late, a dated, approved plan and the technical measures you can prove quickly are worth more than a perfect policy set.

Which deadline applies to you

Italy transposed NIS2 with Legislative Decree 138/2024. ACN started sending notices of inclusion in the NIS list in April 2025, and the terms for the obligations run from that notice. According to the summary by CMS, ACN Determination 379907/2025, published on 24 December 2025 and applicable from 15 January 2026, confirms two terms:

  • 18 months from the notice of inclusion to adopt the baseline security measures;
  • 9 months from the same notice for the significant incident notification obligations.
SituationBaseline measures dueIncident notification
Entity notified in spring 2025 (first cohort)31 October 2026, the date used by Italian legal and industry guidanceAlready in force since January 2026
Entity notified later18 months from its own notice9 months from its own notice
Not sureOpen the ACN notice on the NIS portal and count from its dateSame

Read your own notice. Entities added to the list in 2026 have a later deadline, and the April 2026 determinations, which we cover in our article on the April 2026 ACN determinations, changed the picture for categorisation and relevant suppliers.

What the baseline measures cover

The measures are set out in two annexes: Annex 1 for important entities and Annex 2 for essential entities. As summarised by Italian legal commentary, important entities have 37 measures broken down into 87 requirements, and essential entities 43 measures and 116 requirements: six more measures and 29 more requirements. Measure codes such as GV.RR-02, the one on including the CSIRT contact in the security organisation, follow the functions of the national cybersecurity framework, aligned with the NIST Cybersecurity Framework.

In practice, the requirements fall into these areas:

AreaWhat it means in practice
GovernanceRoles and responsibilities, management body approval of the measures, the CSIRT contact person, training for the management body
Risk managementA documented risk analysis and a treatment plan, reviewed periodically
AssetsAn inventory of systems, software, services and data flows, including what is exposed to the internet
Access and identityAccess control, privileged account management and multi-factor authentication
VulnerabilitiesA process to find, assess and fix vulnerabilities, with timings
Detection and incidentsLogging and monitoring, an incident response plan, the procedure to notify CSIRT Italia
ContinuityBackups, restore tests, business continuity and disaster recovery plans
Supply chainSupplier inventory, security requirements in contracts, assessment of ICT suppliers
PeopleSecurity awareness and training for staff

The exact wording of each requirement is in the annexes published by ACN, and you should work from those texts, not from summaries. The Orizon NIS2 guide collects the framework in one document.

Evidence: what an inspector will ask to see

After 31 October, as PuntoSicuro and other commentators note, ACN moves from accompanying entities to inspecting them. Under NIS2, essential entities are subject to ex ante supervision, so they can be inspected without any incident; important entities are mainly supervised ex post, after an incident or a report. In both cases the sequence described by commentators starts with a request for documents, continues with an assessment of the declared measures and may end with an on-site audit.

Two kinds of evidence carry weight:

  1. Approved documents. Policies, the risk analysis, the incident response plan and the continuity plan, with a date and the management body's approval. A policy nobody approved is a draft.
  2. Operating records. Proof that the measures run: scan reports and remediation tickets, access reviews, MFA coverage, backup restore tests, incident exercises, training completion records, supplier assessments.

The second kind is where most organisations are weakest. A vulnerability management policy is easy to write; twelve months of dated scan reports with the fixes that followed are not.

The technical measures you can prove quickly

Some requirements need months of organisational work. Others can be evidenced in weeks, and they are often the ones an inspector checks first because they are objective.

MeasureEvidenceHow to produce it
Internet-facing asset inventoryList of domains, hosts and services with datesContinuous external discovery of your domains
Vulnerability managementDated scan reports, proven findings, fixes and retestsScheduled external and internal scans with verification
MFA and access controlMFA coverage for admins and users, conditional access policiesRead-only posture check of Microsoft 365 or Google Workspace
Network and endpoint hygieneSegmentation, SMB signing, end-of-life systems, centralised loggingInternal scan from inside the network
BackupsRestore test record with date, scope and resultA real restore of a critical system, documented
TrainingCompletion records for staff and the management bodyAwareness platform reports

What to prioritise if you are late

Being late is not a reason to stop, and the sanctions regime does not reward waiting. If you have not completed the measures, a reasonable order is:

  1. Governance first. Have the management body formally approve the security organisation, the CSIRT contact and a remediation plan with dates. It shows the decision has been taken at the right level.
  2. Know what you expose. Build the internet-facing inventory and fix known-exploited vulnerabilities on exposed systems.
  3. Close the easiest doors. MFA everywhere, phishing-resistant MFA for administrators, no legacy authentication.
  4. Prove you can recover. Run and document a restore test of a critical system.
  5. Be ready to notify. Incident notification is already in force for the first cohort; make sure the procedure to send the 24-hour pre-notification to CSIRT Italia works, including at weekends. Our article on NIS2 incident reporting covers the timings.
  6. Then the rest: supplier assessments, the full policy set and the training programme.

After 31 October

Maximum fines under Legislative Decree 138/2024 are EUR 10 million or 2% of worldwide annual turnover for essential entities, and EUR 7 million or 1.4% for important entities, whichever is higher. Management bodies are directly responsible for approving and overseeing the measures and must follow cybersecurity training. Our article on NIS2 penalties details the regime, and NIS2 after 31 October covers inspections and what to do if you are behind.

Where Orizon fits

No tool makes an organisation compliant, and we never say otherwise. What our services produce is technical evidence for several of the requirements above, dated and repeatable:

  • RECON External discovers your internet-facing assets, verifies each finding and classifies the company as an essential or important entity with the criteria behind it. Scheduled scans and signed reports document how you find and fix vulnerabilities.
  • RECON Internal evaluates, in every internal scan, 25 technical controls related to NIS2 Article 21, such as segmentation, SMB signing, end-of-life systems, centralised logging, MFA indicators and backup detection, and marks each one Pass, Warn, Fail or Not assessed with the affected assets.
  • RECON Cloud includes the ten Article 21(2) measures in its compliance catalogue for cloud accounts and Microsoft 365 or Google Workspace, and counts a control as met only when stored configuration proves it.
  • Fireline's compliance edition cross-references confirmed findings to NIS2 Article 21 and, in Italian reports, to the ACN baseline measures an external test can observe, without ever claiming compliance.
  • Aware keeps training completion and assessment records that document awareness training under Article 20.

The NIS2 compliance page shows how these pieces map to Article 21, and compliance automation explains how to keep the evidence current without rebuilding it before every audit.

Checklist

  1. Find your ACN notice and calculate your own 18-month and 9-month dates.
  2. Download Annex 1 or Annex 2 of Determination 379907/2025 and map each requirement to an owner.
  3. Get the management body's formal approval of the security organisation and the plan.
  4. Build the internet-facing inventory and run verified vulnerability scans, external and internal.
  5. Check MFA coverage and conditional access in your email and identity tenant.
  6. Run and document a backup restore test.
  7. Test the CSIRT Italia notification procedure.
  8. Collect training records for staff and the management body.
  9. Keep everything dated, approved and in one place.

If you want to start with the evidence that is quickest to produce, a RECON scan of your domains and your internal network gives you dated, verified results within days. Talk to us through the NIS2 compliance page and we will tell you honestly which requirements our services cover and which they do not.

nis2
acn
italy
baseline-measures
compliance-evidence
d-lgs-138-2024