Join our Newsletter — 33% off our NHI Course
Home› Guides› Italy NIS2 Implementation Guide: Legislative Decree 138/2024 (NIS2)…
Guide Regulations & Frameworks

Italy NIS2 Implementation Guide: Legislative Decree 138/2024 (NIS2) and ACN registration

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Italy transposed NIS2 on time, and by October 2026 its regime has moved from registration into enforceable security measures, with the Agenzia per la cybersicurezza nazionale (ACN) able to start verifying them. Decreto legislativo 4 settembre 2024, n. 138 sets an annual registration cycle on the ACN portal, a staged set of deadlines counted from each entity's inclusion notice, and binding "basic measures" defined by ACN determinations. This guide explains the Italian scope rules, the registration calendar, the measures and incident notification regime, sanctions and the practical steps for identity and security teams. It is for CISOs, compliance officers and the designated punto di contatto in organisations with Italian entities. The directive itself is covered in the NIS2 Directive Guide; this page covers the Italian layer.

Status checked 27 October 2026: D.Lgs. 138/2024 was published in the Gazzetta Ufficiale (Serie Generale n. 230) on 1 October 2024 and has been in force since 16 October 2024. ACN Determination 379907/2025 (December 2025; sources differ on whether it is dated 18 or 19 December) is the reference for basic measures and significant incidents, and ACN updated it in 2026 through Determination 127434/2026, as summarised by law firm commentary. The publication and in-force dates, the Article 7 registration windows and ACN's Article 10 role were checked against the Gazzetta Ufficiale text. Check Normattiva for the consolidated text before relying on any article, because implementing determinations are updated regularly.

Key takeaways

  • Registration is annual: every entity in scope registers or updates its record on the ACN digital platform from 1 January to 28 February each year, and changes must be reported within 14 days.
  • Deadlines run from the inclusion notice: ACN began notifying listed entities from 12 April 2025 (as reported in Italian trade press), with, according to the same reports, 9 months to start notifying incidents and 18 months to implement the basic measures (October 2026 for most entities).
  • The basic measures are binding detail: Determination 379907/2025 is reported to have separate annexes for important and essential entities, so classification decides how many requirements you must evidence.
  • Management carries the duty: as reported in Italian trade press summaries of the decree, governing bodies must approve and oversee the measures, follow training, and can be held responsible, with temporary bans on managerial functions possible.
  • Machine identities are part of the evidence: access control, logging and supply chain measures apply to service accounts, API keys and AI agents as much as to staff accounts.

Scope: who and what is covered

Article 3 of the decree applies the directive's size-cap rule: entities of the types in Annexes I and II are covered when they exceed the small-enterprise ceilings of Commission Recommendation 2003/361/EC. Some are covered regardless of size, including identified critical entities, electronic communications providers, trust service providers, top-level domain registries, DNS service providers and domain name registrars. Italy also uses Annex III (public administrations) and Annex IV (further entity types it chose to add), so the Italian scope is wider than the directive's two annexes alone.

AnnexWhat it coversPractical note
Annex ISectors of high criticality: energy, transport, banking, financial market infrastructure, health, drinking water, waste water, digital infrastructure, ICT service management (B2B), public administration, spaceMedium or large entities here are usually essential if they are large
Annex IIOther critical sectors: postal and courier, waste management, chemicals, food, manufacturing, digital providers, researchMedium and large entities are usually important
Annex IIIPublic administrations named by the decreeCovered regardless of size
Annex IVAdditional categories chosen nationallyCheck carefully: entities outside the directive annexes may still be in scope
  • Classification: the essential or important label determines which annex of the ACN basic measures applies and which incident categories you notify.
  • Group structures: each Italian legal entity registers in its own right; size is calculated with linked and partner enterprises under Recommendation 2003/361/EC.
  • Financial entities: where DORA applies, sector rules prevail on overlapping obligations. See the DORA and NIS2 Overlap Mapping Guide.

Key obligations

Registration on the ACN platform (Article 7)

WindowWhat happens
1 January to 28 February each yearEntities register or update: legal name, address and up-to-date contact details, designated punto di contatto, sectors and entity types from Annexes I to IV
By 31 MarchACN draws up the list of essential and important entities and notifies inclusion
15 April to 31 MayEntities that remain on the list provide further information
Within 14 days of any changeReport changes to the registered information

The punto di contatto is the named person who handles the relationship with ACN. Choose someone with authority to act and keep a deputy, because the role holds credentials to the portal: treat that account as privileged, with MFA and a documented handover.

Governance (Article 23)

