Wednesday, November 18, 2026 · Week 47 DE · EN · FR · ES Dark
Guides

NIS2 & SaaS: Supply chain compliance gaps

Entities subject to NIS2 must assess SaaS risks in their supply chain and document appropriate security measures.

By Benedikt Langer March 22, 2026 4 min read
NIS2 & SaaS: Supply chain compliance gaps

Germany’s NIS2 implementation law has been in force since 6 December 2025. For important and essential entities, the security of direct service providers forms part of risk management. This also applies to SaaS services where their use poses risks to the entity’s own IT systems and processes. A traceable risk assessment, appropriate measures and their documentation are essential.

Key takeaways

  • Supply chain security is part of risk management. The German BSI Act also covers security aspects of relationships with direct service providers.
  • The level of scrutiny should reflect the risk posed by the service. Data, permissions and the consequences of an outage help determine priorities.
  • Significant security incidents may have to be reported. The early warning must generally be submitted within a maximum of 24 hours of becoming aware of the incident.

Which obligations apply to SaaS customers

The German BSI Act requires important and essential entities to take appropriate, proportionate and effective technical and organisational measures. These include supply chain security, including relationships with direct suppliers and service providers. The entity must document its compliance with its risk management obligations.

Whether a company itself falls under the law depends on its activities and the statutory criteria. Using a SaaS service does not in itself automatically make a provider an entity subject to NIS2, and an assessment of the provider does not replace the customer’s obligations.

For certain digital service providers, including cloud computing service providers, EU Implementing Regulation 2024/2690 specifies the risk management requirements. It includes provisions on the selection of suppliers and security provisions in contracts. Whether it applies to a particular provider must be assessed separately.

Assess SaaS services according to risk

An inventory provides the basis for the assessment: Which services are used, what data is held there and what access do providers or connected applications have? Services whose failure interrupts business processes or whose accounts have extensive permissions may be particularly relevant.

For prioritised services, IT teams should assess the provider’s security measures. Current audit reports, certificates and information on how vulnerabilities and security incidents are handled can provide useful evidence. The assessment should establish whether each item of evidence covers the service actually used and which measures remain the customer’s responsibility.

A certificate alone does not fully answer these questions. Where evidence is missing or risks remain unresolved, the entity should request additional information, agree on security measures or document the residual risk. The assessment should be repeated when significant changes occur or new information becomes available.

Align contracts and incident reporting

Contracts and service descriptions should reflect the risk assessment. Responsibilities for access protection, recovery and notification of security incidents are of practical relevance. The extent to which inspection or audit rights are required and enforceable depends on the service and the applicable requirements.

For important and essential entities, Section 32 of the German BSI Act requires an early warning of significant security incidents without undue delay and within 24 hours of becoming aware of the incident at the latest. A further notification with an initial assessment follows within 72 hours at the latest. An incident at a SaaS provider must be assessed to determine whether it constitutes a significant security incident for the entity.

To enable the entity to make this assessment in time, it should agree with the provider who will be informed and what information is needed. Internal responsibilities and an accessible contact for security incidents are part of the preparations.

Registration and management responsibility

The BSI portal is used, among other things, to register and report security incidents. Under Section 33 of the German BSI Act, important and essential entities must generally register no later than three months after they first or again qualify as such. Registration does not replace the implementation of security measures.

Management bodies must implement risk management measures and oversee their implementation. If they breach these obligations, they are liable to their entity for damage caused through their fault under the applicable company law rules. A security incident at a provider does not in itself establish personal liability for management.

Frequently Asked Questions

Does every SaaS provider need the same level of scrutiny?

The level of scrutiny should reflect the risk involved. In particular, the data used, permissions and consequences of an outage should be considered. The German BSI Act requires appropriate and proportionate measures.

Is a SaaS provider’s security certificate sufficient?

A certificate can be helpful evidence. Its scope, the measures it covers and the risks of the specific use are decisive. The entity remains responsible for its own risk management obligations.

When must an incident at a SaaS provider be reported?

An important or essential entity must assess whether it is facing a significant security incident. If so, the early warning must be submitted without undue delay and within 24 hours of becoming aware of the incident at the latest.

Image source: AI-generated (November 2026)

Translated from the German original using artificial intelligence. The German version is authoritative.

Also available in

FrançaisEspañolDeutsch
MBF Media Newsletter

The monthly briefing for decision-makers

Once a month, the MBF Media Newsletter gathers what matters from cloudmagazin, MyBusinessFuture, Digital Chiefs and SecurityToday, curated by the editorial team.

Around 23,500 IT and business decision-makers read this newsletter. Read along.

Subscribe for free
MBF Media Newsletter, aktuelle Ausgabe auf dem iPhone
A magazine by Evernine Media GmbH