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.
HomeArticlesNIS2 Requirements for Content Delivery Networks
Implementing Regulation 2024 2690 / 2026-10-11

NIS2 Requirements for Content Delivery Networks

Content delivery network providers covered by NIS2 must examine the detailed cybersecurity measures in Implementing Regulation (EU) 2024/2690. Article 9 contains significance criteria for incidents affecting content delivery network services, alongside the common criteria. The provider should map the legal entity, delivery infrastructure and service dependencies before applying the requirements.

Confirm the content delivery service

A content delivery network supplies a geographically distributed network of servers supporting high availability, accessibility or fast delivery of digital content and services to internet users on behalf of content and service providers. Operating a website that uses a CDN does not make its owner the CDN provider. Determine which entity manages the distributed service, edge nodes, traffic routing and contractual delivery obligations, then assess its NIS2 status.

Protect the distributed delivery infrastructure

CDN operations depend on configuration integrity, traffic management, edge software, certificate and key handling, and privileged access across many locations. Risk controls should address deployment pipelines and the possibility that a misconfiguration or compromised management system spreads across the network. Controls from the regulation's Annex should be mapped to these actual delivery functions, with evidence of secure changes, monitoring, incident handling and access governance.

Plan for regional and systemic disruption

A fault at one edge location may have limited impact, while a control-plane failure can affect customers across several countries. Examine origin-server dependencies, interconnection arrangements, routing controls and concentration in shared suppliers. Business continuity testing should include the ability to fail over or roll back changes and to communicate disruptions to customers. A provider should assess the effects on its service rather than assuming customer-facing application availability alone measures CDN resilience.

Use the CDN-specific significance tests

Article 9 of Regulation 2024/2690 sets conditions for significant CDN incidents. Apply these alongside Article 3's common tests and the Article 4 treatment of recurring incidents where relevant. Preserve time-stamped data about affected geographic regions, users, service degradation, availability and malicious activity. The organisation's operational severity labels are useful for response but do not decide legal significance without reference to the regulation.

Keep cross-border governance consistent

CDN providers can operate in many Member States. Review the applicable Article 26 main-establishment rules and Article 27 information duties, rather than equating every edge server location with a separate supervisory jurisdiction. Maintain accurate incident contacts, control owners and reporting routes. Inform the management body about systemic dependencies and unresolved remediation with enough detail to support Article 20 oversight.

Points of clarification

Are these requirements relevant to all NIS2 entities?

No. Regulation 2024/2690 applies to the specified categories of providers in its Article 1.

Are there provider-specific incident criteria?

Yes. Article 9 supplies provider-specific significance conditions alongside other applicable provisions.

Where should the official text be checked?

Consult the operative articles and Annex of Regulation 2024/2690 on EUR-Lex.

Further entries on this subject

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.