As summarised in Italian trade press (the consolidated article text could not be verified at the time of writing):

  • Approval and oversight: the management and governing bodies approve the cybersecurity risk-management measures and oversee their implementation.
  • Training: members of those bodies must receive specific training, and should promote training for staff.
  • Responsibility: the bodies are responsible for violations of the decree's obligations.

Security measures (Article 24) and the ACN basic measures

Article 24 transposes directive Article 21: appropriate and proportionate technical, operational and organisational measures on an all-hazards basis. ACN turns this into binding detail through determinations. According to Italian trade press, Determination 379907/2025 (December 2025) replaced Determination 164179 of 14 April 2025 and contains four annexes.

Annex of Det. 379907/2025Applies toContent (as reported)
Allegato 1Important entitiesBasic security measures: 37 measures, 87 requirements
Allegato 2Essential entitiesBasic security measures: 43 measures, 116 requirements
Allegato 3Important entitiesSignificant incident categories IS-1 to IS-3
Allegato 4Essential entitiesSignificant incident categories IS-1 to IS-4

ACN is also reported to have published non-binding guidance: guidelines on the incident management process (31 December 2025) and a reading guide to the basic specifications (version 2.0, December 2025). Measure and requirement counts above come from trade press summaries of the determination; check the annex text on the ACN site for the authoritative list.

Incident notification (Article 25)

The stages below follow trade press summaries of Article 25, which mirror directive Article 23; check the consolidated text on Normattiva.

StageDeadlineContent
Pre-notification (pre-allarme)Within 24 hours of becoming aware of a significant incidentEarly warning that a significant incident has occurred
NotificationWithin 72 hoursInitial assessment of severity and impact
Final reportWithin one month of the notificationRoot cause, mitigation measures applied, cross-border impact

Notifications are made to ACN through its portal channels, following the ACN incident guidelines. Personal data breaches also go to the Garante per la protezione dei dati personali under GDPR Article 33. See the Cyber Incident Reporting Requirements Map.

Timeline and current status

DateMilestone
4 September 2024D.Lgs. 138/2024 adopted
1 October 2024Published in GU Serie Generale n. 230
16 October 2024Entry into force
By 28 February 2025First registration on the ACN portal
12 April 2025ACN begins sending inclusion notices
14 April 2025Determination 164179 on basic measures (later repealed)
December 2025Determination 379907/2025 replaces 164179
1 January to 28 February 2026Second annual registration and update window
January 2026 (15 January as reported)Incident notification obligation operational for most listed entities (9 months from notice)
October 2026 (31 October as reported)Basic security measures due for most listed entities (18 months from notice); ACN verification can follow
1 January to 28 February 2027Next annual registration window

Entities first notified later than April 2025 have deadlines counted from their own notice. For entities first listed in 2026, law firm summaries of Determination 127434/2026 report incident notification from 1 January 2027 and security measures by 31 July 2027; confirm this on the ACN site. Keep the notice and calculate your dates from it rather than from the national headline dates. Track other Member States in the NIS2 Transposition Tracker.

Enforcement and penalties

ACN is the national competent authority and single point of contact (Article 10). It can carry out inspections and audits, issue warnings and binding instructions, and impose administrative fines.

MeasureEssential entitiesImportant entities
Maximum administrative fine (as reported in Italian trade press)Up to EUR 10 million or 2% of total worldwide annual turnover of the previous year, whichever is higher (public administrations follow a separate regime)Up to EUR 7 million or 1.4% of total worldwide annual turnover, whichever is higher
Personal responsibility of managersArticle 38, comma 5 is reported to provide for responsibility of the natural persons in charge
Temporary bar on managerial functionsArticle 38, comma 6 is reported to allow a temporary bar where non-compliance continues after ACN warnings

The decree also sets minimum amounts and lighter sanctions for procedural failures such as late registration. Read Article 38 on Normattiva for the exact ranges, which this guide does not reproduce because the consolidated article text could not be verified at the time of writing.

What it means for AI agents and non-human identities

The Italian basic measures are written around assets, access, logging and incidents, not around people. Every service account, API key, certificate and AI agent that can touch a network or information system in scope is part of what an ACN inspector can ask about. The Snowflake breach showed what happens when stolen credentials without MFA, rotation or network allow lists reach a data platform: around 165 customer environments were accessed (see the Snowflake breach).

