Headnote
A supplier security questionnaire can collect structured evidence about the cyber risks of a product or service supporting covered operations. NIS2 does not prescribe one universal questionnaire. The questions should reflect Article 21 supply chain security, supplier-specific vulnerabilities and the organisation's actual dependencies.
Begin with scope and criticality
Record the supplier's legal name, the contracted product or service, relevant infrastructure, information handled, geographic and subcontractor dependencies, and access to covered systems. Use the answers to focus the remainder of the review.
Avoid demanding the same exhaustive response from a low-risk vendor and a privileged managed service provider. Ask who owns the relationship and which service would be affected by failure.
Ask about governance and access
Relevant questions include who is responsible for information security, how privileged access is approved, whether multifactor authentication is used where appropriate, and how employee or subcontractor access is removed.
Request evidence at a sensible level. A documented process, a scoped assurance report or a demonstrated control may support answers better than an unsupported yes-or-no assertion.
Cover vulnerability and incident processes
Ask how relevant vulnerabilities are identified, assessed, communicated and remediated, including software update support and secure development where applicable. Seek incident escalation contacts, criteria for notification and procedures for cooperation with customers.
Article 21(3) makes supplier-specific vulnerabilities and the quality of cybersecurity practices relevant. Contractual supplier notices should be distinguished from the covered entity's own regulatory incident-reporting duties.
Examine continuity and indirect dependencies
Ask how the supplier restores important services, tests backups, manages concentration risk and deals with material subcontractors. Confirm whether recovery commitments cover the actual supplied service and its shared dependencies.
Where a supplier cannot disclose sensitive details about its subproviders, record the limitation and seek reasonable assurance about the oversight mechanisms in place.
Score responses without false precision
Define critical failures, missing evidence and opportunities for remediation before collecting answers. Consider the severity of a weakness in the context of the supplied service rather than allocating identical numerical weights to every question.
Document unresolved issues, the risk owner and the approval for continuing the relationship. Avoid treating a completed questionnaire as a certification or proof that controls operate effectively.
Refresh questions and maintain supporting evidence
Review the questionnaire after incidents, service changes, changes in law or significant changes in the threat environment. Keep version history, supporting documents, reviewer decisions and completed remediation together.
Check applicable national legislation and any entity-specific requirements under Implementing Regulation (EU) 2024/2690. The questionnaire is a practical method for supplier oversight, not a statutory NIS2 form.
Questions on the text
Is there an official universal NIS2 supplier questionnaire?
The Directive does not prescribe one universal supplier questionnaire for all covered entities. Tailor questions to identified risks and applicable obligations.
Can a questionnaire replace technical verification?
No. Higher-risk assertions should be supported by relevant evidence or practical verification where feasible.