Guide
Blog
Insights
17 November 2026

Which NIS2 clauses your supplier contracts need now

Which NIS2 clauses your supplier contracts need now

Reviewed by Sven Moritz, co-founder of GetTeddy · As of November 2026

An electronics manufacturer with 320 employees has been an important entity under NIS2 since December 2025. Its supplier list is in good shape: 140 entries, each with a contact and a risk rating. One of them is a service provider that maintains the control systems of the production lines through remote access. Its contract dates from 2019 and says one thing about security: the contractor works according to the state of the art. There is no duty to report security incidents, no audit right, and nothing about subcontractors.

If that provider is attacked on a Friday, the manufacturer may only find out on Monday, from the news. What it can then demand from the provider depends on the contract. Our guide to the German NIS2 Implementation Act covers the full set of obligations. This article covers the part that belongs in supplier contracts.

Key takeaways

  • NIS2 requires supply chain security, including the security aspects of relationships with direct suppliers or service providers. In Germany this is Section 30(2) no. 4 BSIG, based on Article 21(2)(d) of the directive.
  • The German act does not prescribe specific clauses. For cloud, data centre and managed service providers and some other digital providers, Implementing Regulation (EU) 2024/2690 does list what contracts should cover.
  • A supplier list tells you who supplies you. What the supplier has to do when something goes wrong is in the contract.
  • The supplier's notification duty should fit your own deadlines. You report significant incidents within 24 hours, 72 hours and one month.
  • Start with suppliers that have access to your systems or that your operations cannot run without.
  • Existing contracts rarely need renegotiating. An information security annex added by amendment usually covers what is needed.

What the law says about the supply chain

Section 30(1) BSIG requires particularly important and important entities to take appropriate, proportionate and effective technical and organisational measures. Section 30(2) lists ten areas those measures must cover at a minimum. Number 4 is supply chain security, expressly including relationships with direct suppliers or service providers. It transposes Article 21(2)(d) of the NIS2 Directive, Directive (EU) 2022/2555.

Article 21(3) is more specific. When deciding which supply chain measures are appropriate, entities take into account the vulnerabilities specific to each direct supplier, the overall quality of its products and its cybersecurity practices, including secure development procedures. They also have to consider the results of coordinated EU risk assessments of critical supply chains under Article 22(1). The German act does not repeat this paragraph word for word. It still describes quite precisely what a supplier assessment should look at, which makes it a useful yardstick.

The measures must be documented (Section 30(1) BSIG), and management must oversee their implementation (Section 38 BSIG).

The law has no model contract, no deadline for supplier incident reports and no duty to amend every running contract. Measures must be proportionate to risk exposure, size, cost and the likelihood and severity of incidents. Where this article suggests deadlines or wording, it is a recommendation and marked as one.

Digital providers get a more detailed list

For certain entities, the European Commission has set out the measures in Implementing Regulation (EU) 2024/2690. It covers DNS service providers, TLD registries, cloud computing providers, data centre providers, content delivery networks, managed service providers, managed security service providers, online marketplaces, online search engines, social networking platforms and trust service providers. In Germany, Section 30(3) BSIG gives it priority for these entities.

Point 5 of its annex deals with the supply chain. Under point 5.1.4, contracts with suppliers should, where appropriate, specify cybersecurity requirements, staff awareness, skills and training, background checks on staff, a duty to notify incidents without undue delay, a right to audit or to receive audit reports, a duty to handle vulnerabilities, requirements on subcontracting and obligations when the contract ends. Point 5.2 requires a register of direct suppliers with a contact point and the ICT products and services each provides, and point 5.1.6 a review at planned intervals.

For other entities the list is not binding, but it is the most precise official description of what a NIS2 supplier contract should cover. The clauses below follow it.

Why a supplier list is not enough

Many companies started their NIS2 supply chain security work with a supplier register and a questionnaire. Both are useful, but a questionnaire is a snapshot and binds the supplier to nothing. The contract sets out what the supplier owes you: when it reports, whom it may bring in, what you may check and what happens to your data when the contract ends. If it is not in there, you cannot demand it when it counts.

