vendorapp logo

Docs

How Vendorapp supports NIS2 supply chain requirements


Short answer. Vendorapp addresses the supply chain measure — Article 21(2)(d) — rather than NIS2 as a whole. It holds the vendor register, runs sanctions screening and risk ratings at intake, keeps assessments and evidence against each vendor record, tracks contracts and their terms, and surfaces change through alerts and reports.

Last reviewed: 31 July 2026.

What Vendorapp does for NIS

NIS2 has ten minimum measures. Vendorapp is a vendor and supplier risk management platform, so it is relevant to one of them in depth — supply chain security — and contributes evidence to two others: effectiveness assessment under (f), and incident handling under (b) where a supplier is involved.

That is a deliberate scope statement, not modesty. Tools that claim to deliver "NIS2 compliance" wholesale tend to be weakest exactly where the obligation is hardest: the per-supplier, evidenced, current record that Article 21(3) requires.

Mapping the obligation to the product

NIS2 requirementWhat it needs in practiceVendorapp capability
Article 21(2)(d) — relationships with each direct supplierA complete, current supplier inventory linked to services, data and accessVendor register with per-vendor record, stakeholders and vendor view
Article 21(3) — vulnerabilities specific to each supplierPer-supplier assessment with dated evidenceAssessments and ad-hoc assessments held against the vendor
Article 21(3) — quality of products and cybersecurity practicesIndependent signals, not only self-reported answersSanctions screening, tri-risk ratings, breach records
Article 22 — non-technical risk factorsEntity, ownership and jurisdiction factsVendor intelligence and pre-screening at intake
Contractual security termsKnowing which contracts contain which obligationsContract records against the vendor
Ongoing managementCadence, change detection, overdue visibilityAlerts and notifications
Evidence for supervisionRetrievable artefacts with dates and ownersVendor view and reporting

The vendor register

The register is the dependency for everything else — see How to build a NIS2 vendor register.

  • Adding vendors — vendors are matched and pre-screened as they are added, so entity resolution and screening happen at intake rather than as a later cleanup exercise.
  • Understanding the vendor view — the per-vendor record that consolidates ratings, assessments, contracts, contacts, breaches and notes. This is the artefact a supervisor is asking for when they say "show us this supplier".
  • Adding and managing stakeholders — records the internal owner, without which entries go stale.
  • Adding and managing contacts and addresses — the supplier-side contacts your incident notification path depends on.

Assessment and risk rating

  • Tri-risk ratings — exposure, ESG and access dimensions generated automatically. Use them as inputs to your tiering criteria, not as a replacement for criteria you wrote down. A supervisor will ask how the tier was decided, and "the tool said so" is a weak answer; "our criteria weight access and service dependency, informed by the access rating" is not.
  • Perform ad-hoc assessments — for event-driven reassessment after an incident, an ownership change or a change in your dependency. See the trigger list.
  • Global sanctions screening — independent screening against consolidated lists, with outcomes recorded against the vendor.
  • Vendorapp Intelligence — the automation layer running screening and scoring across the lifecycle.
  • Adding and managing notes — where adjudication reasoning and risk-acceptance rationale belong, so decisions are attributable rather than remembered.

Contracts and clause coverage

Contract remediation is the slowest part of most NIS2 supply chain programmes, and the bottleneck is nearly always discovery: nobody can say which agreements contain a security schedule or what notification window they promise without opening every document.

Adding and managing contracts attaches contracts to the vendor record with their key terms captured, which turns questions like "which critical suppliers lack a 24-hour notification obligation" from a project into a query. The clause set to look for is in What contract clauses does NIS2 require with suppliers?

Monitoring between reviews

Periodic assessment leaves gaps that incidents happily occupy.

Evidence and reporting

Understanding reports covers the reporting views. For NIS2 purposes the ones that matter are coverage and currency: how many vendors are assessed, how many assessments are overdue, where the open findings sit.

That is also the substance of the management-body pack Article 20 oversight requires — see What NIS2 requires of directors — and it maps directly onto the artefacts described in What supply chain evidence do regulators expect?

What Vendorapp does not do

Being explicit is more useful than a capability matrix with no gaps in it:

  • It does not determine your NIS2 scope. Whether you are an essential entity in a given member state is a legal analysis. See Who does NIS2 apply to?
  • It does not file your incident reports. The 24-hour early warning goes to your national CSIRT through their channel. Vendorapp holds the supplier-side facts and timeline that feed it.
  • It does not cover the other nine measures. Cryptography, MFA, backup, cyber hygiene and the rest are your own environment's controls.
  • It does not write your policies. The supply chain security policy, the tiering criteria and the risk acceptance framework are yours; the platform records their operation.
  • It is not legal advice, and neither is this learning centre.

Getting started

  1. Work through the NIS2 supply chain compliance checklist to sequence the programme.
  2. Load and reconcile the register — how to build a NIS2 vendor register.
  3. Assess critical suppliers first, using the NIS2 supplier questionnaire.
  4. Attach contracts and identify clause gaps.
  5. Turn on alerting, set the cadence, and put coverage in front of the management body.

New to the product? Start with the Vendorapp overview and types of users.