Why headquarters location is not a complete scope test
Article 2 of Directive (EU) 2022/2555 begins with listed entity types, services or activities in the Union and the relevant size or exception rules. A company incorporated elsewhere may operate through EU establishments or deliver services into EU markets. The scope review must therefore start with the actual legal entities, services and delivery model. A non-EU parent company does not necessarily place every affiliate inside NIS2, and having EU customers does not automatically bring every supplier into scope.
Document which entity holds the customer contracts, operates the service and owns the affected systems. Those facts can change the appropriate jurisdiction analysis.
The important distinction between EU establishment and EU services
Article 26 generally allocates jurisdiction to the Member State in which a covered entity is established, but it creates special rules for telecommunications, certain digital infrastructure and digital service providers, and public administration. A local subsidiary or branch cannot always be treated interchangeably with the non-EU parent. For the Article 26(1)(b) provider categories, main establishment in the Union has a distinct legal meaning.
Companies should establish where decisions about cybersecurity risk-management measures are predominantly taken, then consider the fallback criteria specified in Article 26(2). The assessment should identify the applicable national implementing law.
When an EU representative may be required
Article 26(3) applies to entities in the categories described in Article 26(1)(b) when they have no establishment in the Union but offer services there. Covered categories include DNS services, cloud computing, data centres, managed services and certain online platforms. Such entities must designate a representative in a Member State where services are offered. This is not a blanket rule that every business outside the EU must appoint a representative.
Absence of an appointed representative does not automatically remove enforcement exposure. Article 26(3) allows relevant Member States to pursue legal action against an entity that fails to designate one.
Classification and operational requirements
Once coverage and jurisdiction are established, Article 3 distinguishes essential from important entities. Covered organisations should assess management-body responsibilities, cybersecurity risk-management measures and significant-incident reporting under Articles 20, 21 and 23. Operational requirements and registration arrangements must be verified against applicable national measures and competent-authority guidance.
Do not assume that one country’s registration process, reporting channel or classification decision necessarily settles every other country’s legal issue, particularly where different entities and activities are involved.
A practical cross-border assessment file
For each entity, record legal identity, country of incorporation, EU establishments, services sold into EU markets, sector mapping, staff and financial calculations, ownership structure and any Article 2 exceptions. Add a separate jurisdiction memorandum applying Article 26, noting any representative appointment and the relevant national authority.
Review the file when services expand, governance decisions move, a new EU entity is formed or applicable law changes. Treat a proposed amendment as a proposal until enacted.
Questions on the text
Does a non-EU address always exempt a company from NIS2?
No. The applicable service, EU activities, scope rules and jurisdiction provisions must be considered.
Does every non-EU supplier need an EU representative?
No. The Article 26(3) representative requirement concerns specified provider categories and conditions.
Does a representative replace the company’s responsibility?
No. The Directive does not treat appointment of a representative as a transfer of the provider’s substantive obligations.