To the BSI or an auditor, an answered questionnaire shows an assessment. An agreed notification duty with a named contact point shows a measure. That is why contract review is a criterion of its own in our guide to choosing NIS2 software.

Eight clauses for your supplier contracts

1. Security requirements

“State of the art” is hard to check. An annex with minimum measures that fit the service works better: multi-factor authentication for any access to your systems, encryption, logging, backups with tested restores. Add how the supplier proves it, for example with an ISO 27001 certificate whose scope covers the service you buy, or a suitable TISAX® label.

2. Incident notification

The implementing regulation asks for a duty to notify, without undue delay, incidents that present a risk to your systems. Your own early warning to the BSI is due within 24 hours of becoming aware of a significant incident (Section 32 BSIG). On the wording of the law, your clock starts with your own awareness. A late message from the supplier still hurts: the later you hear, the longer an attacker may have had access to your systems.

Our recommendation: a fixed maximum time from the moment the supplier becomes aware, in hours, not days, for critical suppliers. Add a contact point on both sides that answers at weekends, a minimum content for the first message (what happened, which systems and data, known indicators of compromise) and follow-ups that let you write your 72-hour notification and final report. Where personal data is involved, Article 33(2) GDPR already requires the processor to inform you without undue delay, so you can meet your own 72-hour deadline towards the data protection authority.

3. Subcontractors

Set out whether and how the supplier may pass work on: with your prior consent, or with advance notice and a right to object. It has to pass the agreed security requirements down to its subcontractors and keep a current list. The GDPR uses the same mechanism in Article 28(2) and (4). One process for both saves you and the supplier from doing the work twice.

4. Audit and information rights

The implementing regulation names a right to audit or to receive audit reports. For most suppliers a tiered model works: current evidence each year, such as a certificate and statement of applicability or a SOC 2 report, answers to security questions within an agreed time, and an on-site audit with notice when there is a reason, such as an incident. For financial entities, DORA requires unrestricted audit rights where the service supports a critical or important function.

5. Vulnerability handling

The supplier should handle vulnerabilities that present a risk to you. In practice: it tells you about known vulnerabilities in what it delivers, fixes them within deadlines set by severity and provides security updates over the agreed lifetime. When it plans to end support, you hear in good time. Manufacturers of products with digital elements have also been subject to the Cyber Resilience Act reporting obligations since 11 September 2026.

6. Supplier staff

People with access to your systems should be trained and qualified for the job. The implementing regulation also mentions background checks. Employment and data protection law limit these in Germany and elsewhere, so oblige the supplier to carry out checks within what the law allows.

7. Location and data access

NIS2 says nothing specific here. We still recommend recording where your data is stored and processed, where remote access comes from, and that changes are announced in advance. For personal data, transfers to third countries fall under Articles 44 ff. GDPR, and DORA requires locations to be stated in every ICT contract.

8. Exit and return

When the contract ends, it should be clear in which format you get your data back, how long the supplier supports the transition, and when it deletes the data and confirms it. One point is often missing: every access the supplier has to your systems is removed when the contract ends.

DPA, DORA annex and NIS2 in one contract

Many supplier relationships already have a data processing agreement under Article 28 GDPR. If you sell to financial entities or are one, you will also know the DORA annex under Article 30 DORA, covered in our article on DORA for ICT service providers. The three overlap on subcontractors, audit rights, return and deletion, and incidents.

They differ in scope. A DPA covers personal data only. NIS2 covers the security of your systems as a whole, including a remote maintenance provider that never sees a customer address. So a DPA does not replace a security annex.

In practice, one information security annex works best. It sets out the security requirements, notification channels and audit rights once. The DPA refers to it for the technical and organisational measures under Article 32 GDPR, and so does a DORA annex. Keep deadlines and channels identical across all three, or you will argue about which one applies in the middle of an incident.

Which suppliers come first

Because measures have to be proportionate, you can prioritise. Four criteria help sort suppliers: access to your systems or network, how much your operations depend on them, the data they process and how quickly you could replace them.

The first three groups are usually a small part of the list and get the full annex. For groups 4 and 5, security requirements, incident notification and data return are often enough. Record each supplier's group with a short reason.

What to do with existing contracts

