vendorapp logo

Docs

NIS2 supply chain compliance checklist


Short answer. Work in this order: confirm scope and governance, build a complete supplier register, tier it against written criteria, assess suppliers proportionately, remediate contracts, add continuous monitoring, rehearse incident notification, then make the evidence retrievable. The register is the dependency for everything else.

Last reviewed: 31 July 2026.

The checklist in short

#ItemDone when
1Scope confirmed per legal entity and member stateWritten, dated scoping decision exists
2Supply chain security policy approvedManagement-body approval recorded
3Supplier register completeReconciled against AP and identity provider
4Tiering criteria written and appliedEvery supplier has a tier traceable to criteria
5Critical suppliers assessedDated assessments with evidence attached
6Contract terms remediatedClause coverage reportable across the estate
7Continuous monitoring liveScreening runs between reviews, with alerting
8Incident path testedSupplier windows contractual, filing rehearsed
9Governance operatingBoard pack, metrics, remediation log
10Evidence retrievableFour artefacts producible within days

Scope and governance

  • Determine which legal entities are in scope, in which member states, in which category. Record the reasoning and the date. See Who does NIS2 apply to?
  • Register with each relevant competent authority; record registration references and the responsible owner.
  • Write a supply chain security policy — scope, roles, tiering criteria, assessment method, cadence, contract standards, escalation.
  • Get it approved by the management body and minute the approval. Article 20 requires approval, not awareness.
  • Name an accountable executive and a per-supplier ownership model.
  • Add supply chain to the board reporting cycle. See What NIS2 requires of directors.

Build the supplier register

  • Consolidate sources: procurement, accounts payable, contract repository, identity provider, network and firewall records, business-unit shadow spend.
  • Capture per supplier: legal entity, ownership and jurisdiction, internal owner, service(s) supported, data categories held, access type, contract reference and renewal date, criticality inputs, substitutability.
  • Reconcile — anyone paid but not listed, and anyone with an account but not listed, is a gap.
  • Include intra-group service providers and contractors procured through suppliers.
  • Set an ongoing intake process so new suppliers land in the register at onboarding, not at audit. Detail: How to build a NIS2 vendor register.

Tier the register

  • Write objective criteria — access, data sensitivity, service dependency, substitutability, concentration.
  • Apply them consistently and record the resulting tier per supplier.
  • Identify concentration: shared platforms sitting behind multiple suppliers.
  • Flag suppliers supporting in-scope services specifically — these carry your reporting exposure.
  • Define the re-tiering trigger, and make change of access or scope one of them.

Assess suppliers

  • Build tiered questionnaires mapped to Article 21(2). See NIS2 supplier questionnaire.
  • Assess all critical suppliers first; do not run the estate in alphabetical order.
  • Validate certifications against their scope statements, not their existence.
  • Screen every supplier for sanctions and adverse signals independently of what they tell you.
  • Record each assessment with date, author, inputs and conclusion.
  • Log findings as tracked actions with owner and due date — not comments in a spreadsheet.
  • Record risk acceptances with a named accepter, rationale, compensating controls and a review date.

Remediate contracts

  • Inventory in-force contracts and identify which contain security, notification, audit, subcontracting and exit terms.
  • Determine the notification window in each critical supplier contract — this is the clause that determines whether you can meet your own 24-hour deadline.
  • Draft one security schedule with tiered annexes.
  • Addendum for critical suppliers now; renewal-triggered updates for the rest.
  • Track coverage as a reportable metric. See What contract clauses does NIS2 require with suppliers?

Monitor continuously

  • Continuous sanctions and watchlist screening, with alerting on new hits.
  • Ownership and corporate-change monitoring for critical suppliers.
  • Financial stability signals for continuity-critical suppliers.
  • Breach and adverse-media monitoring.
  • Defined reassessment cadence with automated reminders and visible overdue state. See How often do you have to reassess suppliers?

Incident readiness

  • Contractual supplier notification windows shorter than your regulatory deadline.
  • A monitored channel for supplier notifications, tested annually.
  • Supplier-to-service mapping usable under pressure, so significance can be judged fast.
  • Named filers and deputies for the 24-hour early warning, with out-of-hours cover.
  • Pre-written 24-hour and 72-hour templates, and registered access to the national portal.
  • At least one rehearsal per year of a supplier-origin scenario.
  • A timestamp log capturing when you were told, when you became aware, and when you filed. See NIS2 incident reporting timelines.

Evidence and reporting

  • Assessments, contracts, screening history and remediation actions held in a system of record rather than personal drives.
  • A standing management-body report: coverage, overdue assessments, contract clause coverage, open high-risk findings, supplier incidents.
  • Article 21(2)(f) effectiveness testing performed on the supply chain controls themselves, with findings tracked.
  • The four-artefact test: could you produce policy, register, four named suppliers' assessments and their contracts within a few days? See What supply chain evidence do regulators expect?

A realistic sequence

For an organisation starting from a spreadsheet:

PhaseWeeksFocus
11–3Scope decision, policy draft, register consolidation
23–6Register reconciliation, tiering criteria, tier assignment
35–12Critical supplier assessments; screening switched on across the estate
48–16Contract inventory, clause gap analysis, critical addenda issued
510–20Monitoring, alerting, cadence automation, incident rehearsal
6OngoingBoard reporting, effectiveness testing, renewal-driven remediation

Phases overlap. The critical path runs through phases 3 and 4, because both depend on third parties responding to you — which is why register work should never be allowed to expand into the time those need.