Measure areaNHI and agent controlEvidence to keep
Asset inventoryRegister every machine identity and agent with owner, purpose and systemInventory export with owner and last review date
Access controlLeast privilege, no shared accounts, removal of unused credentialsAccess review records covering service accounts
AuthenticationMFA for humans, workload identity or short-lived tokens for machines, vaulted secretsVault coverage report, list of remaining static keys with exceptions
Logging and monitoringLog machine authentication and agent actions centrallyLog sources list and retention settings
Supply chainReview third-party OAuth grants, API keys issued to suppliersSupplier access register
Incident handlingRunbook to revoke and rotate machine credentials fastExercise record with revocation times
  • Agents need their own identity: do not let an AI agent run on a human's session or a shared key. See the Agent Identity and Access Guide.
  • Inventory feeds registration: Annex IV categories and further information requests are easier to answer when assets and identities are already mapped. Use the Service Account Inventory Template.

Compliance steps

  1. Confirm status and dates: retrieve every Italian entity's inclusion notice, record the classification and calculate the 9-month and 18-month dates from it.
  2. Put the registration calendar in the compliance plan: 1 January to 28 February update, 15 April to 31 May further information, 14-day change reporting.
  3. Appoint and protect the punto di contatto: named person, deputy, MFA on the portal account, handover procedure.
  4. Brief and train the governing body: minute approval of the measures and record training attendance.
  5. Gap-assess against the right annex: Allegato 1 or 2 of Determination 379907/2025, with evidence per requirement. Existing ISO/IEC 27001 controls help.
  6. Operationalise notification: map IS-1 to IS-4 categories to your incident severity scale, and rehearse the 24-hour and 72-hour steps.
  7. Close machine identity gaps: inventory, owners, vaulting, rotation, removal of dormant credentials.
  8. Prepare for verification: organise evidence so an ACN inspection can be answered per requirement, not per policy document.

Small versus large organisations

  • Medium-sized important entities: concentrate on Allegato 1. Use one evidence repository, a managed identity provider with MFA, and a vault for the handful of service credentials that reach production. Outsourced IT providers often hold the most powerful credentials, so put their access in writing.
  • Large essential entities: Allegato 2 adds requirements and the IS-4 incident category. Expect a formal verification, so appoint control owners per requirement, automate evidence collection where you can, and run the NHI inventory as a continuous process rather than a yearly spreadsheet.
  • Groups with several Italian entities: one central programme can serve them all, but each entity keeps its own registration, classification, deadlines and punto di contatto.

Framework mapping

Italian obligationNIST CSF 2.0NIST SP 800-53 r5ISO/IEC 27001:2022 Annex A
Governing body approval and training (Art. 23)GV.RR-01, GV.OV-01PM-2, AT-2A.5.1, A.6.3
Access and identity measures (Art. 24)PR.AA-01, PR.AA-05AC-2, AC-6, IA-4, IA-5A.5.15 to A.5.18, A.8.2
Supply chain measures (Art. 24)GV.SC-01SR-3A.5.19 to A.5.21
Logging and detection (Art. 24)DE.CM-01, PR.PS-04AU-2, AU-6A.8.15, A.8.16
Incident notification (Art. 25)RS.CO-02IR-6A.5.24, A.5.26

Detection and measurement

  • Requirement coverage: percentage of the applicable annex's requirements with current evidence.
  • Registration accuracy: days since the portal record was last checked against reality, and changes reported within 14 days.
  • NHI ownership: share of machine identities and agents with a named owner and review in the last 12 months.
  • Notification readiness: time from detection to draft pre-notification in exercises, against 24 hours.
  • Credential revocation time: median time to revoke and replace a compromised machine credential.

Common failure patterns

  • Treating registration as one-off: missing the annual window or the 14-day change rule after a merger or new service.
  • Using national headline dates: an entity notified later has later deadlines, and one notified earlier may already be late.
  • Policy without evidence: the basic measures are requirement-level; a policy document alone will not satisfy an inspector.
  • Service accounts outside reviews: certifying human access while integration keys with wider rights are never reviewed.
  • Unprotected portal access: the punto di contatto's credentials shared by email or without MFA.

Practitioner checklist

  • File each entity's ACN inclusion notice and record its computed deadlines.
  • Add the annual registration and further-information windows to the compliance calendar.
  • Name a punto di contatto and deputy, with MFA on the portal account.
  • Minute governing body approval of measures and record training.
  • Map evidence to every requirement in the applicable annex of Determination 379907/2025.
  • Align incident severity with IS-1 to IS-4 and rehearse 24-hour and 72-hour notifications.
  • Inventory all non-human identities and AI agents with owner, scope and rotation date.
  • Read Article 38 on Normattiva and brief management on fines and personal responsibility.

Standards and references

Related NHI Mgmt Group resources: NIS2 Directive Guide · NIS2 Readiness Checklist · NIS2 Transposition Tracker · Non-Human Identity (NHI) Guide. This guide summarises Italy's NIS2 implementation under D.Lgs. 138/2024 as it stood on 27 October 2026 and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.