You do not need to terminate contracts or renegotiate everything. For most suppliers an amendment that brings in the information security annex is enough. Start with groups 1 to 3 and use occasions that come up anyway: a renewal, a price change, a new service.

Large providers with standard terms rarely negotiate. Map their terms, security documentation and audit reports to the eight clauses instead. Document the remaining gaps and compensate for them, for example with your own backups and an exit plan.

If a supplier refuses a clause, record the remaining risk, how you reduce it and who accepted it. For group 1 suppliers that decision should sit with management, which oversees implementation under Section 38 BSIG.

Where contract reviews go wrong

  • Questionnaire instead of contract. Answers describe a state of affairs. Obligations only come from the agreement.
  • The same full text for every supplier. An on-site audit right for the office supplies vendor uses up negotiation time you need for critical suppliers.
  • “Without undue delay” with no contact point. A duty to notify only helps if it is clear who receives the call on a Saturday.
  • Access outlives the contract. Remote maintenance accounts stay active because nobody tells IT the contract has ended.

Where to start

  1. Sort your supplier list using the four criteria above.
  2. Check the contracts in the first group against the eight clauses: present, partial, missing. Our supplier contract clause check (PDF) lists the checkpoints with their legal references.
  3. Draft an information security annex and agree it with your legal team or outside counsel.
  4. Send amendments group by group.
  5. Document results and open points and report them to management. Our NIS2 checklist shows where the supply chain sits in the wider programme.

At GetTeddy, contract analysis supports step two. It maps the clauses of a supplier contract to the requirements of Article 21(2)(d) NIS2, Article 28 GDPR and Article 30 DORA and rates each match on a scale of 1 to 5. Uncertain assessments go to an approver in your team. Negotiation and the legal assessment of disputed clauses stay with you and your lawyers. Our NIS2 page and the page for legal teams have more detail.

Frequently asked questions about NIS2 supply chain security

What does NIS2 require for supply chain security?

In Germany, Section 30(2) no. 4 BSIG covers this. Essential and important entities must include supply chain security in their risk management measures. This includes the security aspects of their relationships with direct suppliers or service providers. The source is Article 21(2)(d) of the NIS2 Directive (EU) 2022/2555.

Does the BSIG prescribe specific contract clauses?

No. The BSIG contains no model contract and no mandatory clauses. For cloud providers, data centres, managed service providers and some other digital providers, Implementing Regulation (EU) 2024/2690 takes precedence (Section 30(3) BSIG). Point 5.1.4 of its annex lists what contracts should cover. For all other entities this list is not binding, but it works well as a benchmark.

Do I have to change every existing supplier contract?

The law does not require that. The measures must be proportionate (Section 30(1) BSIG). Start with suppliers that have access to your systems or that your operations cannot run without. For most contracts, an amendment that adds an information security annex is enough.

How quickly must a supplier report a security incident?

The BSIG sets no deadline for suppliers. You report a significant incident no later than 24 hours after you become aware of it, confirm it within 72 hours and send the final report no later than one month after that (Section 32 BSIG). Agree a fixed maximum period from the moment the supplier becomes aware, and a contact point that can be reached at weekends.

Is a data processing agreement under Article 28 GDPR enough for NIS2?

No. A data processing agreement only covers personal data. NIS2 is about the security of your systems as a whole, which includes a remote maintenance provider that never processes personal data. A single information security annex can set the rules for the data processing agreement, the DORA annex and NIS2 in one place.

How GetTeddy handles this

From the first signal to an approved early warning, within 24 hours

GetTeddy links every security event to your product inventory, checks the CRA threshold and the NIS2 and GDPR duties next to it, and drafts the early warning with everything the form asks for. The decision and the submission stay with your named people.

How GetTeddy handles this

A new framework in an afternoon, not a second program

GetTeddy keeps one model of your company and one control set. When a new framework arrives, it reads every requirement against what you already have and labels it full, partial or missing. Only the real gaps become tasks.

How GetTeddy handles this

Agents do the work. You can see every step and stop any of it.

Every result in GetTeddy carries a label: done by an agent, drafted by an agent and approved by a person, or decided by you. Drafts wait for a named approver, connections are read-only unless you allow more, and every action lands in a log your auditor can read.