SDG data protection blog

Laws & regulationIT security

NIS2 and the Supply Chain: Obligations, Contracts and Suppliers

20 October 2026 by Sebastian Baier · Reading time approx. 10 minutes

Under Section 30 (2) No. 4 BSIG (the BSI Act), particularly important and important entities must manage the security of their supply chain, including the security-related aspects of their relationships with their direct suppliers and service providers. Suppliers that do not fall under NIS2 themselves have no obligations of their own under the BSIG. However, they feel the requirements through their customers' contracts, questionnaires and audits.

This article shows what regulated entities have to do with regard to suppliers, what belongs in contracts and how suppliers can prepare. You will find an overview of all NIS2 obligations on the page NIS2 consulting.

What the law requires

Section 30 (1) BSIG obliges entities to take appropriate, proportionate and effective technical and organisational measures. Subsection (2) lists ten minimum areas. Number 4 is supply chain security, including security-related aspects of the relationships with direct suppliers or service providers.

The NIS2 Directive specifies this in Art. 21 (3) of Directive (EU) 2022/2555. According to it, entities should take into account in particular:

Aspect What this means in practice
vulnerabilities specific to each supplier Where can a supplier put your company at risk, for example through remote access or software updates?
overall quality of products and cybersecurity practices How securely does the supplier work, for example with regard to patches and access rights?
secure development procedures Does the supplier develop software according to recognised security principles?
results of coordinated EU risk assessments Are there EU-level assessments of critical supply chains that affect you?

Like the other measures, supply chain measures must be documented. For certain digital providers such as cloud services, data centres and managed service providers, Implementing Regulation (EU) 2024/2690 also applies, with specific requirements, including a register of suppliers and service providers.

The BSI (Federal Office for Information Security) points to the SolarWinds attack of 2020. In that attack, attackers used a manipulated software update to plant a backdoor in the systems of many customers. Attacks like this target the weakest link in the chain.

Only direct suppliers or the whole chain?

The legal obligation relates to direct suppliers and service providers. The BSI makes clear that the BSIG does not indirectly impose obligations on all suppliers.

Nevertheless, the risk does not end with your direct contractual partner. Your IT service provider itself uses cloud services and software from other providers. The BSI therefore recommends understanding the entire supply chain, including sub-suppliers, in line with cyber supply chain risk management (C-SCRM). In practice, you deal with this through contracts: you require your direct supplier to manage its own subcontractors appropriately.

Level Basis Typical means
direct suppliers and service providers legal obligation under Section 30 (2) No. 4 BSIG assessment, contract, review
sub-suppliers risk management, passing on obligations by contract subcontracting clauses, transparency about the service providers used

Supplier management in five steps

Important: who is responsible?

Setting up and running supplier management is not a task of the ISMS, but of the organisation itself, for example purchasing or the business units that select and manage suppliers. The information security officer and the ISMS coordinator play a supporting role: they contribute the requirements from ISO 27001, NIS2 or KRITIS and check whether they have been implemented.

The BSI describes five steps for C-SCRM. We translate them into the practice of a medium-sized company:

  1. Identify Who is involved in your supply chain? Create a register of all suppliers and service providers with access to your systems, data or premises, or that are important to your operations. Commonly forgotten are maintenance access for machine manufacturers, software as a service and cleaning or security services with access to the building.
  2. Develop rules Define which security requirements apply to which group of suppliers. Not every supplier needs the same depth of review.
  3. Know what you buy Which IT systems, software and services come from whom? You also need this information to respond quickly when a vulnerability becomes known.
  4. Understand dependencies Which suppliers do critical processes depend on, and are there alternatives? Where are sub-suppliers involved?
  5. Assess effectiveness Review suppliers regularly, for example via certificates, questionnaires, evidence or audits, and practise emergencies together with critical suppliers.

A simple criticality assessment has proved effective for classification:

Criticality Characteristics Appropriate depth of review
high privileged access to systems or sensitive data, failure stops critical processes evidence of an ISMS (for example ISO 27001 with a suitable scope), detailed contractual provisions, regular review, audit if necessary
medium limited access, failure with fallback options questionnaire, contract clauses, review at fixed intervals
low no access to systems or data, easily replaceable basic requirements in the contract

With certificates, pay attention to the scope: an ISO 27001 certificate only helps if it covers the services you buy. More on this in the article ISO 27001 certification.

What belongs in contracts with suppliers

The BSI recommends service level agreements that cover risk management measures, handling of security incidents and patch management. Suppliers should also be committed to security by design and security by default. This results in typical points to be covered:

Point to cover Example
Level of security commitment to appropriate technical and organisational measures, where applicable to a standard such as ISO 27001
Reporting incidents information without undue delay about security incidents affecting your data or services, so that you can meet your own deadlines under Section 32 BSIG
Vulnerabilities and patches deadlines for security updates, information about known vulnerabilities
Access rules for remote access, personal accounts, multi-factor authentication, logging
Subcontractors information or consent in the event of subcontracting, passing on obligations
Evidence and audit rights provision of certificates or reports, right to questionnaires or audits
Emergencies and exit cooperation in an emergency, return and deletion of data, handover at the end of the contract

