NIS2: what the customer asks of its suppliers, and how to answer
For the supplier, often an SME, that receives a security questionnaire or a contract clause from a customer subject to NIS2: whether the law applies to it too, from when the requests arrive, what they contain, what is mandatory and what can be discussed, and how to answer once for every customer.
If my customer is subject to NIS2, does that make me subject too?
Not for that reason. NIS2, transposed in Italy by Legislative Decree 138/2024, applies to organisations in the sectors listed in its annexes that exceed the small-enterprise thresholds, plus a few cases where size does not matter (article 3). Working for a NIS2 entity is not one of those cases. The National Cybersecurity Agency (ACN), the Italian authority that enforces the decree, says so in its frequently asked questions on scope: there is «no mechanism of direct propagation» of the scope from NIS entities to their supply chain. Suppliers «will have to meet contractual obligations», but they do not become NIS entities and the ACN does not supervise them. The quotations from Italian texts in this guide are our translations.
The threshold is the one in Recommendation 2003/361/EC, which the decree refers to: a small enterprise employs fewer than 50 people and has an annual turnover or balance sheet total of no more than 10 million euros. An SME that stays below it is out, even in a listed sector, except in the cases in the table.
| You are subject too if | Where it says so | For example |
|---|---|---|
| your sector is in annex I or II and you exceed the small-enterprise thresholds | article 3, paragraph 2 | a 120-person manufacturer in an annex II sector |
| you provide public electronic communications, trust services, DNS or domains | article 3, paragraph 5 | a small telecoms operator, at any size |
| you are linked to the entity and provide it with IT or security services | article 3, paragraph 10 | a group's IT company, even a small one |
| the ACN identifies you as a systemic element of the supply chain | article 3, paragraphs 9 and 13 | a supplier with no alternative for many entities |
Among entities, those in annex I above the medium-enterprise thresholds (at least 250 people, or more than 50 million in turnover and more than 43 million in balance sheet) are essential, the others important (article 6). The difference matters to you as well, because it changes what the customer must ask of you, as shown further on.
The provisional 2026 list counts «over 21,000» NIS entities, «of which at least 5,000 essential», according to an ACN press release of 9 April 2026. Each one has its suppliers, and each one must take care of their security: that is why the requests reach companies that have never read NIS2. The useful question is not whether you are subject, but what the contract will ask you to prove, and whether you could prove it today.
What must the customer ask, and from when?
The customer must put security requirements into contracts that are proportionate to the risk of your supply, and then check that you meet them. The obligation comes from article 24, which lists «supply chain security» among the security measures and requires entities to take into account «the overall quality of the products and cybersecurity practices» of their suppliers, «including their secure development procedures». It transposes article 21 of Directive (EU) 2022/2555, whose recital 85 encourages entities to bring these measures into their agreements with direct suppliers.
How to do it is set by the ACN in determination 379907 of 19 December 2025, applicable from 15 January 2026: 37 measures with 87 requirements for important entities (annex 1), 43 measures with 116 requirements for essential ones (annex 2), according to the ACN reading guide. Five measures, coded GV.SC, concern suppliers, and the ACN frequently asked questions on the measures (FAQ MSB.13) line them up in four steps: the customer assesses the risk of the supply, derives the security requirements from it, puts them into requests for offers and contracts, then checks compliance periodically and documents it. The last step is what brings the questionnaire back: filling it in once is not enough.
Not every supply gets requirements, only those «with potential impacts on the security of network and information systems»; the ACN states that they need not be defined for all of them (FAQ MSB.15). Whoever delivers stationery does not get the questionnaire sent to whoever maintains the business software. The risk is assessed on at least five criteria, set by measure GV.SC-07:
| What the customer assesses | The risk rises, for example, when |
|---|---|
| your access to its systems | you connect remotely, with administrator accounts |
| your access to data and intellectual property | you handle personal data, drawings or source code |
| the impact of a serious interruption on your side | without you a customer service stops |
| recovery time and cost | replacing you would take months |
| your role in governing its systems | you run or maintain its systems |
From when do the requests arrive?
Running contracts do not have to be amended. According to ACN FAQ MSB.12 «it is not mandatory to amend supply contracts already in place», and the requirements are mandatory «for contracts signed, renewed or extended from the deadline for adopting the security measures». That deadline depends on when the customer entered the list of NIS entities.
| Customer | Deadline for the measures | Contracts with requirements |
|---|---|---|
| on the list since 2025 | 18 months from the ACN notice, «October 2026» | signed, renewed or extended after the deadline |
| on the list for the first time in 2026 | 31 July 2027 | from 31 July 2027, our reading |
The ACN sent its notices to the 2025 entities «starting from 12 April 2025», says the reading guide, and on its basic specifications page it sums up the deadline as «October 2026»; for each entity the exact date depends on the day it received the notice. For 2026 entities the deadline comes from determination 127434 of 2026; that contracts follow the same date is our reading, because the FAQ speaks only of 2025 entities. As of 16 November 2026, then, a customer listed in 2025 must already put the requirements into every new or renewed contract, and nothing stops the others from asking earlier.
Incidents run on a different calendar. The customer must send CSIRT Italia, the ACN incident response team, an early warning within 24 hours of becoming aware of a significant incident and a notification within 72 hours (article 25). Notifying is not your job: according to FAQ ISB.F.1 the obligation «lies with the NIS customer», which must however make sure that the supplier «promptly reports» security events affecting its services. Incident notification applies from «January 2026» for 2025 entities and from 1 January 2027 for 2026 entities.
Why does the customer ask for your tax code and CPV codes?
Because it has to list you with the ACN. From 15 April to 31 May every year, the NIS entity lists its «relevant suppliers» on the ACN platform, with name, tax code, country of the registered office, the CPV codes of the supply (the Common Procurement Vocabulary of European public procurement) and the relevance criterion (determination 314287 of 2026, in force from 25 October 2026). There are two criteria: the supply is an IT supply of the kind listed in points 8 and 9 of annex I of the decree, or it is not fungible, meaning its interruption would have a significant impact on the customer, also because there are no alternative suppliers.
The ACN uses the list to recognise the systemic elements of the supply chain (FAQ FRN.1), which can become entities even when small. Our reading: a supplier that appears on the lists of many entities is the first one the ACN will look at.
Would you rather talk it through?
Book a call with people who work on these topics every day: we will look at your case together.
What is in the questionnaire?
Each customer writes its own, because there is no official questionnaire. As of 16 November 2026 neither the ACN nor the European Commission publishes one: the EU toolbox on ICT supply chain security, adopted on 13 February 2026, is a non-binding framework, and the ENISA technical guidance, from the EU cybersecurity agency, mentions supplier questionnaires only as examples of evidence. The questions, though, nearly always come from the same areas: the 17 that ACN annex 2, in measure GV.SC-01, asks essential entities to consider «where applicable» in their supplier requirements. For an important customer they are not mandatory, but they remain the most likely outline (our reading).
| Areas of measure GV.SC-01 | What they ask you | What you prepare |
|---|---|---|
| supplier reliability | security practices, continuity of supply and support | company profile, contacts, support commitments |
| roles, people, training | who does what in the supply, reliability and training | roles in the supply, training records |
| compliance and audit | written policies, certifications, checks | policies, certificates if any, latest check |
| identity, access, monitoring | multi-factor authentication, named accounts, logs | list of accounts, remote access, logs |
| data, networks, physical security | where data lives, how it is protected, who gets in | data map, encryption, site access control |
| incidents and continuity | reporting to the customer, backups, recovery | procedure with times and contacts, recovery tests |
| development, maintenance, vulnerabilities | secure development, updates, fixes | development process, time to fix |
| end of supply and subcontracting | return and deletion of data, subcontractors | exit procedure, list of subcontractors |
The 17 items, grouped here into eight rows, are these: supplier reliability; roles and responsibilities; reliability of human resources; compliance and security audit; vulnerability management; business continuity and disaster recovery; authentication, digital identities and access control; physical security; staff training and awareness; data security; network and communications protection; monitoring of security events, including access and activities performed; incident management and reporting; secure code development and security by design and by default; maintenance, including security updates; end of supply, with return and deletion of data; subcontracting and requirements along the supply chain.
Two more measures affect whoever works remotely on the customer's systems. Every account, including those used for remote access, must be «registered, approved by people inside the NIS entity» (measure PR.AA-01), and every remote access is logged (PR.PS-04). If you provide support over VPN or with a remote control tool, expect named accounts instead of the shared one, and a list of the people using them. We already work this way: the accounts are created by the client: we do not create our own users on your environments, we ask to be authorized on the existing ones or to be added to your team (as we explain in who accesses your systems).
Clauses: what is mandatory and what can be negotiated?
For the customer it is mandatory to put into the contract the security requirements derived from the risk assessment, «save for justified and documented regulatory or technical reasons» (measure GV.SC-05). It is not mandatory to copy them word for word, nor to include all of them: according to FAQ MSB.16 it is enough that the contract takes on «their substantial content». Everything else, from penalties to certification, is the customer's choice, and like any choice it can be discussed. For public administrations the ACN adds that requirements must be consistent with the subject of the contract and with the «actual risk profile» (FAQ MSB.17), avoiding «the generalised imposition of obligations not consistent» with the supply (MSB.19).
| Clause | Where it comes from | Our reading |
|---|---|---|
| security requirements consistent with the customer's measures | measures GV.SC-01 and GV.SC-05, the customer's duty | they stay; discuss how to prove them |
| incident reporting to the customer | FAQ ISB.F.1, the customer must secure it | agree the deadline, channel and what to report |
| right to audit or to audit reports | measure GV.SC-07, periodic documented checks | offer periodic evidence and audits with notice |
| ISO 27001 certification | no ACN measure imposes it on the supplier | equivalent evidence, or a path with a date |
| return and deletion of data | area of measure GV.SC-01, essential entities | agree formats, timing and a statement |
| list and duties of subcontractors | area of measure GV.SC-01, essential entities | disclose it, and pass the requirements down |
| penalties and uncapped liability | no NIS rule | negotiated like any other clause |
The decree sets no deadline for the supplier's report: the contract does. Our reading: it must leave the customer time to meet its own 24 hours, so expect a few hours, and ask that the clause state precisely which events to report, to whom and through which channel, because «any security event» cannot be complied with.
The customer insists for a reason: fines for an essential entity reach 10 million euros or 2% of worldwide annual turnover, whichever is higher, and for an important one 7 million or 1.4% (article 38); management bodies approve the measures and are liable for breaches (article 23). A clause the customer cannot show it requested and checked is its problem; a signed clause you cannot meet becomes yours. Sign what you can prove with a document, and for the rest propose a date. This section sets out the rules and our reading, it is not legal advice: a lawyer should review the wording of your contract.
What changes if you supply software or IT services?
The questions get more technical, and some come straight from the law. Article 24 names the secure development procedures of suppliers, and among the customer's measures it lists the security of acquiring, developing and maintaining network and information systems, including vulnerability handling and disclosure. From whoever develops or maintains software, the customer asks how code is written and tested, which third-party components are used, how fast a vulnerability is fixed, how updates are rolled out, who accesses production environments and how data and code are returned at the end of the contract. An essential customer also monitors the channels of the suppliers of software it deems critical (measure ID.RA-08).
Three cases change more. If yours is an IT company in the same group as the customer, you are subject too, at any size (article 3, paragraph 10). If you provide cloud, data centre or managed IT services, you are in the annex I sectors and, above the thresholds, subject in your own right; for these services Implementing Regulation (EU) 2024/2690 also details the contracts with their own suppliers, with eight elements to specify where appropriate, including incident notification without undue delay, the right to audit, vulnerability handling, subcontracting and the recovery and disposal of information at the end of the contract. If you sell a SaaS to large companies, questionnaires, certifications, data processing agreement and contracts are in the guide Selling SaaS to enterprises.
For the software we develop, the answers to these questions are in the Trust Center. How do we protect data? With security designed in from the start: role-based access, least privilege and isolated services. Authentication integrates with the company identity provider, with a second factor (how we handle authentication); backups come with documented recovery procedures (backup, RTO and RPO); third-party components are declared with their licence (components that do not become yours). We are not ISO 27001 certified, and we say so (certifications): if your customer's purchasing process requires a formal certification, it is better to know at the first call.
How do you prepare the answers once for every customer?
With a single file, organised on the areas in the table, that you update once and draw the answers from for each customer. Questionnaires differ in form and resemble each other in substance, because they come from the same measures.
Before answering, ask the customer three things: whether it is an essential or an important entity, because that decides whether the 17 areas are mandatory; what risk it assigned to your supply; and which supply the answers are for, if you have more than one. A long questionnaire on a low-risk supply can be scaled down with FAQ MSB.15 in hand, which rules out requirements for supplies with no security impact.
Then write each answer once, area by area, with its evidence: a document, a log, a screenshot, with a date and an owner. Separate what you already do from what you will do: «in progress, completed by March» holds up better than a yes that falls at the first check. Keep track of what you declared to each customer and in which version, because they will ask you again at renewal, and review the file whenever something that affects it changes: a new subcontractor, a new system, an incident. An answer is worth the evidence that comes with it: a yes without a document is a promise. The same method works for sustainability questionnaires, in the guide The ESG data large customers ask of their suppliers.
The reverse problem belongs to the customer, which sends the questionnaire to dozens or hundreds of suppliers and must collect answers, documents and review dates. For the customer it is a software problem. Every piece of evidence is tied to the control and the period it refers to at the moment it is produced, with a trace of who uploads it and who approves it, and recurring audits are planned (software for audit and compliance). In an auditing platform we built, an AI agent replaced manual interviews: it knows the questions, the valid answers and the history of past submissions, so data arrives already structured (the case study). A custom register of risks and controls is on the risk management software page; when the customer wants a space where each supplier uploads its documents, the right guide is the one on the portal for suppliers, subcontractors and partners.
An example: the 40-person panel builder and the multi-utility
A 40-person company builds electrical panels, has a turnover of 8 million euros and supplies a multi-utility, an essential entity on the list since 2025. It is not subject to NIS2: it has fewer than 50 people and stays under 10 million. The details are invented, to be replaced with yours.
When the framework contract is renewed, at the end of 2026, the multi-utility sends a questionnaire and a security annex. The company asks what risk was assigned to the supply, and finds that the panels are not what weighs: it is the remote control module connected to the customer's network and the remote support its technicians provide over VPN on the programmable controllers. That is where the questions concentrate.
The file it prepares answers area by area: the named list of technicians with access, each with an account on the customer's VPN and a second factor; a procedure stating who notifies the customer, through which channel and within how many hours, for an event affecting its systems; how and how often it updates the modules' firmware; the list of subcontractors for the remote control module; what it returns and what it deletes at the end of the contract.
On the clauses, it accepts the security requirements, which the customer cannot drop. Instead of the ISO 27001 requested «within six months» it offers the file with the evidence and a yearly check with notice, and asks for a cap on penalties. When a second customer's questionnaire arrives, the file answers almost all of it.
Sources and further reading
- Italian Legislative Decree of 4 September 2024, no. 138 (NIS2), text in force, articles 3, 6, 7, 23, 24, 25 and 38normattiva.it, in Italian, accessed 16 November 2026
- Directive (EU) 2022/2555 (NIS 2), article 21 and recital 85eur-lex.europa.eu, accessed 16 November 2026
- Commission Recommendation 2003/361/EC concerning the definition of micro, small and medium-sized enterpriseseur-lex.europa.eu, accessed 16 November 2026
- ACN, determination no. 379907 of 19 December 2025, basic obligations of NIS entitiesacn.gov.it, in Italian, accessed 16 November 2026
- ACN, annex 1, basic security measures for important entitiesacn.gov.it, in Italian, accessed 16 November 2026
- ACN, annex 2, basic security measures for essential entitiesacn.gov.it, in Italian, accessed 16 November 2026
- ACN, NIS guidelines, basic specifications, reading guide, version 2.1, April 2026acn.gov.it, in Italian, accessed 16 November 2026
- ACN, basic procedures and specificationsacn.gov.it, in Italian, accessed 16 November 2026
- ACN, determination no. 127434 of 2026, deadlines for entities listed in 2026acn.gov.it, in Italian, accessed 16 November 2026
- ACN, determination no. 314287 of 2026, platform and relevant suppliersacn.gov.it, in Italian, accessed 16 November 2026
- ACN, NIS frequently asked questions, scopeacn.gov.it, in Italian, accessed 16 November 2026
- ACN, NIS frequently asked questions, security measures and incident notificationacn.gov.it, in Italian, accessed 16 November 2026
- ACN, «ACN convoca il Tavolo per l'attuazione della disciplina NIS», 9 April 2026acn.gov.it, in Italian, accessed 16 November 2026
- Commission Implementing Regulation (EU) 2024/2690, annex, point 5eur-lex.europa.eu, accessed 16 November 2026
- ENISA, «NIS2 Technical Implementation Guidance», version 1.0, 26 June 2025enisa.europa.eu, accessed 16 November 2026
- European Commission, «ICT supply chain security: EU adopts a toolbox to mitigate risks», 13 February 2026digital-strategy.ec.europa.eu, accessed 16 November 2026
If my customer is subject to NIS2, does that make me subject too?
No, not for that reason. You are subject if your sector is in the annexes of Italian Legislative Decree 138/2024 and you exceed the small-enterprise thresholds, or in a few cases regardless of size. The ACN says it plainly: a supplier to a NIS entity has contractual obligations, but it is not a NIS entity and the ACN does not supervise it.
When does a supplier become subject to NIS2 itself?
In four cases: its sector is in annex I or II and it exceeds the small-enterprise thresholds, meaning at least 50 people or more than 10 million in both turnover and balance sheet; it provides public electronic communications, trust services or DNS; it is linked to the entity and provides it with IT or security services; the ACN identifies it as a systemic element of the supply chain.
Is there an official NIS2 questionnaire for suppliers?
No. As of 16 November 2026 neither the ACN nor the European Commission publishes one, and each customer writes its own. The questions nearly always come from the 17 areas the ACN asks essential entities to consider in supplier requirements: access, data, incidents, continuity, secure development, updates, end of supply, subcontracting and the others.
Do I have to accept the new clauses on contracts already running?
Not by law. The ACN says it is not mandatory to amend contracts already in place: security requirements are mandatory for contracts signed, renewed or extended from the measures deadline, October 2026 for entities listed in 2025 and 31 July 2027 for those listed in 2026. The customer can still ask for them earlier.
Can the customer require me to hold ISO 27001?
The law cannot: no ACN measure imposes a certification on the supplier. The customer can, however, make it a condition of the contract. You can offer equivalent evidence, area by area, or a certification path with a date; if the customer still wants it, that is a commercial choice, not a NIS2 obligation.
How fast must I report an incident to the customer?
Within the deadline written in the contract: the decree sets none for the supplier. The customer must send CSIRT Italia an early warning within 24 hours and a notification within 72, so it will ask you for a few hours. Have the contract state precisely which events to report, to whom and through which channel.
What do I risk if I do not answer the NIS2 questionnaire?
No fine from the ACN, because you are not subject. The risk is the contract: the customer must document its supplier requirements and checks, and without your answers it may not renew or may pick another supplier. The fines are the customer's, up to 10 million euros or 2% of worldwide turnover for an essential entity.
Why does the customer ask for my tax code and CPV codes?
Because every year, from 15 April to 31 May, it must list its relevant suppliers with the ACN: those providing IT services and those with no alternative. For each it gives the name, tax code, country of the registered office, the CPV codes of the supply and the relevance criterion. Being on that list does not make you subject.
A NIS2 questionnaire on your software to fill in?
Tell us what your customer is asking, in an introductory call, free and with no commitment: we tell you which answers about your software and systems you can already document and what it would take for the others.
- You won't talk to a salesperson
- NDA before we get into the details
- The code stays yours
Articles on the same topics.

Data quality: data decides, not the model
When AI gets it wrong, blame the data, not the model. How to identify, sanitize and refresh your sources so AI actually works in your next business project.
Read
European AI Act who does it really affect?
The EU AI Act doesn't only target those who build the models, but those who use AI in business. What applies from 2 August 2026 and what moves to 2027-2028.
Read
Digital accessibility is not a badge
Discover why accessibility overlays fail WCAG 2.2 AA compliance and why building native accessibility is crucial for legal and commercial success.
Read