vendorapp logo

Docs

NIS2 supplier questionnaire: what to actually ask


Short answer. There is no official NIS2 questionnaire. Build one that maps to the ten Article 21(2) measures and to your actual dependency on the supplier — roughly 20–30 targeted questions for a critical supplier, each tied to an evidence request, with depth scaled down for lower tiers.

Last reviewed: 31 July 2026.

What to ask suppliers under NIS

Most supplier questionnaires fail for the same reason: they ask everything, verify nothing, and get filed. A questionnaire is only useful if the answers change a decision — the tier, the contract, the remediation plan, or whether you buy at all.

Design principles

  • Map to Article 21(2). If a question does not trace back to one of the ten measures or to your dependency, cut it.
  • Ask for evidence, not assertions. Every "yes" that matters should have an attachment.
  • Tier the form. Three lengths — critical, significant, low — not one form with skip logic nobody maintains.
  • Ask closed questions. "Do you require MFA for all remote administrative access? (Y/N — if N, describe compensating controls)" beats "describe your access control approach".
  • Date everything. Answers are point-in-time; capture when they were given and by whom.
  • Reuse. Accept a recent completed standard questionnaire (CAIQ, SIG) plus your delta questions rather than forcing a rewrite.

The core questionnaire

Grouped by the Article 21(2) measure each supports.

Governance and risk (a)

  1. Who is accountable for information security, and to whom do they report?
  2. Do you hold ISO 27001, SOC 2 Type II or an equivalent? Provide the certificate and scope statement — does it cover the service we buy?
  3. When was your last independent security assessment, and can you share the summary and remediation status?

Incident handling (b) 4. Do you have a documented, tested incident response plan? When was it last exercised? 5. Within what timeframe will you notify us of an incident affecting our data or services? 6. Who is the named 24/7 security contact, and through what channel? 7. Have you experienced a security incident affecting customer data in the last 24 months? What changed as a result?

Continuity (c) 8. What are your recovery time and recovery point objectives for our service? 9. When did you last test failover or restoration, and what was the result?

Supply chain (d) 10. Which subcontractors or sub-processors are material to the service you provide us? 11. Do you impose equivalent security obligations on them, and how do you verify compliance? 12. Will you notify us before material changes to that list?

Secure development and vulnerabilities (e) 13. Do you perform security testing before release? Describe the gates. 14. What are your remediation timeframes for critical and high vulnerabilities? 15. Do you operate a coordinated vulnerability disclosure policy? Where is it published?

Effectiveness (f) 16. How do you measure whether your security controls are working, and who reviews the results?

People and hygiene (g, i) 17. Do personnel with access to our data receive security training, and how often? 18. Do you screen personnel proportionately to their access? 19. Describe joiner, mover and leaver handling for accounts with access to our environment.

Cryptography (h) 20. Is our data encrypted in transit and at rest? What algorithms and key management?

Access and authentication (i, j) 21. Is MFA enforced for all remote and administrative access? 22. How is privileged access to our data granted, reviewed and revoked? 23. Are administrative actions on our data logged, and can those logs be provided to us?

Dependency and jurisdiction 24. Where is our data stored and processed, and from which countries is it accessed or supported? 25. What is your legal entity, ownership structure and ultimate parent? 26. What happens to our data on termination — return format, deletion standard, timeline, verification?

Extra questions for software suppliers

  • Will you provide an SBOM, or disclose third-party components on request?
  • How are you notified of vulnerabilities in your dependencies, and what is your response time?
  • How do you notify customers of vulnerabilities affecting the version we run?
  • What is your supported-version policy and end-of-support notice period?
  • Are build and release pipelines protected against tampering, and are artefacts signed?

Extra questions for cloud and managed services

  • What exactly is your responsibility versus ours under the shared responsibility model?
  • Which of your staff can access our tenant, under what controls, and is access logged and reviewable by us?
  • Can we export our data and logs at any time, in a usable format?
  • How is our tenant isolated from other customers?
  • What notice do you give of region, architecture or sub-processor changes?

Managed service providers deserve particular scrutiny — see How does NIS2 treat MSPs and ICT service providers?

Questions to drop

  • Anything answerable "we follow industry best practice" without consequence.
  • Long free-text policy descriptions you will not read.
  • Questions about controls irrelevant to the service you buy — physical data centre security from a SaaS reseller, for example.
  • Duplicates of what a current certification's scope already covers.
  • Anything you have no intention of verifying or acting on.

Cutting these is not a shortcut. Every question you remove increases the chance the remaining ones are answered accurately.

Verifying the answers

A questionnaire is a claim by the supplier about the supplier. Three independent checks turn it into assurance:

  1. Documentary evidence — certificates with scope, audit reports, test summaries, policy extracts. Check dates and scope, not just existence.
  2. Independent signals — sanctions and watchlist exposure, ownership and jurisdiction, breach history, financial stability. These do not depend on the supplier's cooperation, and they are the ones that reveal what a questionnaire will not. Vendorapp screens vendors against consolidated global lists as part of assessment; see global sanctions screening and tri-risk ratings.
  3. Contractual reinforcement — the important answers become obligations. If they told you 24-hour notification, the contract says 24 hours.

What to do with the results

  • Record the assessment with its date, author, inputs and conclusion.
  • Turn gaps into a remediation log with an owner and a due date — not a note in a spreadsheet cell.
  • Feed material findings into the tier: an answer can move a supplier up.
  • Set the reassessment trigger. See How often do you have to reassess suppliers?
  • Keep it retrievable. The value of the assessment at supervision time is entirely a function of whether you can produce it. See What supply chain evidence do regulators expect?