vendorapp logo

Docs

How to build a NIS2 vendor register


Short answer. Capture every direct supplier with its legal entity, internal owner, the services it supports, the data and access it holds, its tier, contract reference and assessment status — then reconcile that list against accounts payable, your identity provider and network records. The register is the dependency for every other supply chain control.

Last reviewed: 31 July 2026.

Why the register comes first

You cannot assess suppliers you have not listed, contract-remediate agreements you cannot find, or judge the significance of a supplier incident when you do not know which of your services depend on that supplier.

NIS2 never uses the word "register", but Article 21(2)(d) is framed around "each entity and its direct suppliers", and Commission Implementing Regulation (EU) 2024/2690 requires a directory of direct suppliers and service providers for the digital entities it covers. Every supervisory conversation in practice opens with a request for the list.

What fields to capture

FieldWhy it matters
Legal entity name and identifierAssessments and screening need the entity, not the brand
Ultimate parent and ownershipOwnership change is a reassessment trigger; jurisdiction is a risk factor
Country of establishment and of service deliveryJurisdiction and data location exposure
Internal ownerSomeone has to answer for the relationship
Services supportedTurns a supplier incident into a significance judgement in minutes
Supports an in-scope service?Determines your reporting exposure
Data categories heldSensitivity, and the GDPR overlap
Access typeNone / data only / network access / privileged access
Criticality tierDrives assessment depth and cadence
Substitutability and switching timeContinuity exposure
Contract reference, term, renewal dateDrives remediation sequencing
Key contract termsNotification window, audit rights, subcontracting, exit
Assessment date, author, outcomeThe Article 21(3) evidence
Screening statusSanctions and adverse signals
Open findings and due datesThe remediation trail
Subcontractors material to your serviceFourth-party visibility for critical suppliers

Two fields carry disproportionate weight: services supported and access type. Registers that omit them look complete and answer nothing useful during an incident.

Where to find your suppliers

No single system holds them all:

  • Accounts payable — the most complete list of who you actually pay. Start here, not with the procurement system.
  • Procurement and contract repository — terms and owners, but usually missing low-value and card spend.
  • Identity provider — external accounts, guest identities, federated access. This finds suppliers nobody purchased.
  • Network, VPN and firewall records — who actually connects, including maintenance and OT vendors.
  • Cloud tenant admin — connected applications, OAuth grants and API integrations.
  • Expense and card data — the SaaS bought on a card that now holds customer data.
  • DPA and processor register — a subset, not the whole (see NIS2 vs GDPR).
  • Business-unit interviews — the last resort, and reliably the source of the most surprising entries.

The reconciliation step

This is the step that separates a real register from a plausible one. Take three independent sources — paid, has an account, connects — and diff them against the register.

Every discrepancy resolves into one of three outcomes:

  1. Add to the register — a genuine supplier that was missing.
  2. Record a triage decision — a counterparty with no security relevance, with the reasoning captured. See the scoping test.
  3. Remove the access — an account or connection nobody can account for. This finding alone usually justifies the exercise.

Repeat the reconciliation at least annually, and report the drift. A register that never gains or loses entries is not being maintained.

Deciding what belongs in the register

Include every counterparty with a direct paid relationship, then mark each as in or out of security scope using the criteria in Who counts as a direct supplier under NIS2?.

Do not pre-filter. A register that only lists security-relevant suppliers cannot answer "why isn't this supplier assessed?", because the supplier is not there at all. Recording the exclusion is the point.

Keeping it current

Registers decay fastest at three moments:

  • Onboarding. If a supplier can be paid before appearing in the register, the register will always trail reality. Tie creation to procurement or payment setup.
  • Change. New integration, new data, new access, new subcontractor, change of ownership. Each needs a route back into the record.
  • Offboarding. Terminated suppliers whose access, data and integrations were never revoked are a live risk and an audit finding. Treat exit as a process with evidence, not an invoice stopping.

Assign an internal owner per supplier and make ownership transfer part of leaver handling. Unowned entries are the ones that go stale.

Spreadsheet versus system of record

A spreadsheet is a reasonable way to start and a poor way to continue. Three specific failures:

  • No history. You cannot show what you knew on a given date, which is exactly what a supervisor asks after an incident.
  • No enforcement. Nothing prevents blank fields, stale dates or duplicate entities.
  • No alerting. Overdue assessments and new sanctions hits do not announce themselves.

The threshold is usually somewhere between 50 and 100 suppliers, or the first time someone asks for evidence with a deadline attached.

Building it in Vendorapp

Mapping the register model onto the product:

  • Add vendors individually or in bulk; pre-screening runs on addition, so entity resolution and sanctions screening happen at intake rather than as a later task — see adding vendors.
  • Tri-risk ratings provide the exposure, ESG and access dimensions that feed tiering rather than replacing your own criteria — see tri-risk ratings.
  • Vendor view holds the per-supplier record — assessments, contracts, contacts, breaches and notes in one place, which is the artefact a supervisor is actually asking for. See understanding the vendor view.
  • Contracts attach to the vendor record with their terms captured, which is what makes clause coverage reportable across the estate — see adding and managing contracts.
  • Stakeholders record the internal owner per vendor — see adding and managing stakeholders.
  • Breaches capture supplier incident history against the record — see adding and managing breaches.
  • Alerts and notifications drive the cadence and surface changes between reviews — see managing alerts and notifications.
  • Reports turn the register into the coverage and status views the management body needs — see understanding reports.

More on the mapping: How Vendorapp supports NIS2 supply chain requirements.