NIS2 Directive — EU 2022/2555 · Article 21(2)(d)

NIS2 Vendor Compliance:
What Article 21 Actually Requires

NIS2 enforcement is active across the EU. National competent authorities are conducting Article 21 reviews — and supply chain risk documentation is the first thing they ask for. This guide explains what compliance means in practice, who it affects, and how to build a defensible programme without a GRC consultant or a €50k tool.

NIS2 Article 21 vendor requirement — in plain English
NIS2 Article 21(2)(d) requires you to assess, document, and maintain ongoing oversight of your suppliers and ICT service providers — and to produce that evidence to regulators on request. A vendor list in a spreadsheet is not evidence of oversight. A dated, continuously maintained risk programme is. Most organisations have the list. Very few have the programme.

Who is affected

NIS2 vendor compliance: direct scope and supply chain pressure

NIS2 creates two categories of organisations that need to take vendor compliance seriously — those directly in scope and those indirectly affected through their customers’ requirements.

Directly in scope

18 Critical Sectors

Energy, transport, banking, financial market infrastructure, health, drinking water, digital infrastructure, ICT service management, public administration, and more. Medium (50+ employees / €10m+ turnover) and large organisations in these sectors must comply with Article 21 in full.

Direct obligation
Directly in scope

Digital Service Providers

Cloud computing services, online marketplaces, online search engines, and social networking platforms above size thresholds. ICT managed service providers are explicitly included — if you provide outsourced IT to regulated businesses, NIS2 applies to you directly, not just via your clients.

Direct obligation
Indirectly affected

Suppliers to In-Scope Organisations

If your customers include banks, energy companies, healthcare providers, or any other NIS2-regulated entity, their Article 21(2)(d) obligation flows directly to you via vendor questionnaires and contract requirements. You do not need to be in scope yourself to face NIS2 vendor compliance demands from enterprise customers.

Supply chain pressure

The five requirements

What NIS2 Article 21 actually requires for vendor compliance

Article 21(2)(d) is deliberately broad — it requires “supply chain security.” National competent authorities have clarified what this means in practice across five areas.

1

A complete, current vendor register

A full inventory of all suppliers and ICT service providers, classified by criticality to your operations. Not a one-time exercise — auditors verify the register is current and reflects recent vendor changes. Critical vendors (those whose failure would significantly disrupt your operations) require the most rigorous documentation.

VendorAuditly: live vendor register with risk tiers and auto-scoring
2

Documented risk assessments per vendor

Risk assessments must be documented, dated, and proportionate to each vendor’s criticality. Auditors look for evidence of methodology — how you determined the risk tier, what criteria you applied, and when you last reviewed it. An undated spreadsheet cell saying “medium risk” does not satisfy this requirement.

VendorAuditly: risk scores with full audit trail, methodology, and review dates
3

Security questionnaires sent and tracked

Evidence that you have assessed each critical vendor’s security posture directly — through questionnaires, self-assessments, or third-party audit reports. Auditors want to see: when questionnaires were sent, whether they were chased for non-response, what the responses contain, and how gaps were addressed. The send timestamp and chase log matter as much as the responses themselves.

VendorAuditly: NIS2 questionnaire templates, auto-chase, response tracking with timestamps
4

Contractual security obligations in critical vendor contracts

Contracts with critical vendors must include security obligations: breach notification timelines (NIS2 requires 24/72-hour notification chains), audit rights, data processing terms, and incident cooperation requirements. Auditors may request contract clauses for critical vendors — missing clauses are a finding requiring remediation.

VendorAuditly: AI contract clause checker flags missing NIS2 obligations automatically
5

Continuous oversight, not annual point-in-time reviews

NIS2 requires ongoing monitoring — not a once-a-year audit. Evidence of continuous oversight includes: certificate expiry tracking with alerts, breach monitoring, reassessment records after vendor incidents, and a programme that updates when vendors change their security posture. A programme last reviewed 14 months ago is a compliance gap regardless of what it contained.

VendorAuditly: continuous monitoring, expiry alerts, breach watchlist, live risk scores

Excel vs consultant vs software

How to meet NIS2 vendor compliance requirements

Three approaches exist. Each has different costs, limitations, and outcomes when a regulator asks for evidence. Here is an honest comparison.

Requirement Spreadsheet GRC consultant VendorAuditly ($49/mo)
Vendor register ∼ Manual, no structure ∼ Built once, not maintained ✓ Live, risk-tiered, searchable
Dated risk assessments ✗ No audit trail or timestamps ∼ Point-in-time only ✓ Auto-timestamped, full history
Questionnaire tracking ✗ Email threads, no evidence log ∼ Manual, billed by hour ✓ Sent, chased, logged automatically
Certificate expiry alerts ✗ Manual calendar reminders ✗ Not included ✓ Automated alerts, AI extraction
Contract clause checks ✗ Not possible ∼ Manual, expensive ✓ AI flags missing NIS2 clauses
Continuous monitoring ✗ Static, not live ✗ Annual engagement only ✓ Weekly scans, breach watchlist
Regulator-ready evidence pack ✗ Not exportable in standard format ∼ Custom report, weeks turnaround ✓ One-click NIS2 Article 21 PDF
Annual cost Staff time (40–80 hrs/year) €5,000–€20,000+ $588/year ($49/month)

