Back to Articles

NIS2

Italy's NIS2: the 13 April 2026 ACN determinations on relevant suppliers, categorisation and new-entity deadlines

12 min read

On 13 April 2026 ACN adopted determinations 127434/2026 and 127437/2026. Who counts as a relevant NIS supplier, what data to submit, how the yearly categorisation of activities and services works, the deadlines for entities listed in 2026, and what suppliers should expect.

nis2
acn

On 13 April 2026 Bruno Frattasi, Director General of ACN, Italy's National Cybersecurity Agency, signed two determinations that changed the day-to-day work of every NIS entity in Italy and of many of their suppliers: Determinazione 127434/2026 and Determinazione 127437/2026. The first sets the deadlines for entities added to the NIS list during 2026. The second introduces two new yearly duties: listing your "relevant NIS suppliers" and categorising your activities and services. Seven months later the first windows have closed, but the obligations are permanent and the next deadline, the designation of a CSIRT contact for 2026 entities, falls on 31 December 2026. This article explains what the determinations require, who counts as a relevant supplier, and how to prepare for the 2027 cycle. For the general framework, start from our complete NIS2 guide.

Key takeaways

  • Entities first listed in 2026: Referente CSIRT by 31 December 2026, significant-incident notification from 1 January 2027, baseline security measures by 31 July 2027
  • Entities listed in 2025 keep their existing deadlines, counted from their own inclusion notice
  • Every NIS entity must list its relevant suppliers as part of the yearly information update on the ACN portal
  • A supplier is relevant if it provides ICT services of the digital infrastructure or ICT management type, or if it cannot easily be replaced
  • Activities and services must be categorised every year between 1 May and 30 June; after that the list is final

What changed on 13 April 2026

Italy transposed NIS2 with Legislative Decree 138/2024 (the "decreto NIS"). Its first application phase, under Article 42, ended on 31 December 2025, and the baseline security measures and incident notification rules were set by ACN Determinazione 379907 of 19 December 2025. The April determinations, adopted after the NIS Implementation Table met on 9 April 2026, build on that framework:

  • Determinazione 127434/2026 sets the deadlines for entities included in the NIS list for the first time during calendar year 2026. It applies from 30 April 2026. We have read the signed text.
  • Determinazione 127437/2026 updates and replaces the earlier determination on how NIS entities use the ACN digital platform, and adds the relevant-supplier list (Article 18), the categorisation of activities and services (Articles 20 and 21) and rules on the CSIRT contact (Article 7). Our summary of this determination follows the analyses published by CMS and Agenda Digitale; check the official text on the ACN website before acting on a detail.

Who counts as a relevant NIS supplier

A supplier that provides products or services to a NIS entity is a "fornitore rilevante NIS" if it meets at least one of two criteria:

  1. ICT supply. The supply relates to the activities or services in Annex I, points 8 and 9, of the decreto NIS: digital infrastructure (such as DNS, cloud computing, data centres and content delivery networks) and B2B ICT service management (managed service providers and managed security service providers).
  2. Non-substitutable supply. Its interruption or compromise would significantly affect the entity's ability to deliver its activities or services, including because there is no adequate alternative supplier.

The second criterion goes beyond IT. A single supplier of a critical component, a logistics provider without a practical alternative or a specialised maintenance contractor can all qualify. The purpose, according to the summaries, is to help ACN identify suppliers that could themselves qualify as essential or important entities and to strengthen security along the supply chain.

The data required for each supplier

For each relevant supplier the NIS entity submits:

FieldWhat it means in practice
Name (denominazione)The legal name of the supplier, as in the contract
Tax code (codice fiscale)The supplier's Italian tax code, or the foreign equivalent
Country of registered officeWhere the supplier is legally established, not where it delivers
CPV codesThe Common Procurement Vocabulary codes (Regulation (EC) 2195/2002) of the supplies received
Relevance criterionICT supply, non-substitutable supply, or both

The list is submitted through the "Servizio NIS/Aggiornamento annuale informazioni" on the ACN portal, as part of the yearly information update, which according to CMS ran from 15 April to 31 May 2026. Plan for the same window in 2027.

Where to find CPV codes

CPV codes are the classification used across the EU for public procurement. Public bodies will already have them in their tenders. Private companies usually do not, and will need to map each supply to the vocabulary. For ICT, most supplies fall in two divisions: 48 (software packages and information systems) and 72 (IT services: consulting, software development, internet and support). Start from your purchase ledger and contracts, not from memory: the supplier you forget is often the one with remote access.

Categorisation of activities and services

