Back to Articles

NIS2

NIS2 After 31 October: ACN Supervision, What to Expect and What to Do If You Are Behind

10 min read

The 31 October 2026 deadline for the ACN baseline measures has passed for most Italian NIS entities listed in 2025. What ACN can verify under Articles 36 and 37 of Legislative Decree 138/2024, what is confirmed and what is rumour, and a plan if you are late.

nis2
acn

For most Italian entities placed on the NIS list in 2025, the deadline to adopt the ACN baseline security measures fell on 31 October 2026. Eleven days later, two questions dominate: what happens now, and what should you do if you are not ready? This article separates what is confirmed from what is rumour, explains the verification and enforcement powers that Legislative Decree 138/2024 gives the National Cybersecurity Agency (ACN), and sets out a practical plan for organisations that are behind. It follows our piece on the baseline measures to have ready by 31 October and fits into our complete NIS2 guide.

Key Takeaways

  • 31 October 2026 was the deadline for most of the 2025 cohort, not for everyone. The 18 months run from each entity's own ACN inclusion notice; entities added in 2026 have until 31 July 2027.
  • ACN's powers are written in Articles 36 and 37 of Legislative Decree 138/2024: document checks, on-site and remote inspections including random checks, requests for data, ordered audits and security scans, binding instructions and formal warnings.
  • Essential and important entities are treated differently. For important entities, inspection powers apply only when ACN has evidence or indications of possible violations, and ACN cannot impose periodic audits on them.
  • No public inspection calendar has been published. Claims about specific start dates for inspections are not backed by an official ACN source.
  • If you are late, the worst position is the undocumented one. A dated plan approved by management, with priorities, owners and evidence of progress, is what you can show.

Where We Are: Confirmed Facts and Rumours

StatementStatusSource
Entities on the 2025 NIS list have 18 months from their ACN inclusion notice to adopt the baseline measuresConfirmedLegislative Decree 138/2024 and ACN Determination 379907/2025
For most of the 2025 cohort, whose notices started in April 2025, the deadline was 31 October 2026Confirmed for most, not all: check your own noticeACN notices and Italian legal guidance
ACN can carry out document checks, on-site and remote inspections, random checks and data requestsConfirmedArticle 36, Legislative Decree 138/2024
Entities added in 2026 must adopt the baseline measures by 31 July 2027ConfirmedACN Determination 127434/2026 of 13 April 2026
Formal inspections start on a specific date in November 2026Not confirmedNo official ACN calendar found
ACN granted an extension of the 31 October deadlineNot confirmed; Italian sources report no extensionSecondary sources

According to an analysis published by noze, no inspection calendar appeared on ACN's NIS pages as of 9 November 2026. In the absence of an official schedule, the useful question is not "when will they come?" but "what would I show them if they asked tomorrow?".

Does 31 October Apply to You?

The deadline is not a single date fixed in law. ACN Determination 379907/2025 sets the baseline specifications (according to the same analysis, 37 measures for important entities and 43 for essential entities) and gives 18 months from receipt of the inclusion notice. ACN started sending notices to the first cohort in April 2025, which is why 31 October 2026 became the reference date. Your date is the one in your own notice, received by certified email (PEC).

Your situationKey dates
On the NIS list since 2025 (notice received in April 2025)Baseline measures due by 31 October 2026, 18 months from your notice
On the NIS list since 2025, notice received later18 months from the date of your notice
Added to the NIS list in 2026CSIRT contact person designated by 31 December 2026; incident notification from 1 January 2027; baseline measures by 31 July 2027 (Determination 127434/2026)
Every NIS entity, every yearRegistration or update on the ACN platform; annual update including the list of relevant NIS suppliers (15 April to 31 May); categorisation of activities and services (1 May to 30 June)

Sources: ACN determinations as summarised by CMS and noze. For the April 2026 determinations, see our article on relevant suppliers and categorisation.

What ACN Can Do: Articles 36 and 37

Verification and inspection (Article 36)

Article 36 of Legislative Decree 138/2024 allows the national NIS authority to subject entities to:

  • checks of the documentation and information sent to the authority;
  • on-site and remote inspections, including random checks;
  • requests for access to data, documents and other information, stating the purpose and specifying what is requested.

Paragraph 2 makes the key distinction: for important entities, these powers apply only when the authority acquires or receives evidence, indications or information suggesting possible violations. For essential entities, supervision can be proactive.

Enforcement measures (Article 37)

Article 37 lists what ACN can require, including:

  • evidence of implemented cybersecurity policies, such as the results of security audits;
  • periodic or targeted security audits (periodic audits cannot be imposed on important entities; targeted ones can, for example after a significant incident);
  • security scans based on objective, non-discriminatory and transparent risk criteria;
  • implementation of audit recommendations, compliance with binding instructions and correction of deficiencies, within reasonable deadlines and with progress reports;
  • the appointment of an ACN official to support the entity for a defined period, with full cooperation required;
  • a formal warning (diffida) if the entity does not comply.

