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.
HomeArticlesRepresentative Requirements for Non-EU Entities Under NIS2
Registration Jurisdiction / 2026-10-10

Representative Requirements for Non-EU Entities Under NIS2

Article 26(3) of NIS2 requires certain digital infrastructure, ICT service and digital providers that offer services in the Union without an EU establishment to designate a representative in a Member State where those services are offered. This obligation is category-specific, not a general requirement for every foreign business with EU customers.

Which entities need to examine Article 26(3)

The representative requirement concerns providers specified in Article 26(1)(b), including DNS, TLD registries, cloud computing, data centres, content delivery networks, managed service and managed security service providers, and certain online marketplaces, search engines and social networking platforms. The provider must meet the applicable conditions, including offering services in the Union without being established there. Mere accessibility of a general business website is not conclusive.

How the representative location is selected

Article 26(3) calls for designation in one Member State where the provider offers its services. The provider must identify the appropriate legal entity, the covered service and the chosen Member State. It should confirm the national implementation and administrative process associated with that appointment. The country need not be guessed from customer concentration or corporate preference without examining statutory conditions.

What the representative does and does not do

The representative provides a point through which competent authorities or CSIRTs may address the relevant provider under the Directive. The organisation must document the representative's role, contact details and authority to act. Appointment does not shift the substantive cybersecurity and incident reporting responsibilities from the provider to an unrelated third party, and it does not replace the provider's own compliance programme.

Consequences of failing to appoint

Article 26(3) provides that failure to designate a representative does not prevent legal actions against the entity by Member States in which services are offered. A provider should not treat non-appointment as a way to avoid jurisdiction. Record any uncertainty about the provider category, establishment status or national requirements, and obtain appropriate advice where the legal position is complex.

How to keep the appointment effective

Maintain the appointment agreement, legal names, service details, communication arrangements and relevant Member State contact information. Align that record with Article 27 information duties where applicable, national registration requirements and Article 23 incident escalation. Reassess if the provider creates an EU establishment, transfers services to another entity or changes where cybersecurity decisions are made.

Questions on the text

Does every US or UK company serving Europe need a NIS2 representative?

No. Article 26(3) is limited to specified provider categories under particular conditions.

Can the representative take over compliance obligations?

No. The provider retains substantive NIS2 responsibilities.

Does failing to designate a representative remove NIS2 exposure?

No. Article 26(3) explicitly preserves the possibility of legal action.

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.