Questionario per fornitori NIS 2
Le domande che un soggetto regolato da NIS 2 deve porre ai propri fornitori. Ancorate una volta al diritto dell'UE. Libere da usare.
Quasi ogni team di approvvigionamento nel mid-market europeo sta attualmente scrivendo il proprio questionario per fornitori NIS 2. Le stesse domande ancorate all'UE, in forme leggermente diverse, inviate a fornitori che finiscono per compilare cinque versioni della stessa cosa. Questo questionario è la base condivisa.
Ogni domanda indica la sua fonte a livello UE: il regolamento di esecuzione (UE) 2024/2690, la Technical Implementation Guidance dell'ENISA, il GDPR o il Cyber Resilience Act. 46 delle 50 domande indicano anche i controlli dell'allegato A della ISO/IEC 27001:2022 a cui servono, secondo la corrispondenza dell'ENISA. Sovrapposizioni settoriali come TISAX, VDA ISA, BSI C5 o i cataloghi di audit KRITIS si collocano sopra questa base, non al suo posto.
Ogni fornitore risponde a 21 domande. Quali altre vede dipende da ciò a cui accede presso i suoi clienti: i loro dati, i loro sistemi, i loro locali, il software che gestisce o consegna, o l'IT che gestisce per loro. Ogni domanda condizionale indica la risposta da cui dipende.
- Versione
- 4.0.0
- Ultimo aggiornamento
- 2026-10-04
- Campi
- 50
- Licenza
- MIT (schema) + CC BY 4.0 (contenuto)
Profilo del fornitore
16 campiDenominazione legale
Il nome registrato della vostra azienda, così come appare nel registro delle imprese. Esempio: Müller GmbH o Acme Software Ltd.
Base giuridica: CIR 2024/2690 §5.2
Indirizzo della sede legale
L'indirizzo commerciale registrato della vostra azienda. È sufficiente un solo indirizzo, anche se avete più sedi.
Base giuridica: CIR 2024/2690 §5.2
Paese
Il paese in cui la vostra azienda è legalmente stabilita. Due lettere, ad esempio DE per la Germania.
Base giuridica: CIR 2024/2690 §5.2
Dominio principale
Il vostro dominio principale, di solito l'URL del vostro sito web. Esempio: acmesoftware.com.
Base giuridica: CIR 2024/2690 §5.2(a)
Description of services provided
One paragraph on what you deliver to customers: concrete products, services or work, not marketing. Examples: “Office cleaning three evenings a week, with keys to the building” or “Payroll accounting for up to 200 employees”.
Base giuridica: CIR 2024/2690 §5.2(b)ISO/IEC 27001:2022 A.5.19, A.5.22
Nome del referente per la sicurezza
La persona che i clienti contattano in caso di incidente di sicurezza. Nelle aziende più piccole spesso l'amministratore delegato o il responsabile IT. È sufficiente una sola persona.
Base giuridica: CIR 2024/2690 §5.2(a)ISO/IEC 27001:2022 A.5.20, A.5.24
E-mail di contatto per gli incidenti
Indirizzo e-mail che i clienti utilizzano per segnalare un incidente di sicurezza. Idealmente una lista di distribuzione come security@example.com che raggiunge più persone.
Base giuridica: CIR 2024/2690 §5.2(a)ISO/IEC 27001:2022 A.5.20, A.5.24
Incident contact phone
Phone number for urgent incident reports. Add the hours it is answered in brackets; round-the-clock cover is not expected.
Base giuridica: CIR 2024/2690 §5.2(a)ISO/IEC 27001:2022 A.5.20, A.5.24
How fast you inform customers of an incident (hours)
At most this many hours after you notice a security incident that affects a customer, for example a data leak, a hacked account or a lost key. A customer under NIS 2 must send its authority an early warning within 24 hours of becoming aware of a significant incident (Art. 23(4)(a) NIS 2), so a promise of 24 hours or less helps them most. Give a value you keep.
Base giuridica: CIR 2024/2690 §5.1.4(d)ISO/IEC 27001:2022 A.5.20, A.5.24
Forniamo servizi SaaS / in hosting
Eseguite software per i clienti sulla vostra infrastruttura e lo erogate tramite internet. Selezionate più caselle se offrite più modelli.
Base giuridica: CIR 2024/2690 §5.2(b)ISO/IEC 27001:2022 A.5.19, A.5.22, A.5.23
Forniamo software on-premise
Fornite software che i clienti installano ed eseguono sulla propria infrastruttura.
Base giuridica: CIR 2024/2690 §5.2(b)ISO/IEC 27001:2022 A.5.19, A.5.22
Forniamo servizi gestiti / MSP
Gestite per il cliente parti della sua infrastruttura IT, con personale proprio. Tipico dei modelli MSP e MSSP.
Base giuridica: CIR 2024/2690 §5.2(b)ISO/IEC 27001:2022 A.5.19, A.5.22
We process or store our customers' data
Tick yes if you hold or handle your customers' data or documents, electronically or on paper, for example in software, a data centre, a ticket system, accounting or an archive.
Base giuridica: ENISA TIG §5.1.2ISO/IEC 27001:2022 A.5.19
Paesi / regioni in cui vengono trattati i dati dei clienti
Solo se: We process or store our customers' data = Sì
Tutti i paesi in cui i dati dei vostri clienti vengono archiviati o trattati. Separati da virgole, codici paese ISO. Esempio: DE, NL, US. Se trattate interamente all'interno dell'UE, è sufficiente elencare i paesi dell'UE.
Base giuridica: ENISA TIG §5.1.4 TIPSISO/IEC 27001:2022 A.5.20, A.5.23, A.5.34
We access our customers' systems
Tick yes if you can sign in to your customers' systems, remotely, as an administrator or on site, for example for maintenance, support or operations.
Base giuridica: ENISA TIG §5.1.2ISO/IEC 27001:2022 A.5.19
Our staff enter our customers' premises
Tick yes if your staff or subcontractors go into a customer's offices or buildings, escorted or not, for example for cleaning, maintenance, repairs, deliveries into the building or on-site support. Holding keys, badges or door codes counts.
Base giuridica: CIR 2024/2690 §11.1.2(a); §13.3.2(b)ISO/IEC 27001:2022 A.5.19
Prassi di sicurezza
28 campiStaff who work for customers are instructed in security when they start and at regular intervals
Tick yes if everyone who works for customers learns the security rules that apply to them when they start, and again at regular intervals, for example in a short briefing, an e-learning course or written rules they sign.
Base giuridica: CIR 2024/2690 §5.1.4(b)ISO/IEC 27001:2022 A.6.3
We accept audits by customers or provide audit reports
Tick yes if you either let customers audit you or give them audit reports instead (for example SOC 2, ISAE 3402).
Base giuridica: CIR 2024/2690 §5.1.4(e)ISO/IEC 27001:2022 A.5.20, A.5.22
We use subcontractors to deliver our service
Tick yes if other companies help you deliver your service and in doing so reach customer data, systems or premises. Examples: a cloud host such as AWS or Azure, a payment provider, or a subcontracted crew that works on site.
Base giuridica: CIR 2024/2690 §5.1.4(g)ISO/IEC 27001:2022 A.5.20, A.5.21
List of subcontractors
Solo se: We use subcontractors to deliver our service = Sì
Every subcontractor with name, location and what they do for you. One per line is enough. Update it whenever you add or remove one.
Base giuridica: CIR 2024/2690 §5.1.4(g)ISO/IEC 27001:2022 A.5.20, A.5.21
We bind subcontractors to comparable security requirements
Solo se: We use subcontractors to deliver our service = Sì
Tick yes if your contracts with subcontractors contain security requirements that match what your customers ask of you, for example on incidents, access and data handling.
Base giuridica: CIR 2024/2690 §5.1.4(g)ISO/IEC 27001:2022 A.5.20, A.5.21
We inform customers of material changes, including where their data is processed
Tick yes if you tell customers before anything material changes in how you deliver: a takeover, a new subcontractor, another hosting provider, or a new country where their data is processed.
Base giuridica: ENISA TIG §5.1.4ISO/IEC 27001:2022 A.5.22
On request, we tell customers about security incidents that affected customers
Tick yes if, when a customer asks, you say openly whether and which security incidents affecting customers you had in the past.
Base giuridica: ENISA TIG §5.1.2ISO/IEC 27001:2022 A.5.22
We give customers the information their authority asks for
Tick yes if you give your customers the information their supervisory authority asks for after an incident or during an audit. Unless you are an essential or important entity under NIS 2 yourself, you owe that authority nothing directly; the duty is your customer's, and you help them meet it.
Base giuridica: ENISA TIG §5.1.4ISO/IEC 27001:2022 A.5.20, A.5.31
Everyone who works for our customers is bound to confidentiality
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Our staff enter our customers' premises = Sì
Tick yes if everyone who works for customers has signed a confidentiality commitment, in the employment contract or a separate agreement, or is bound by professional secrecy by law.
Base giuridica: ENISA TIG §5.1 TIPS; CIR 2024/2690 §10.3.2ISO/IEC 27001:2022 A.6.6
We check that staff who get access at customers are suitable
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Our staff enter our customers' premises = Sì
Tick yes if, before they start, you check that people who will have access to customer data, systems or premises (key holders, for example) are suitable for that role, as far as employment and data protection law allow: references, for example, or a criminal record certificate where lawful and needed for the role. Checking every member of staff is not expected.
Base giuridica: CIR 2024/2690 §10.2.1ISO/IEC 27001:2022 A.6.1
At contract end we hand back or destroy what we hold of the customer
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Our staff enter our customers' premises = Sì
Tick yes if your contract commits you to hand back the customer's data in a usable, documented format (for example CSV or JSON) and then delete it, return keys, badges and documents, and close accounts you had with them.
Base giuridica: CIR 2024/2690 §5.1.4(h); §5.1.2(d)ISO/IEC 27001:2022 A.5.11, A.8.10
Data processing agreement (Art. 28 GDPR)
Solo se: We process or store our customers' data = Sì
Needed when you process personal data on a customer's behalf and on their instructions (Art. 28(3) GDPR). Some professions are controllers by law and sign none, in Germany tax advisers (§ 11(2) StBerG).
- Yes, we offer a standard DPA
- Not needed: we are an independent controller (for example a tax adviser)
- Not needed: we process no personal data for customers
- No
Base giuridica: GDPR Art. 28(3); Art. 4(7)ISO/IEC 27001:2022 A.5.34
Customer data we hold electronically is encrypted
Solo se: We process or store our customers' data = Sì
Tick yes if customer data is encrypted wherever you store it electronically: on servers, laptops, phones and backups, for example with BitLocker, FileVault or your cloud provider's disk encryption.
Base giuridica: CIR 2024/2690 §5.1.2(c); §9.2(a)ISO/IEC 27001:2022 A.8.24
Customer data we send is encrypted in transit
Solo se: We process or store our customers' data = Sì
Tick yes if your websites and interfaces use HTTPS with TLS 1.2 or higher, and files go to customers through an encrypted portal or encrypted email.
Base giuridica: CIR 2024/2690 §5.1.2(c); §9.2(a)ISO/IEC 27001:2022 A.8.24
We run a documented information security management system (ISMS)
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì oppure Forniamo servizi gestiti / MSP = Sì
Tick yes if you have a written information security policy with assigned roles, regular reviews and documented incident handling. ISO/IEC 27001 certification, also on the basis of IT-Grundschutz, implies yes.
Base giuridica: CIR 2024/2690 §5.1.2(a)ISO/IEC 27001:2022 A.5.1
We hold a current security certificate or audit report that covers the service we deliver to customers
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì oppure Forniamo servizi gestiti / MSP = Sì
Counts: ISO/IEC 27001 (also on the basis of IT-Grundschutz), a BSI C5 attestation, a TISAX label, a SOC 2 Type II or ISAE 3402 report, or a European cybersecurity certificate. Tick yes only if its scope covers the service you deliver to customers.
Base giuridica: CIR 2024/2690 §5.1.2(a); ENISA TIG §5.1.2ISO/IEC 27001:2022 A.5.19, A.5.22
Certificate or report: standard, issuer, valid until, scope
Solo se: We hold a current security certificate or audit report that covers the service we deliver to customers = Sì
Copy the scope as it is printed on the certificate or report. Several? One per line.
Base giuridica: CIR 2024/2690 §5.1.2(a); ENISA TIG §5.1.2ISO/IEC 27001:2022 A.5.22
We install security updates promptly and follow up known vulnerabilities
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì oppure Forniamo servizi gestiti / MSP = Sì
Tick yes if you have a set routine for security holes in the systems and software you use for customers: you learn about them, judge how urgent they are, and install the update or take another measure in time.
Base giuridica: CIR 2024/2690 §5.1.4(f)ISO/IEC 27001:2022 A.8.8
We have a written plan for security incidents
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì oppure Forniamo servizi gestiti / MSP = Sì
Tick yes if a written plan sets out how you handle a security incident: who decides, who informs customers and who documents.
Base giuridica: CIR 2024/2690 §5.1.2(a); §3.1ISO/IEC 27001:2022 A.5.24, A.5.26
We have a written plan for outages, including backups
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì oppure Forniamo servizi gestiti / MSP = Sì
Tick yes if a written plan says how you keep working or restart after an outage, including backups of the data you hold for customers, kept apart from the live systems and test-restored. It names your critical systems, the fallback, and how long an outage may last and how much data may be lost at most.
Base giuridica: CIR 2024/2690 §5.1.2(c); §4.1; §4.2ISO/IEC 27001:2022 A.5.29, A.5.30, A.8.13
All internal administrator accounts are protected with a second factor
Solo se: We process or store our customers' data = Sì oppure We access our customers' systems = Sì oppure Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì oppure Forniamo servizi gestiti / MSP = Sì
Tick yes if every account with administrator rights in your own systems (email, cloud, servers, accounting) needs a second factor to sign in, such as an authenticator app or a security key. Codes by SMS count but are the weakest option.
Base giuridica: CIR 2024/2690 §5.1.2(a); §11.7ISO/IEC 27001:2022 A.8.5, A.8.2
The systems we use to serve customers are security tested by an independent party
Solo se: Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì oppure Forniamo servizi gestiti / MSP = Sì
Tick yes if an independent party tests these systems for security holes, as often as your risk calls for. A penetration test and an external vulnerability scan both count.
Base giuridica: CIR 2024/2690 §5.1.2(a); §6.5ISO/IEC 27001:2022 A.8.29, A.8.8
We develop to defined secure development rules
Solo se: Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì
Tick yes if your development follows set rules, for example a review before every change goes live, dependencies kept up to date, tests, and a check for known vulnerabilities. Asked only of suppliers who run software as a service or ship software.
Base giuridica: CIR 2024/2690 §5.1.2(a)ISO/IEC 27001:2022 A.8.25, A.8.28
We publish how to report a security hole to us
Solo se: Forniamo servizi SaaS / in hosting = Sì oppure Forniamo software on-premise = Sì
Tick yes if your website says how to report a security hole and what you then do, for example in a security.txt file (RFC 9116). From 11 December 2027 the Cyber Resilience Act requires such a policy and a contact address from makers of software products.
Base giuridica: CIR 2024/2690 §5.1.4(f); CRA Annex I Part II(5), (6)ISO/IEC 27001:2022 A.8.8, A.5.21
Access to customer systems uses personal accounts with a second factor
Solo se: We access our customers' systems = Sì
Tick yes if everyone who signs in to customer systems uses their own account with a second factor, including remote maintenance tools such as TeamViewer; nobody shares a login.
Base giuridica: CIR 2024/2690 §5.1.4(a); §11.3.2(a); §11.5.2(b)ISO/IEC 27001:2022 A.8.2, A.8.5, A.5.16
Administrative access to customer systems is logged
Solo se: We access our customers' systems = Sì
Tick yes if it is recorded who accessed your customers' systems with administrator rights, and when, so it can be traced afterwards. Recording whole sessions is not expected.
Base giuridica: CIR 2024/2690 §5.1.4(a); §3.2.3(e)ISO/IEC 27001:2022 A.8.15
We keep track of the keys, badges and codes customers give us
Solo se: Our staff enter our customers' premises = Sì
Tick yes if you always know who holds which key, badge or code, take it back when someone leaves or changes job, and tell the customer without delay when one is lost.
Base giuridica: CIR 2024/2690 §5.1.4(a); §11.2.2(d); §13.3.2(b)ISO/IEC 27001:2022 A.7.2, A.5.11, A.5.18
Our staff on customer premises follow written rules of conduct
Solo se: Our staff enter our customers' premises = Sì
Tick yes if your staff have written rules for working at customers, for example: let no one in, leave screens, devices and documents alone, report anything unusual to the customer.
Base giuridica: ENISA TIG §5.1 TIPS; CIR 2024/2690 §8.1.1ISO/IEC 27001:2022 A.7.2, A.7.7, A.6.3
Software come servizio (SaaS)
2 campiCustomers can protect their accounts with a second factor
Solo se: Forniamo servizi SaaS / in hosting = Sì
Tick yes if your application offers sign-in with a second factor (an authenticator app, a security key or a one-time code), at least for your customers' administrators. Your own internal admin accounts are a separate question under security practices.
Base giuridica: CIR 2024/2690 §5.1.2(c); §11.7ISO/IEC 27001:2022 A.8.5, A.5.23
Longest outage until your service is restored (hours)
Solo se: Forniamo servizi SaaS / in hosting = Sì
The most hours your service may be unavailable before it is restored. Give a value you keep.
Base giuridica: ENISA TIG §5.1 TIPSISO/IEC 27001:2022 A.5.30, A.5.23
Software presso il cliente (on-premise)
4 campiUntil when you supply security updates for the version you deliver
Solo se: Forniamo software on-premise = Sì
Month and year, or the rule you apply. From 11 December 2027 the Cyber Resilience Act requires manufacturers to state this date at the time of purchase.
Base giuridica: CIR 2024/2690 §6.1.2(b); CRA Art. 13(19)ISO/IEC 27001:2022 A.5.21
Deadline for security updates for critical vulnerabilities (hours)
Solo se: Forniamo software on-premise = Sì
Hours from a critical vulnerability becoming known to your fixed release. From 11 December 2027 the Cyber Resilience Act requires manufacturers to fix vulnerabilities without delay.
Base giuridica: CIR 2024/2690 §5.1.4(f); CRA Annex I Part II(2)ISO/IEC 27001:2022 A.8.8
Customers can get a Software Bill of Materials (SBOM)
Solo se: Forniamo software on-premise = Sì
Tick yes if you give customers an SBOM for your releases (CycloneDX or SPDX). From 11 December 2027 the Cyber Resilience Act requires manufacturers to keep an SBOM in the technical documentation of products with digital elements; handing it to customers is up to you.
Base giuridica: CIR 2024/2690 §6.1.2(c); CRA Annex I Part II(1)ISO/IEC 27001:2022 A.5.21
Releases and updates are signed
Solo se: Forniamo software on-premise = Sì
Tick yes if every release and update carries a signature your customers can check before installing, for example Sigstore, Authenticode or PGP.
Base giuridica: CIR 2024/2690 §6.6.1(c); CRA Annex I Part II(7)ISO/IEC 27001:2022 A.5.21
Questo questionario copre la sostanza giuridica dell'UE per la due diligence sui fornitori ai sensi di NIS 2. È inteso come base condivisa, non come modello completo specifico per settore.
TISAX, VDA ISA, BSI C5, i cataloghi di audit KRITIS e le vostre sovrapposizioni di rischio si collocano sopra come estensioni. Fate fork del repository, aggiungete le vostre domande settoriali, oppure usate i campi condivisi come base per il vostro modello.