vendorapp logo

Docs

Who counts as a direct supplier under NIS2?


Short answer. A direct supplier is any party you contract with directly whose products or services touch the security of your network and information systems. That is broader than "IT vendors": it includes cloud and software providers, MSPs, contractors, hardware suppliers, and non-IT suppliers with physical or logical access to your environment or data.

Last reviewed: 31 July 2026.

Who counts as a direct supplier

Article 21(2)(d) covers "direct suppliers or service providers". The directive does not define the term further, which leaves two boundaries to draw: how far down the chain (direct), and how far across the category (relevant to security).

The first is straightforward. The second is where most scoping arguments happen.

What direct means

Direct means first tier — you have a contractual relationship with them. Your cloud provider is direct. Your cloud provider's data centre landlord is not.

That is a genuine limit, and it is deliberate: the drafters chose a perimeter entities could actually control. It is not, however, permission to be incurious about what lies behind a critical direct supplier. See sub-suppliers and fourth parties below.

Suppliers people forget

Registers assembled from the IT budget miss a predictable set of relationships:

  • Contractors and staff augmentation — individuals with the same access as employees, procured through a supplier, and often absent from both HR systems and the vendor list.
  • Professional services — auditors, law firms and consultancies holding sensitive documents and, sometimes, production data extracts.
  • Maintenance and support vendors — OT and building systems engineers with remote access into networks nobody maps.
  • Facilities, cleaning and security — physical access to server rooms and desks. NIS2's all-hazards framing puts physical access squarely inside the security relationship.
  • Logistics and couriers — custody of devices and media in transit.
  • Payroll, benefits and HR platforms — large volumes of personal data, procured outside IT.
  • Marketing and analytics SaaS — bought on a card, connected by API, never reviewed.
  • Certificate authorities, DNS registrars and payment providers — small spend, enormous blast radius.
  • AI and model providers — increasingly reached through an existing product rather than a separate contract; the security relationship changes even where the paper does not.

The reliable way to find these is to reconcile the supplier list against three independent sources: accounts payable, the identity provider (who actually has an account), and network or firewall records (who actually connects).

Where to draw the line

Not every counterparty is a security-relevant supplier. A supplier belongs in scope for Article 21(2)(d) if any of the following is true:

  1. They hold, process or can reach your data — including backups and test extracts.
  2. They have logical access to your systems — accounts, API keys, VPN, remote support tooling, or an integration.
  3. They have physical access to premises, equipment or media.
  4. They supply or maintain a component of a system supporting an in-scope service — software, hardware, firmware, OT.
  5. Their failure would materially disrupt one of your services, regardless of access.

If none applies, record the triage decision and move on. That record is the answer to "why isn't this supplier assessed?".

What about sub-suppliers and fourth parties

The obligation is framed at the first tier, but concentration risk is not. Three practices bridge the gap without pretending to assess the whole chain:

  • Contractual flow-down. Require direct suppliers to impose equivalent security obligations on subcontractors, to maintain their own supplier security programme, and to notify you of material changes in subcontracting. This is standard in the Implementing Regulation (EU) 2024/2690 pattern.
  • Disclosure for critical services. For critical suppliers, require a current list of subprocessors or subcontractors material to your service, with notice of change.
  • Concentration analysis. Look across your register for the shared dependency — the single hyperscaler, identity provider or payment processor sitting behind a dozen "independent" suppliers. A supplier-by-supplier view will never surface it.

Group companies and intra-group services

Shared service centres, group IT, and offshore development entities are service providers to the in-scope entity in substance, even when the paperwork is thin or absent.

Treat them as suppliers for assessment purposes: same tiering, same evidence, same expectations for access control and incident notification. Where intra-group arrangements are governed by service-level documents rather than contracts, make sure those documents carry the security and notification obligations you would demand of a third party.

A practical scoping test

For each counterparty, answer five questions and record the answers:

  1. Do we have a direct contract or paid relationship with them?
  2. Can they reach our data or systems — logically or physically?
  3. Which of our services would degrade if they failed, and how quickly?
  4. Are they readily substitutable, and how long would substitution take?
  5. Do they sit behind, or in front of, a concentration we already carry?

Answers to 2–5 give you the tier. Question 1 tells you whether the obligation is yours directly or belongs to your supplier's own programme.

Next: What contract clauses does NIS2 require with suppliers?

Frequently asked questions

Who counts as a direct supplier under NIS2?
Any party you contract with directly whose products or services are relevant to the security of your network and information systems — software and cloud vendors, managed service providers, contractors, hardware suppliers, and non-IT suppliers that hold data or have physical or logical access.
Are sub-suppliers covered by NIS2?
Article 21(2)(d) is framed around direct suppliers and service providers, so fourth parties are not directly in scope. Where a critical dependency sits behind a direct supplier, the expectation is that you require that supplier to manage and disclose its own supply chain.
Do non-IT suppliers count under NIS2?
They can. NIS2 requires an all-hazards approach covering physical and environmental factors, so a facilities, cleaning, maintenance or logistics provider with physical access to your sites or equipment is in scope of the security relationship.
Do intra-group service providers count?
Yes, in substance. A shared services company or group IT function providing services to an in-scope entity is a service provider to that entity. Many supervisors expect the relationship to be governed and evidenced, even where no arms-length contract exists.