Identify the entities and services first
A multinational group may contain a manufacturer, an IT service provider, a holding company and a distribution subsidiary. They share ownership but may perform different activities. NIS2 Annexes I and II identify particular entity types and services rather than automatically classifying an entire corporate family under one category.
Create an entity inventory showing registered names, locations, actual services, customers and operational responsibilities. Assess each potentially relevant entity against the annexes and applicable Member State law.
Separate legal-entity scope from enterprise size
The size methodology in Recommendation 2003/361/EC may require the figures of partner or linked enterprises to be included when analysing a particular entity. This does not remove the need to identify the provider that actually supplies a covered service. A small operating subsidiary may be treated as larger for the size test because of linked enterprises, while another affiliate outside listed activities may not be covered on that basis alone.
The distinction should appear expressly in scope memos. Otherwise the organisation risks either overlooking a covered subsidiary or treating an unrelated affiliate as automatically regulated.
Cross-border structures add jurisdiction questions
Groups operating in several Member States should determine jurisdiction for each relevant entity. Article 26 contains general establishment-based principles and special rules for certain digital infrastructure and ICT service providers. A central headquarters location is not a sufficient answer for all subsidiaries and services.
Record the establishment, actual service provider, relevant authority and any special jurisdiction rule. Registration, reporting channels and operational deadlines may depend on the country and national implementation concerned.
Classification and governance within the group
Essential or important status follows Article 3 and the relevant national implementation. Two entities under the same parent can therefore have different classifications and supervisory contexts. The group may centralise cybersecurity controls and incident response, but regulated entities still need a clear allocation of management responsibility, incident-notification decisions and evidence.
A shared security team should maintain an entity-by-entity responsibility map so statutory duties are not obscured by central service arrangements.
Practical group-wide assessment records
Keep a group structure chart, entity-service matrix, size calculation, annex mapping, country-by-country jurisdiction record and classification rationale. Identify who signs off each conclusion and how it is refreshed after mergers, disposals or changes in service delivery. Explicitly note where the group relies on a shared control and which entity is accountable for its implementation.
Such records also help incident teams identify which legal entities must assess notification duties when a shared platform fails or a supplier incident affects several subsidiaries.
Questions on the text
Does a covered subsidiary make its parent automatically subject to NIS2?
No. Each relevant entity and its activities require assessment, although ownership can affect size calculations.
Can subsidiaries have different NIS2 classifications?
Yes. Their covered services, size and applicable classification provisions may differ.
Can group-wide security controls satisfy requirements?
Shared controls can support compliance, but each covered entity must still assess and document its own responsibilities under applicable law.