An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 Supplier Security Questionnaire: Questions and Evidence
Readiness Templates Software Automation / 2026-10-11

NIS2 Supplier Security Questionnaire: Questions and Evidence

This article is the ready-to-use template: the questionnaire itself, grouped by topic, with the evidence a supplier should provide alongside each answer. For the surrounding process - how to scope a questionnaire, send it, score the answers and act on them as part of supplier risk management - see the companion guide on building a NIS2 supplier security questionnaire.

Headnote

A supplier security questionnaire helps covered entities assess cybersecurity risks arising from direct suppliers and service providers. Article 21(2)(d) includes supply-chain security, but a completed questionnaire should be corroborated with evidence and proportionate follow-up based on service criticality.

Scope the supplier relationship first

Identify the contract, supplied service, systems accessed, information handled, subcontracting dependencies and possible effect on the covered entity's services. Rank assurance needs using exposure and operational criticality rather than giving every vendor an identical form.

Article 21(2)(d) addresses supply-chain security, including security-related aspects of relationships with direct suppliers and service providers. National and applicable sector-specific measures may add requirements.

Ask about governance and incident handling

Request accountable security contacts, relevant policy scope, incident detection and response responsibilities, escalation channels and the supplier's approach to vulnerability handling. Ask how critical incidents would be communicated to customers and within what contracted timeframe.

Distinguish provider notifications to the customer from the covered entity's own regulatory reporting duties. A supplier's delay can affect the information available for the entity's Article 23 assessment.

Assess access, resilience and technical protections

Ask about administrative access, authentication, logging, supported software, backup testing, recovery targets, segmentation, encryption and physical safeguards where relevant to the purchased service.

For cloud or managed services, clarify the shared-responsibility boundary. Questionnaires should request details appropriate to the risk without demanding confidential technical secrets unnecessary for assurance.

Request targeted evidence and evaluate findings

Accept suitable independent assurance, scoped test findings, certification details and documented exercise results where relevant, while verifying that the evidence covers the actual services and period. A certificate alone does not establish every control in operation.

Record unanswered questions, material exceptions, compensating controls and remediation commitments. Assign an owner to decide whether a residual risk is acceptable or requires contractual changes.

Build ongoing review into the relationship

Include contractual obligations for incident notice, material service changes, audit or assurance access where appropriate, subcontractor controls and orderly termination. Reassess after major incidents, architectural changes or a supplier's significant control failure.

For providers covered by Implementing Regulation (EU) 2024/2690, more detailed requirements may apply to their own operations. These provisions should not be described as universally binding on all suppliers in a supply chain.

Questions on the text

Does completing this checklist prove NIS2 compliance?

No. Checklists support a documented assessment; actual obligations depend on applicable legislation and effective controls.

Can software replace a legal or operational assessment?

No. Automation can organise evidence and reminders, while accountable reviewers must evaluate legal requirements and material risks.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.