Getting compliant

How to build a NIS2-compliant vendor programme in 4 steps

Most organisations can build a defensible Article 21 programme in two weeks. The key is starting with the vendor register and working outward — not trying to do everything at once.

Step 1 — Week 1

Build and classify your vendor register

Import your full supplier list. Classify each vendor as critical, high, medium, or low based on: data access, operational dependency, and potential disruption impact. This is the foundation — everything else is built on it.

  • Import from existing spreadsheet or enter manually
  • Assign criticality tier using the built-in risk framework
  • Flag data-processing vendors separately for GDPR overlap
  • Generate register export for internal sign-off
Step 2 — Week 1

Send NIS2 questionnaires to critical vendors

Send Article 21-aligned security questionnaires to your top critical vendors immediately. The send timestamp creates your evidence — even partial responses are better than no documented assessment.

  • Use the NIS2 questionnaire template (pre-built)
  • Send via public link — no vendor login required
  • Automatic 3-day and 7-day chaser emails
  • Response tracking dashboard with completion status
Step 3 — Week 2

Upload certificates and run contract checks

Upload insurance certificates, ISO 27001 certs, and SOC 2 reports from critical vendors. Run AI contract analysis on top-5 vendor contracts to identify missing NIS2 Article 21 clauses — audit rights, breach notification, data location.

  • AI extracts expiry dates from certificates automatically
  • Alerts fire 90, 60, and 30 days before expiry
  • Contract clause checker flags missing NIS2 obligations
  • Findings created automatically for gaps
Step 4 — Ongoing

Export evidence pack and maintain continuously

Generate your NIS2 Article 21 evidence pack — a regulator-formatted PDF containing everything an auditor will ask for. Schedule quarterly re-assessments to keep the programme live, not point-in-time.

  • One-click NIS2 Article 21 evidence pack export
  • Continuous breach watchlist monitoring
  • Weekly vendor website scans for security changes
  • Quarterly re-assessment reminders built in

Frequently asked questions

NIS2 vendor compliance — common questions

What does NIS2 Article 21 require for vendor compliance?
NIS2 Article 21(2)(d) requires organisations to implement supply chain security measures covering the security practices of direct suppliers and ICT service providers. In practice: a complete vendor register with criticality classifications, documented risk assessments, security questionnaires sent and tracked, contractual security obligations in critical vendor contracts, and ongoing monitoring. Regulators expect dated, documented evidence — not a policy statement.
Can a spreadsheet satisfy NIS2 vendor compliance requirements?
A spreadsheet can hold a vendor list, but it cannot produce a regulator-formatted evidence pack, cannot automatically track certificate expiry dates, cannot timestamp when questionnaires were sent and chased, and cannot demonstrate continuous monitoring rather than a one-time exercise. NIS2 Article 21 reviewers specifically look for evidence of ongoing oversight. A spreadsheet is a starting point — not a compliance programme.
Does NIS2 vendor compliance apply to my company even if we are a small supplier?
NIS2 directly applies to medium and large organisations (50+ employees or €10m+ turnover) in 18 critical sectors. However, if you supply software, cloud services, or managed IT to any NIS2-regulated entity, their Article 21(2)(d) obligation flows down to you via vendor questionnaires and contract requirements. Most SMBs serving enterprise clients in banking, energy, healthcare, or digital infrastructure are already receiving NIS2 compliance demands from their customers — regardless of their own direct scope status.
What is the difference between NIS2 and DORA vendor compliance requirements?
DORA (Digital Operational Resilience Act) applies only to financial services entities and their ICT vendors. NIS2 extends the same supply chain risk logic to 18 critical sectors including energy, health, transport, and manufacturing. If you are a financial services firm, both regulations apply and the evidence overlaps significantly — a DORA-compliant vendor programme covers approximately 70–80% of NIS2 Article 21 requirements. VendorAuditly generates both DORA and NIS2 evidence packs from the same vendor data.
How long does it take to build a NIS2-compliant vendor programme?
Initial setup takes under 10 minutes: import your vendor list, assign risk tiers, and send Article 21 questionnaire templates to critical vendors. A fully documented programme — register, risk assessments, questionnaire responses, certificates uploaded — can be in place within two weeks for a typical company with 10–30 vendors. The ongoing commitment is smaller: monthly reviews of open findings, quarterly re-assessments for critical vendors, and certificate expiry tracking (which VendorAuditly automates).

NIS2 enforcement is active

Build your Article 21 vendor programme today.

Import your vendor list, send NIS2 questionnaires, and export a regulator-ready evidence pack — all in under 10 minutes. No GRC consultant. No enterprise contract.

Free forever on 3 vendors  ·  NIS2 evidence pack included  ·  $49/month for full programme