The second new duty, based on Article 30 of the decreto NIS, asks each entity to list its activities and services and assign each one a relevance category, using a model set by a separate ACN determination. ACN announced support material for a simplified business impact analysis.

  • Window: from 1 May to 30 June of each year, through the "Servizio NIS/Categorizzazione" on the ACN portal.
  • Confirmation: the NIS point of contact confirms the information as a formal declaration and transmits it; ACN sends a copy to the entity's certified digital address.
  • Finality: after the deadline the categorised list is final and cannot be changed. Late submissions are accepted as late, except for documented technical problems not attributable to the entity.
  • Checks: ACN may check lists on a sample basis and compare them with similar entities. It responds within 90 days, extendable once by 60; requests for information must be answered within 30 days. Without a negative outcome in time, the list is considered validated.

Categorisation matters because it drives proportionality: which activities are most relevant determines where the security measures and the incident notification rules bite hardest. Do not delegate it entirely to IT. It needs the people who know which services the business cannot live without.

Deadlines for entities added to the list in 2026

ObligationEntities first listed in 2026Entities listed in 2025 and still listed
Designate the Referente CSIRTBy 31 December 2026Already due
Notify significant incidentsFrom 1 January 20279 months from the inclusion notice, unchanged
Adopt the baseline security measuresBy 31 July 202718 months from the inclusion notice, unchanged

Two details are easy to miss. The CSIRT contact rule in Determinazione 127437/2026 is permanent: any entity designates it by 31 December of the year in which it is listed. And if the CSIRT contact and their deputies are unavailable, the NIS point of contact may exceptionally submit incident notifications on the entity's behalf. Financial entities under DORA are exempt from designating the CSIRT contact and from categorisation, though they may comply voluntarily.

If you registered late, the yearly update must be completed within 30 days of receiving the inclusion notice, without prejudice to the penalties of Article 38 of the decreto NIS. Our article on NIS2 penalties covers the amounts.

Calendar for the next twelve months

  • 31 December 2026: Referente CSIRT designated by entities first listed in 2026.
  • 1 January 2027: those entities start notifying significant incidents.
  • 15 April to 31 May 2027: yearly information update, including the relevant-supplier list.
  • 1 May to 30 June 2027: categorisation of activities and services.
  • 31 July 2027: baseline security measures in place for entities first listed in 2026.

What suppliers should expect

If you sell ICT services to a NIS entity, or you are hard to replace, you are probably on someone's list already. That has practical consequences:

  • More questionnaires, and increasingly requests for evidence rather than self-declarations: test reports, certifications, incident procedures, the name of a security contact.
  • New contract clauses on incident notification to the customer, right to audit, subcontractors and security requirements aligned with Article 21 of NIS2.
  • Visibility to ACN. Being named by several NIS entities is exactly the signal the list is designed to give. If your company could fall within the scope of NIS2 itself, check it now; our NIS2 guide for SMEs helps.

The best position for a supplier is to have the evidence ready before it is asked for. For the customer side of the same relationship, see our article on NIS2 supply chain security.

A practical checklist

  1. Extract every supplier from your purchase ledger and contracts of the last two years.
  2. Mark which ones provide digital infrastructure or managed ICT services, and which ones you could not replace quickly.
  3. For each relevant supplier, collect name, tax code, country of registered office and CPV codes, and keep the file updated during the year.
  4. Involve operations and finance in the categorisation, not only IT, and prepare it before 1 May.
  5. If you were listed in 2026, designate the Referente CSIRT and at least one deputy before 31 December.
  6. Prepare the incident notification procedure for 1 January 2027 and test it with an exercise.
  7. Plan the baseline measures backwards from 31 July 2027, starting from the technical ones that take longest.
  8. Ask your critical suppliers for dated technical evidence, and prepare your own for your customers.

How Orizon helps

The determinations ask for lists; Article 21 of NIS2 asks for measures that work. Orizon helps with the evidence side, not with the declaration. Fireline, our autonomous external penetration test on the perimeter you authorise, has a compliance edition that cross-references each confirmed finding to NIS2 Article 21(2)(a) to (j); Italian reports add a chapter on the ACN baseline measures that an external test can observe and the TC-ACN pre-classification. It never claims compliance: a requirement is flagged only when a confirmed finding stands behind it. Inside the network, RECON Internal evaluates 25 technical controls related to Article 21, such as segmentation, SMB signing, end-of-life systems and centralised logging, and marks each one Pass, Warn, Fail or Not assessed with the affected assets. For suppliers, a dated report is a concrete answer to a customer's questionnaire. See how it fits together on our NIS2 compliance page.

nis2
acn
italy
supply-chain
relevant-suppliers
compliance