Before adopting these measures, ACN must notify its preliminary findings and allow at least fifteen days for observations, except where immediate action is needed to stop or respond to an incident. In practice, this is a structured process with room to respond, not a single surprise visit followed by a fine.

What "Diligent" Looks Like

Whether ACN arrives with a document request or an inspection, it will look at evidence. The organisations in the strongest position are not necessarily those that have implemented everything, but those that can show what they did, when and on whose authority.

  • Governance. Minutes showing that the management body approved the security measures and oversees their implementation, as Article 23 of the decree requires, and records of the training its members followed.
  • Roles. The point of contact, the CSIRT contact person and deputies, with their designation dates.
  • Risk analysis and plan. A documented risk assessment and an implementation plan for each baseline measure, with status, owner and target date.
  • Accepted risk. Where a measure is not yet in place, a written risk acceptance with compensating controls and a deadline, signed by the right level of management.
  • Technical evidence. Asset inventories, vulnerability scans and their remediation, MFA coverage, backup and restore tests, logs of incident handling. Dated, repeatable and stored where you can find them.
  • Incident readiness. A procedure that meets the notification timelines (pre-notification to CSIRT Italia within 24 hours, notification within 72 hours, final report within one month) and evidence that it was tested.

If You Are Late: Prioritise and Document

Missing the deadline is a problem; hiding it is a bigger one. A credible recovery plan has three phases.

  1. First 30 days: take control. Retrieve your ACN notice and confirm your category and dates. Have the management body formally acknowledge the gap and approve a plan with a budget. Confirm the point of contact and the CSIRT contact person. Write the incident notification procedure and run a tabletop exercise on the 24 and 72-hour windows.
  2. Days 30 to 60: close the gaps attackers use first. Complete the inventory of hardware, software, services and suppliers. Enforce MFA for remote and administrative access, separate admin accounts and keep an offline backup. Scan your internet-facing perimeter and fix known exploited vulnerabilities first: in 2026 one exploited vulnerability in four concerned firewalls, VPNs and other edge devices, as our KEV analysis shows.
  3. Days 60 to 90: make it measurable. Test the effectiveness of what you implemented (penetration testing and repeat scans), document results and remediations, start the training programme for staff and management, and update the risk register. Report progress to the management body with dates.

Each step produces evidence. Keep it dated and organised by baseline measure, so that a document request can be answered in hours rather than weeks.

Penalties in Context

Article 38 of the decree sets maximum fines of 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, with separate amounts for public administrations and specific penalties for registration and categorisation failures. Read them alongside Article 37: the decree's path runs through findings, deadlines to fix and formal warnings before sanctions. Our article on NIS2 penalties covers the full regime, including management liability.

What Is Coming at EU Level

On 20 January 2026 the European Commission proposed a cybersecurity package with targeted amendments to NIS2 and a revised Cybersecurity Act. According to Freshfields' analysis, the NIS2 changes include a new "small mid-cap" category (fewer than 750 employees and turnover up to EUR 150 million or a balance sheet up to EUR 129 million), generally classed as important rather than essential entities; the possibility of more detailed ransomware reporting; a limit on national requirements added on top of EU implementing acts on technical measures; and national plans for post-quantum cryptography. The revised Cybersecurity Act introduces EU-level risk assessments of ICT supply chains that could lead to restrictions on high-risk suppliers. The package is with the European Parliament and the Council, with no adoption date yet. None of it changes your Italian obligations today.

Checklist for This Month

  • Find your ACN notice and confirm your deadline and category.
  • Bring the gap analysis to the management body and minute its decisions.
  • Confirm the point of contact and the CSIRT contact person, with deputies.
  • Test the incident notification procedure against the 24 and 72-hour windows.
  • Scan the external perimeter and fix known exploited vulnerabilities first.
  • Write risk acceptances for measures not yet in place, with deadlines.
  • Create an evidence folder per baseline measure, with dated documents.
  • Check the 2027 calendar: registration, supplier list and categorisation windows.

How Orizon Helps

Orizon does not certify compliance, and no tool can. What we provide is dated, repeatable technical evidence for the measures that can be tested. On our NIS2 page you will find how it fits together: RECON External positions you on the Article 21 measures an outside scan can evidence (met, gap or not assessable from outside), and proven vulnerabilities count towards vulnerability handling; the RECON Internal probe evaluates 25 controls mapped to Article 21(2), each pass, warn, fail or not assessed; RECON Cloud maps cloud and SaaS findings to the ten Article 21(2) measures. Fireline's compliance edition cross-references confirmed penetration test findings to NIS2 Article 21(2), with a chapter on Italy's ACN baseline measures, and never claims compliance on your behalf. Aware documents the training records that Articles 20(2) and 21(2)(g) of the directive call for. For keeping that evidence organised over time, see compliance automation.

nis2
acn
italy
inspections
baseline-measures
compliance