Skip to main content
NIS2

This text was generated with the help of AI and has not been reviewed by a person.

NIS2 obligations for groups with several entities

NIS2 applies entity by entity: a four-step scope test, what a group can share and what each entity keeps (board approval, registration, reporting, fines).

ResiPlan Team15 min
NIS2
Groups
Subsidiaries
Scope
Article 20
Article 26
Main establishment
SME definition

NIS2 does not apply to a group as such. It applies to each legal entity of the group, one by one. For every subsidiary you check its activity, its size (counted with the group's figures), and the country whose law applies to it. Each entity in scope then has its own duties: it registers, its management body approves the measures, it reports its incidents and it can be fined. A group can share policies, a security operations centre (SOC) and tools. It cannot share the legal accountability of each entity.

The obligations come from Directive (EU) 2022/2555 (NIS2). Because NIS2 is a directive, each entity is bound by the national law of its Member State, and those laws differ on details. This guide was checked on 20 November 2026. It is not legal advice: have your own situation confirmed by your legal adviser or the competent authority.

Key takeaways

  • Scope is decided entity by entity: activity listed in Annex I or II, size, and in some cases a national independence rule.
  • Size is counted with the group's figures (Recommendation 2003/361/EC), so a small subsidiary of a large group can be in scope.
  • Each entity in scope keeps its own duties: registration, approval by its management body (Article 20), incident notification (Article 23), supervision and fines (Articles 32 to 34).
  • Country: as a rule, each entity follows the law of the Member State where it is established. Some digital providers follow the country of their main establishment instead (Article 26).

Does NIS2 apply to the group or to each entity?

To each entity. The directive's obligations are addressed to "essential and important entities" (Articles 3, 20, 21 and 23). In practice, that means each legal entity, not the group. The Centre for Cybersecurity Belgium (CCB) says the same about the Belgian law: it applies to all organisations individually, even if they belong to the same group or holding company (CCB, the NIS2 law).

The group still matters in two places: size, because the figures of linked and partner enterprises are counted, and fines, which are calculated on the turnover of the undertaking the entity belongs to. Both are covered below.

A four-step test for each entity

Run this test for every legal entity in the group, including holding companies and service companies.

StepQuestionWhere it comes from
1. ActivityDoes the entity provide a service, or carry out an activity, of a type listed in Annex I or Annex II? Does a size-independent rule apply?Article 2(1) and (2), Annexes I and II
2. Own sizeIs the entity at least medium-sized on its own figures?Article 2(1); Recommendation 2003/361/EC
3. Consolidated sizeOnce the figures of linked and partner enterprises are added, is it at least medium-sized? Does it exceed the medium-sized ceilings?Recommendation 2003/361/EC, Annex, Articles 3 and 6
4. IndependenceDoes the national law allow the entity's independence from the group to be taken into account, and does that change the result?Recital 16 of NIS2; national law

1. Activity

NIS2 covers entities of a type listed in Annex I (sectors of high criticality, such as energy, transport, banking, health, digital infrastructure and ICT service management) or Annex II (other critical sectors, such as postal services, waste management, manufacturing and digital providers). The test is about what the entity itself does, not what the group does. A group's manufacturing subsidiary may be in scope while its sales subsidiary is not.

Some entities are in scope regardless of size (Article 2(2)). Examples are providers of public electronic communications networks or services, trust service providers, top-level domain name registries and DNS service providers. The same goes for entities that a Member State identifies, for instance because they are the sole provider of an essential service in that State.

2. Own size

The size-cap rule of Article 2(1) brings into scope Annex I and II entities that are at least medium-sized under Recommendation 2003/361/EC. Medium-sized means 50 to 249 staff with a turnover of up to €50 million or a balance sheet of up to €43 million. Below 50 staff, an entity is still medium-sized if both its turnover and its balance sheet exceed €10 million. An entity with 250 staff or more, or with a turnover above €50 million and a balance sheet above €43 million, exceeds the medium-sized ceilings.

3. Consolidated size

This is where groups are often caught out. Under the Recommendation, an enterprise's data includes that of its linked enterprises (typically those it controls or that control it, counted in full) and its partner enterprises (holdings of 25% or more without control, counted in proportion to the stake) (Annex, Articles 3 and 6). A 30-person subsidiary of a large group can therefore count as large.

The result also sets the category. An Annex I entity that exceeds the medium-sized ceilings is, as a rule, essential. Other entities in scope are important, unless a size-independent rule or a national designation makes them essential (Article 3(1) and (2)). Our guide to essential and important entities goes through the categories.

4. Independence

Recital 16 of NIS2 lets Member States take into account how independent an entity is from its partner and linked enterprises. This applies in particular to the network and information systems it uses to provide its services, and to the services it provides. If the entity would not have reached the medium-sized threshold on its own figures, a Member State may then treat it as out of scope. This is an option for Member States, not a right of the entity, and it sits in a recital, not an article. National laws use it in different ways. Check the law and the authority's guidance in the country where the entity is established. Keep a written analysis either way: the authority may ask for it.

An entity that relies on the group's systems, network or IT team will find it harder to argue independence. That is one more reason to map shared IT before concluding.

What the group can share, and what stays with each entity

The directive puts its obligations on each entity. It does not say how a group should organise the work behind them. The table below is our reading of the articles cited. It is not an official interpretation.

TopicCan be shared at group levelStays with each entity
Policies and methodsA common information security policy, risk method, business impact analysis (BIA) scales and measure catalogueAdoption of the measures for its own systems, proportionate to its own risk exposure and size (Article 21(1))
Security operationsA group SOC, a monitoring service, a common incident response teamThe decision that an incident affecting it is significant, and the notification (Article 23)
ToolsShared platforms, a common register of assets and suppliersEvidence for its own scope, available to its own authority
SuppliersCommon supplier assessments and contract clausesSupply chain security for its own direct suppliers and service providers (Article 21(2)(d))
TrainingCommon training contentTraining of the members of its own management body (Article 20(2))
RegistrationPreparing the data centrallyRegistration with the competent authority of its country, and updates within two weeks of a change (Article 3(4))
GovernanceA group programme, a group committeeApproval of the measures by its own management body, which oversees them and can be held liable (Article 20(1))
Supervision and finesNoneSupervision by its own authority and fines imposed on the entity (Articles 32 to 34)

Whether a holding company can carry out formalities on behalf of its subsidiaries depends on national practice. In Belgium, the CCB covers this in its FAQ (question 3.13.5, FAQ on NIS2 and CyberFundamentals).

Board approval in every entity (Article 20)

Article 20(1) requires the management bodies of essential and important entities to approve the cybersecurity risk-management measures taken under Article 21, to oversee their implementation, and makes them liable for infringements. Article 20(2) requires the members of those management bodies to follow training.

For a group, that means a policy approved only by the parent company's board is not enough for the subsidiaries. Each in-scope entity's own management body has to approve the measures that apply to it and follow up on them. A common approach is a group policy that each subsidiary's board formally adopts, plus an entity-level record of the measures, their status and the training of its board members. National laws add their own details, for example on training deadlines or directors' personal fines. Our article on the Netherlands and Belgium compares two of them.

The group's in-house IT company

Many groups run their IT through an internal service company that manages networks, workplaces, cloud tenants or security for the other entities. NIS2 raises three questions for it.

  1. Is it itself in scope? Annex I lists "ICT service management (business-to-business)": managed service providers and managed security service providers (definitions in Article 6(39) and (40)). The directive does not expressly say whether services provided only to companies of the same group count. Check the guidance of the authority in the country where the IT company is established, and record your conclusion. If it is in scope, it goes through steps 2 to 4 like any other entity.
  2. Which country? If it is in scope as a managed (security) service provider, it falls under the Member State of its main establishment in the EU (Article 26(1)(b)), not under every country where it operates. Those providers also submit their details for the registry kept by ENISA (Article 27).
  3. Either way, it is a supplier. Even out of scope, the IT company is a direct service provider for every in-scope entity it serves. Their supply chain security measures cover it (Article 21(2)(d)). Write down what it does for each entity, at what service level and with what security commitments. An incident at the IT company can also lead several entities to notify their own authorities at the same time.

Which country's law applies? (Article 26)

As a rule, each entity follows the law of the Member State where it is established (Article 26(1)). A group with subsidiaries in three Member States applies three national laws, registers on three portals and reports incidents to three sets of authorities. The NIS2 transposition tracker lists the law, the registration portal and the authority of each Member State.

There are three exceptions:

  • Providers of public electronic communications networks or services fall under each Member State where they provide their services (Article 26(1)(a)).
  • DNS service providers, top-level domain name registries, domain name registration services, cloud computing, data centre and content delivery network providers, managed service providers, managed security service providers, and providers of online marketplaces, online search engines and social networking platforms fall under the Member State of their main establishment in the EU (Article 26(1)(b)).
  • Public administration entities fall under the Member State that established them (Article 26(1)(c)).

The main establishment is where decisions on cybersecurity risk-management measures are mainly taken. If that cannot be determined, or if those decisions are not taken in the EU, it is where cybersecurity operations are carried out. Failing that, it is the establishment with the most employees in the EU (Article 26(2)). A provider in the exceptions above that is not established in the EU but offers services there must designate a representative in the EU (Article 26(3)).

For a group, the main establishment rule is not a way to bring all subsidiaries under one country. It applies to each entity that provides one of those services, based on where that entity's cybersecurity decisions are taken.

Incident notification in a group

Each in-scope entity notifies significant incidents to its own CSIRT or competent authority (Article 23(1)). It sends an early warning within 24 hours of becoming aware of the incident, an incident notification within 72 hours, and a final report within one month of the incident notification (Article 23(4)). Our NIS2 incident notification guide covers the content of each step.

In a group, one incident often hits several entities at once, for example an outage at a shared data centre, at the in-house IT company or at a common supplier. Each affected entity then assesses whether the incident is significant for it, and notifies its own authority, in its own country, within its own deadlines. Prepare a contact list per entity (authority, portal, person in charge) before the first incident, not during it.

Fines and sanctions

Fines are imposed on the entity. National law must set maximum fines of at least €10 million or 2% of the total worldwide annual turnover for essential entities, and at least €7 million or 1.4% for important entities, whichever is higher (Article 34(4) and (5)). The turnover is that of the undertaking to which the entity belongs in the preceding financial year. In a group, that can reach beyond the subsidiary's own turnover.

For essential entities, authorities can also, as a last resort, ask for people with managerial responsibilities at chief executive or legal representative level to be temporarily prohibited from managerial functions in that entity (Article 32(5)(b)).

What if some entities fall under DORA?

For financial entities, DORA (Regulation (EU) 2022/2554) is a sector-specific act within the meaning of Article 4 of NIS2. A bank or insurer in the group follows DORA for ICT risk management and incident reporting, while the group's non-financial entities stay under NIS2 as transposed in their countries. See DORA vs NIS2 and our guide to group-level operational resilience.

A group programme in six steps

  1. List every legal entity with its country, its activity (Annex I, Annex II or none), its own figures and its figures with linked and partner enterprises.
  2. Run the four-step test for each entity and record the result, including any independence argument and the source it relies on.
  3. Find the entities covered by Article 26 exceptions, the in-house IT company first, and document where their cybersecurity decisions are taken.
  4. Register each entity in scope in its country, by that country's deadline.
  5. Set one group baseline (policies, method, BIA scales, supplier assessments), then have each entity's management body approve it for that entity and keep its own evidence.
  6. Prepare incident notification per entity and map the shared services and suppliers whose failure would hit several entities at once.

How ResiPlan supports a group

Disclosure: this guide is published by ResiPlan, which sells a business continuity platform. NIS2 does not require or certify any software.

The ResiPlan solution for groups and subsidiaries gives each entity its own workspace, with its own data and users. Headquarters gets a consolidated dashboard with one line per entity. A shared suppliers view shows which entities and processes depend on the same critical supplier. This follows the logic of the table above: one method shared across the group, with records kept entity by entity.

FAQ

Does NIS2 apply to the parent company or to each subsidiary?

To each legal entity that meets the criteria. Each subsidiary is checked for its own activity (Annex I or II), its size counted with group figures, and the country whose law applies to it. A parent company is only in scope if it meets these criteria itself. Being at the top of a group that has in-scope subsidiaries is not enough.

Is a small subsidiary of a large group in scope?

It can be. Size is calculated under Recommendation 2003/361/EC, which adds the figures of linked and partner enterprises. A small subsidiary of a large group can therefore be medium-sized or large for NIS2 if its activity is listed in Annex I or II. Recital 16 lets Member States take its independence from the group into account. Check how the law of its country uses that option.

Can one group policy cover all entities?

The content can be shared, but each in-scope entity's management body must approve the measures that apply to it and oversee them (Article 20(1)). A group policy formally adopted by each entity's board, with entity-level evidence, is a common way to meet this.

Does our in-house IT company fall under NIS2?

Possibly, as a managed service provider or managed security service provider (Annex I, ICT service management). The directive does not expressly settle the case of services provided only within a group, so check the guidance of the authority in its country. If it is in scope, it falls under the country of its main establishment (Article 26). Either way, it is a service provider covered by the supply chain measures of every entity it serves.

Must each entity notify incidents separately?

Yes. Each in-scope entity notifies significant incidents to its own CSIRT or competent authority, within 24 hours, 72 hours and one month (Article 23). When one incident affects several entities in different countries, several notifications may be needed.

How is the fine calculated in a group?

The fine is imposed on the entity. The maximum is set by national law at no less than €10 million or 2% of worldwide annual turnover for an essential entity, and €7 million or 1.4% for an important entity, whichever is higher. The turnover is that of the undertaking to which the entity belongs (Article 34).

Sources

Further reading

Found this useful?
Share it with your team.

Try ResiPlan for free

14-day trial, no credit card. Import your risks and plans in minutes.

NIS2

NIS2 for groups in the Netherlands and Belgium, entity by entity

NIS2 applies entity by entity: group size calculation, registration per country, board approval in each subsidiary, group IT companies, fines on group turnover. Worked through for the Netherlands and Belgium.

NIS2

NIS2 transposition by country: laws, dates and authorities

Where each of the 27 EU Member States stands on NIS2 on 4 November 2026: national law, entry into force, registration of entities and competent authority.

NIS2

NIS2 Essential vs Important Entities: Complete 2026 Scope Guide

NIS2 2026 full guide: essential vs important entities classification, thresholds, sectors, obligations and consequences of each classification under EU cybersecurity law.