An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesCloud Supplier Risk Under NIS2
Supply Chain Security / 2026-10-09

Cloud Supplier Risk Under NIS2

Cloud arrangements differ between infrastructure, platform and software services. Document which controls the provider operates and which remain with the customer, including identities, applications, logging, encryption and backups. Evaluate which workloads support covered services. The same cloud vendor may host both critical operational systems and low-impact collaboration tools, requiring different assurance priorities.

Identify the cloud service and responsibility boundaries

Cloud arrangements differ between infrastructure, platform and software services. Document which controls the provider operates and which remain with the customer, including identities, applications, logging, encryption and backups.

Evaluate which workloads support covered services. The same cloud vendor may host both critical operational systems and low-impact collaboration tools, requiring different assurance priorities.

Assess resilience and concentration

Determine dependencies on regions, network connectivity, management APIs and shared services. Review realistic recovery options for a regional outage, configuration error or compromise of the customer's cloud tenant.

Multi-region use may still depend on common identity, control-plane or provider services. Avoid asserting independence without checking the architecture and exercising failover.

Review access, data and configuration security

Examine privileged roles, service accounts, key custody, retention, audit logs, baseline configurations and the ability to export required data. Review provider evidence for the particular cloud service rather than relying only on enterprise-wide claims.

Where a customer misconfiguration could expose information, agree who detects it, who responds and which evidence will be available after an incident.

Prepare incident cooperation and recovery

Record incident contacts, notification arrangements, log retention, support escalation and tested restoration paths. Verify whether the customer can recover workloads when a provider account or region is inaccessible.

Contractual commitments and service level objectives may support planning but do not themselves prove end-to-end continuity.

Check applicable NIS2 scope and retain evidence

Cloud computing service providers are among entity types addressed by NIS2, with relevant jurisdiction and classification rules. Their potential legal status does not automatically establish that every customer falls within the Directive.

Keep a supplier assessment, dependency map, cloud responsibility matrix, evidence of controls and recovery tests. Check applicable Member State law and the additional requirements for specified providers under Regulation 2024/2690.

Questions on the text

Does outsourcing remove a covered entity's NIS2 responsibility?

No automatic transfer of statutory duties follows from outsourcing. Assess obligations for each legal entity under applicable national law.

Does the same supplier assessment suit every relationship?

No. The depth of assessment should reflect service criticality, access, exposure and applicable legal requirements.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.