vendorapp logo

Docs

Does NIS2 require vendor risk assessments?


Short answer. Yes. Article 21(2)(d) makes supply chain security one of the ten minimum measures every in-scope entity must implement, and Article 21(3) requires you to take account of the specific vulnerabilities of each direct supplier and service provider and the overall quality of their products and cybersecurity practices.

Last reviewed: 31 July 2026.

Does NIS require vendor risk assessments

The directive never uses the phrase "vendor risk assessment". It does something more demanding: it requires an outcome that cannot be achieved without one.

If you must take into account the vulnerabilities specific to each direct supplier, the quality of their products and cybersecurity practices, and their secure development procedures — and you must be able to demonstrate that to a supervisor — then you are performing supplier assessments, whatever you call them internally.

Where the requirement comes from

Three provisions stack:

Article 21(2)(d) lists as a minimum measure: supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers.

Article 21(3) adds the substance: entities shall take into account the vulnerabilities specific to each direct supplier and service provider and the overall quality of products and cybersecurity practices of their suppliers and service providers, including their secure development procedures. It also requires entities to take into account the results of the coordinated security risk assessments of critical supply chains carried out under Article 22.

Article 21(1) sets the standard: measures must be appropriate and proportionate, following an all-hazards approach, taking into account the state of the art, the entity's exposure to risks, its size, and the likelihood and severity of incidents including their societal and economic impact.

Read together: per-supplier, risk-proportionate, evidenced.

What the directive does not say

It does not prescribe:

  • a questionnaire, a scoring model or a rating scale;
  • an assessment frequency;
  • a certification you must demand from suppliers;
  • a supplier tiering scheme;
  • a tooling requirement.

That freedom is often mistaken for laxity. It is the opposite — you cannot point at a completed standard template and declare compliance. You have to be able to explain why your approach is appropriate to your risk, which requires a documented method.

For the digital entities covered by Commission Implementing Regulation (EU) 2024/2690, the picture is more prescriptive: that regulation requires a supply chain security policy, documented criteria for selecting and contracting suppliers, and review at planned intervals. It is a good template even where it does not legally bind you.

What a defensible assessment covers

A supplier assessment that stands up to Article 21(3) generally establishes:

  1. Who the supplier actually is — legal entity, ownership, jurisdiction, group structure. Ownership and jurisdiction drive both regulatory and geopolitical exposure.
  2. What the dependency is — which of your services rely on them, what data they hold, what access they have, and how quickly their failure would hurt.
  3. Their security practices — governance, access control, encryption, vulnerability management, incident response, business continuity, and where relevant secure development procedures.
  4. Their assurance — certifications (ISO 27001, SOC 2) with scope statements, audit reports, pen test summaries. Scope matters more than the badge.
  5. Their own supply chain — whether they manage their subcontractors, and which fourth parties sit behind a critical dependency.
  6. Adverse signals — sanctions and watchlist exposure, breach history, financial distress, litigation.
  7. The residual risk decision — what you concluded, who accepted it, and what conditions or compensating controls apply.

Points 1, 6 and 7 are the ones most often missing. A questionnaire response is a claim; entity, sanctions and stability data are independent evidence.

How deep does the assessment have to go

Proportionality does the work here. A workable tiering:

TierTypical criteriaAssessment depth
CriticalSupports an in-scope service, or holds sensitive data, or has privileged network access, or is not readily substitutableFull assessment, evidence review, contract with security and notification clauses, annual reassessment and continuous monitoring
SignificantMaterial dependency but substitutable, or limited data accessStandard questionnaire, certification review, contract clauses, periodic reassessment
LowNo system access, no sensitive data, easily replacedRecorded triage decision, screening for adverse signals, refresh on renewal

The tier must be derived from criteria you wrote down, not from who shouts loudest. See How often do you have to reassess suppliers?

Common mistakes

  • Assessing only new suppliers. The requirement is about the relationship, which persists. An unassessed ten-year incumbent with domain admin rights is the higher risk.
  • Treating certification as the assessment. An ISO 27001 certificate whose scope excludes the service you buy proves nothing about that service.
  • One questionnaire for everybody. A 200-question form sent to a stationery supplier discredits the whole programme and delays the assessments that matter.
  • No link to the service. If you cannot say which of your services a supplier supports, you cannot judge significance during an incident or justify the tier.
  • Point-in-time only. Article 21(3) speaks in the present tense about the quality of a supplier's practices. A 2024 assessment does not describe 2026.
  • No evidence trail. The assessment that cannot be produced with its date, author and inputs is, for supervisory purposes, an assessment that did not happen.

What good looks like

  • A complete supplier inventory, reconciled against accounts payable and against your identity system, so it reflects who is actually paid and who actually has access.
  • Written tiering criteria, applied consistently, with the tier recorded per supplier.
  • Assessments dated, owned and versioned, with the evidence attached rather than referenced.
  • Continuous signals — sanctions, adverse media, breach and stability data — refreshed between assessments rather than only at review time.
  • A remediation log: findings, owner, due date, status.
  • A single view you can hand to an auditor without assembling it first.

That last point is the difference between a programme and a project. How Vendorapp supports NIS2 supply chain requirements covers how the platform maps onto this.

Frequently asked questions

Does NIS2 require vendor risk assessments?
Yes. Article 21(2)(d) makes supply chain security one of the ten minimum measures, and Article 21(3) requires entities to take into account the specific vulnerabilities of each direct supplier and service provider and the overall quality of their products and cybersecurity practices.
Does NIS2 say how to assess suppliers?
No. The directive sets the objective, not the method. It requires measures that are appropriate and proportionate to your exposure, size and risk, which means a risk-tiered approach where critical suppliers get deeper scrutiny than low-impact ones.
Do I have to assess every supplier under NIS2?
You must be able to justify your treatment of every supplier, which means every supplier needs at least a recorded triage decision. Depth then scales with risk — full assessment for suppliers with system access or critical dependency, light-touch for the rest.
Do sub-suppliers count under NIS2?
Article 21(2)(d) is framed around direct suppliers and service providers. Fourth parties are not directly in scope, but where a critical dependency sits behind a direct supplier you are expected to understand it, typically by requiring the direct supplier to manage and disclose its own supply chain.