Coordination is particularly important for incident reporting. If your service provider learns of an attack, your own 24-hour deadline only starts once you become aware of it. Without a clear reporting obligation in the contract, you may find out too late. More on the deadlines in the article NIS2 reporting obligations.

You do not have to renegotiate all existing contracts at once. Start with the critical suppliers and use contract renewals and new contracts.

What NIS2 means for unregulated suppliers

Many medium-sized companies do not fall under NIS2 themselves, but supply regulated customers. You can clarify whether your company is affected itself with the NIS2 applicability assessment. For the others: the BSIG does not impose obligations on you directly. However, the BSI points out that regulated entities can no longer work with certain companies without breaching their own obligations. This makes it a commercial question too.

Typical requirements that reach suppliers:

  • security questionnaires from customers, often with questions about ISMS, backup, access protection and emergency planning
  • contract clauses on reporting obligations, patches and audit rights
  • requests for certificates, frequently ISO 27001
  • audits by customers for critical services

How to prepare:

  1. Clarify which of your customers fall under NIS2 or KRITIS themselves.
  2. Determine where you stand with a gap analysis against the common requirements.
  3. Build the foundations: responsibilities, access protection, backup, incident process, emergency planning.
  4. Keep evidence ready so that you can answer questionnaires quickly and consistently.
  5. Check whether an ISMS based on ISO 27001 makes sense for you. A certificate answers many customer enquiries at once.

If you are well prepared, you can use security as a sales argument instead of handling every customer enquiry individually.

ISO 27001, data protection and the CRA: what you can combine

Topic Link to the supply chain
ISO/IEC 27001:2022 Annex A contains controls on supplier relationships (A.5.19 to A.5.22), cloud services (A.5.23) and outsourced development (A.8.30). In this way the ISMS brings the security requirements into supplier management; the organisation itself must set it up and run it, see NIS2 and ISO 27001.
Commissioned data processing under Art. 28 GDPR Many service providers also process personal data. Review, contract and monitoring can be combined with the supplier assessment, see commissioned data processing under Art. 28 GDPR.
Cyber Resilience Act Manufacturers of products with digital elements will have to meet security requirements and handle vulnerabilities. This makes it easier to assess purchased products, but does not replace the assessment, see CRA: obligations for manufacturers.

The NIS2 checklist gives an overview of all ten areas of measures.

How SDG supports you

  • Security requirements for your supplier management: criteria for the supplier register, criticality assessment, review procedures and documentation, which your organisation implements; we provide advice, while setting up and running it remains with you
  • Contract requirements: security and reporting clauses for supplier contracts, aligned with commissioned data processing
  • For suppliers: gap analysis against customer requirements and support with answering security questionnaires
  • ISMS based on ISO 27001 that sets the security requirements for suppliers and serves as evidence for customers
  • External information security officer for ongoing support: external information security officer

Frequently asked questions about the NIS2 supply chain

What does NIS2 require regarding the supply chain?

Under Section 30 (2) No. 4 BSIG, particularly important and important entities must ensure the security of their supply chain, including the security-related aspects of the relationships with direct suppliers and service providers. This includes assessing suppliers, contractual provisions and reviewing them.

Does the obligation apply to all suppliers in the chain?

The legal obligation relates to direct suppliers and service providers. However, the BSI recommends understanding the entire supply chain, including sub-suppliers. In practice, this is dealt with through subcontracting clauses in contracts.

As a supplier, do I have to implement NIS2 if my company is not affected?

No, the BSIG does not impose obligations directly on suppliers that are not affected. However, regulated customers pass on their requirements through contracts, questionnaires and audits. Suppliers that do not meet them risk losing orders.

What belongs in a contract with a service provider?

Typical provisions cover the level of security, reporting incidents without undue delay, patches and vulnerabilities, access, subcontractors, evidence and audit rights, as well as emergencies and the end of the contract.

Is a supplier's ISO 27001 certificate sufficient as evidence?

A certificate is strong evidence if its scope covers the services you buy. Check the scope and validity. It does not replace contractual provisions, for example on incident reporting.

How often should suppliers be reviewed?

The law does not specify a fixed interval. A review based on criticality makes sense: critical suppliers regularly and in the event of significant changes, less critical ones at longer intervals.

How are supplier management and commissioned data processing related?

Many service providers also process personal data and need a contract under Art. 28 GDPR. Review, contract and monitoring can be combined with the NIS2 supplier assessment in one process.

Sources: Section 30 BSIG, Directive (EU) 2022/2555 (NIS2), BSI: NIS2 and a secure supply chain, Implementing Regulation (EU) 2024/2690

Note: This article provides general information and does not replace legal advice in individual cases.