Skip to main content

Guide

NIS2 supply chain security: Assess suppliers and address risks

Implement NIS2 supply chain security: identify critical providers, assess evidence, review contracts and follow up findings.

Benjamin Schatter
|Updated|Read time: 5 minutes

A provider outage becomes your problem when orders stop arriving, production systems halt or customer data becomes inaccessible. NIS2 supply chain security therefore starts with a question: Who do our operations depend on, and how do we manage those risks?

This guide explains the requirements in Germany and a practical workflow for supplier assessment, contract review and follow-up. Legal position: 12 November 2026.

What does NIS2 require for supply chains?

Section 30(2), point 4 BSIG includes supply chain security in risk management measures, covering security aspects of relationships with direct suppliers and service providers. Measures must be appropriate, proportionate and effective overall, and implementation must be documented.

This does not mean every supplier becomes directly regulated by NIS2 because you are affected. Nor does every supplier require the same certificate, questionnaire or annual on-site audit. Assess the significance of the relationship and the specific risks.

Article 21(2) and (3) of the NIS2 Directive addresses supplier-specific vulnerabilities and the quality of security practices, among other factors. Certain digital services face additional technical and methodological requirements. Check those separately for your entity type.

1. Make dependencies visible

Start with services and processes essential to your operations. Associate suppliers, purchased services and affected systems with them. A contract register alone does not show the consequences of a disruption.

For example, your customer portal runs with a hosting provider, while login depends on an identity service. Even if hosting remains available, customers can be locked out when the identity service fails. Include this dependency in the assessment.

Initially record:

  • supplier, service and internal owner;
  • supported business processes and systems;
  • access to information and administrative permissions;
  • known subcontractors and significant further dependencies;
  • available alternatives and potential outage consequences.

Subcontractors can affect the assessment even if your contract is with the direct provider. Determine what information you need from that provider to understand the risk.

2. Prioritise suppliers by risk

Do not assess only the purchase value. An inexpensive service with extensive system access can be more critical than a costly supplier without access to your operations.

Assessment questionWhy it matters
Which services stop during an outage?Reveals operational impact
Which data and permissions are involved?Shows potential confidentiality and integrity damage
How quickly can the service be replaced?Helps assess dependency and available options
Which subcontractors are shared?Can reveal concentration risk
Which incidents or unresolved findings are known?Prevents reliance on self-assessment alone

You could use internal categories such as “critical”, “elevated” and “normal”. These are your assessment method, not statutory NIS2 tiers. Record the reasoning and use it to determine review depth and frequency.

3. Assess evidence rather than just collecting it

A certificate helps when it covers the relevant service and scope. Check validity, exclusions and unresolved findings. A certificate for another company or an unused service may not answer your question.

Depending on risk, supplement it with information on access management, recovery, vulnerability handling and incident communication. A suitable assurance report may be relevant for a cloud service. What matters is what it actually establishes for your use.

The supplier audit and evidence guide explores this further. Reusable questionnaires help with comparable services; additional questions remain necessary when your use introduces specific risks.

4. Seven topics for contract review

These are questions for suitable agreements, not a legally prescribed set of seven standard clauses.

TopicWhat to agree or clarify
Security levelSpecific requirements, relevant evidence and treatment of deviations
Incident informationOwners, contact channels and sufficiently early information to meet your own duties
Review rightsInformation, reports or audits appropriate to the risk and service model
SubcontractorsTransparency, changes and passing on relevant security requirements
Data and locationsPermitted processing, access and any separate data protection requirements
Business continuityRecovery, emergency cooperation and necessary testing
Termination and switchingData return, deletion, transition support and removal of access

A blanket 24-hour supplier notification period is not automatically the right contractual solution. Your own NIS2 reporting deadlines run from awareness of a significant incident. You need enough time and information for assessment and reporting; specific contracts may therefore require earlier information and continuing updates.

Our sample clauses PDF offers a starting point for contract work. It contains negotiation examples that must be adapted to the service, risk and legal position before use. Certification, review frequency and data location must not be inferred as blanket NIS2 requirements from the examples.

5. Turn findings into decisions

What happens when recovery evidence is missing or a provider does not meet an important security requirement? Record the gap, its impact and your decision. Options include requesting evidence, adding safeguards, time-limited acceptance or seeking an alternative.

A reasoned decision identifies its owner, rationale, deadline and reassessment conditions. “Supplier approved” without this basis does little to help procurement or management respond to later changes.

Kopexa supplier management helps keep assessments, evidence and outstanding work together. Missing evidence remains a task requiring a verifiable result rather than being replaced by a green status label.

6. Track changes during operation

Assessments become outdated when certificates expire, services change or new subcontractors are introduced. Plan reviews according to criticality and respond to relevant events as well. A serious incident must not wait until the next routine review.

Review your own changes too: is the service now supporting more important processes? Has it gained additional access? Is the original alternative still available? These can change the risk even if the supplier offers the same service.

Start with one critical provider

Choose a provider whose outage would materially affect customers or production. Record the dependency, review one meaningful piece of evidence and identify the most important unanswered question. Establish who will answer it, by when and which decision depends on it.

This turns a collection of questionnaires into accountable risk treatment. The NIS2 requirements overview places supply chain work in context; Kopexa for NIS2 explains how to organise implementation together.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Which organisations must implement NIS2 supply chain security?

Section 30 BSIG includes relevant risk management measures for essential and important entities. Whether a supplier is directly in scope is separate from your requirements for the business relationship.

May I use the contract clause template commercially?

The Kopexa template uses CC-BY-4.0. Commercial use and adaptation are permitted under its conditions, including attribution, a licence reference and indication of changes. The licence does not replace review of the clauses for your situation.

Is a supplier’s ISO 27001 certificate enough?

A certificate can be relevant evidence. Check scope, service, validity and remaining risks. It does not automatically replace assessment of your specific dependency or suitable contractual agreements.

How often should critical suppliers be reviewed?

Set depth and frequency according to risk and specific applicable requirements. Section 30 does not impose annual on-site audits on every supplier. Relevant incidents or changes can trigger additional reviews.

Should providers outside the EU be included?

Your supply chain risk assessment does not stop at the EU border. Include relevant direct providers regardless of location and separately assess additional requirements, such as data protection.

What sanctions apply if supply chain security is missing?

A breach involving section 30 measures can fall under section 65 BSIG. The specific offence and entity type matter; the fine framework is not an automatic penalty.

Is the supplier automatically liable for an attack?

Claims against a supplier depend, among other things, on the contract and specific breach. Your own regulatory duties do not disappear because an incident starts at a provider.

How many suppliers must we assess?

Identify relationships relevant to your security risks and assess direct suppliers and service providers appropriately. Scope and depth follow risk, not a fixed percentage or universal tier classification.