Skip to main content
Back to overview

NIS2 Linked Enterprises: Why a 30-Person Subsidiary Can Be Essential

By NIS2Certify
nis2linked-enterprisesscopesize-capcorporate-groupsmsp
NIS2 Linked Enterprises: Why a 30-Person Subsidiary Can Be Essential

A client tells you they have 30 employees and €6 million in turnover, so NIS2 does not apply. Then you look at the shareholder register. A parent company holds 60% of the shares, and the parent group employs 300 people with €70 million in turnover.

That client is not small. Under the NIS2 linked enterprises rules, it is large. If it operates in an Annex I sector, it is an essential entity.

This is the most common scoping error we see consultants inherit. The size test in NIS2 does not look at the legal entity in isolation. It looks at the enterprise, and the enterprise includes its partners and linked companies.

NIS2 measures size with the EU SME definition, not the company's own payroll

Article 2(1) of Directive (EU) 2022/2555 applies NIS2 to entities that qualify as medium-sized enterprises "under Article 2 of the Annex to Recommendation 2003/361/EC", or exceed those ceilings.

That Recommendation is the EU SME definition. It sets three ceilings:

  • Medium: fewer than 250 staff, and turnover up to €50 million or balance sheet up to €43 million.
  • Small: fewer than 50 staff, and turnover or balance sheet up to €10 million.
  • Micro: fewer than 10 staff, and turnover or balance sheet up to €2 million.

An entity reaches "medium" with 50 or more staff, or when both turnover and balance sheet exceed €10 million. It is "large" with 250 or more staff, or when turnover exceeds €50 million and the balance sheet exceeds €43 million.

The part most people skip is Articles 3 and 6 of the same Annex. They decide whose numbers go into the calculation.

Linked, partner or autonomous: the classification decides the numbers

The Annex sorts every ownership relationship into one of three types.

Autonomous. No other enterprise holds 25% or more of the capital or voting rights, and your client holds less than 25% in others. Only the client's own figures count.

Partner. A holding of 25% or more, but no control. The partner's figures are added pro rata to the higher of the capital or voting-rights percentage. A 30% partner with 200 staff adds 60.

Linked. One enterprise controls the other: majority of voting rights, the right to appoint or remove a majority of the board, or a dominant influence by contract or articles of association. Linked enterprises add 100% of their figures. Every company in the controlled chain counts.

There are exceptions. Under Article 3(2) of the Annex, certain investors can hold between 25% and 50% without becoming partners: public investment corporations, venture capital firms, business angels investing up to €1.25 million in one company, universities and non-profit research centres, institutional investors, and small autonomous local authorities.

Two more rules matter in practice:

  • Article 2(2) NIS2 disapplies Article 3(4) of the Annex. Normally, 25% public ownership disqualifies an enterprise from SME status. For NIS2, that rule does not apply, so a municipally owned company is measured on its real figures.
  • Article 4(2) of the Annex says status changes only when a ceiling is crossed in two consecutive financial years. One strong year does not pull a client into scope. Two do.

For the full scope logic beyond size, see Does NIS2 apply to my organisation?.

Worked example: how the 30-person firm becomes essential

Take the client from the opening. It runs a road haulage operation, an Annex I transport activity.

StaffTurnoverBalance sheet
Client alone30€6m€4m
Parent group (60% stake, linked)300€70m€60m
Consolidated330€76m€64m

Alone, the client is small and out of scope. Consolidated, it exceeds 250 staff. That makes it a large Annex I entity, and under Article 3(1)(a) an essential entity.

The difference is not cosmetic. Essential entities face ex-ante supervision and higher maximum fines. We set out what that means in Essential vs Important Entities Under NIS2.

Note what does not happen: the parent does not automatically come into scope because its subsidiary does. Scope is assessed per legal entity. The parent is only in scope if it carries out an Annex I or II activity itself.

Recital 16: the independence escape hatch, and who actually opened it

Recital 16 of NIS2 lets Member States take into account "the degree of independence an entity enjoys in relation to its partner or linked enterprises", particularly regarding its network and information systems and the services it provides.

In plain terms: if the subsidiary's IT is genuinely separate from the group, a Member State may let it be measured on its own figures.

This is optional. Member States made very different choices:

  • Germany: § 28(4) BSIG excludes partner and linked data if the company is independent "with regard to the nature and operation of its IT systems, components and processes". The BSI FAQ says independence is denied when IT is run entirely by the group parent.
  • Austria: § 25(4) NISG 2026, in force since 1 October 2026, requires organisational, technical and operational independence of the network and information systems.
  • Belgium: Article 3 §2 of the NIS2 law of 26 April 2024 tells the CCB to take independence into account. The CCB FAQ says this applies "only in exceptional cases": no shared Active Directory, servers, cloud tenant or central management. The burden of proof is on the entity.
  • Italy: Article 3(4) of D.Lgs. 138/2024, detailed by DPCM 221/2024, requires the entity to declare both independent systems and independent services, during registration with ACN.
  • Poland: Article 5(6)–(7) of the amended KSC uses "or": independent systems or no jointly provided services is enough. That is the loosest test in this list.
  • Netherlands: the Cyberbeveiligingswet has no independence rule. Normal aggregation applies.
  • France and Spain: neither the French Résilience bill nor the Spanish draft law contains a linked-enterprise rule at all. Both are still in the legislative process.

The practical consequence: the same group structure can produce a different answer in Munich, Rotterdam and Warsaw. If your client has subsidiaries in several Member States, run the test per country. Article 26 jurisdiction rules decide which national law applies to each entity.

NIS2 transposition by country

  • AustriaIn force
    • In force since October 1, 2026
    • Act: NISG 2026 (BGBl. I Nr. 94/2025)
    • Registration due December 31, 2026

    Authority: Federal Office for Cybersecurity · Source

  • NetherlandsIn force
    • In force since August 15, 2026
    • Act: Cyberbeveiligingswet (Stb. 2026, 187)
    • Registration required, no transition period

    Authority: NCSC (MijnNCSC) · Source

  • LuxembourgIn force
    • In force since May 10, 2026
    • Act: Law of 5 May 2026
    • Registration due July 10, 2026

    Authority: ILR (CSSF for finance) · Source

  • PolandIn force
    • In force since April 3, 2026
    • Act: UKSC (Dz.U. 2026 poz. 252)
    • Registration due October 3, 2026
    • Measures due April 3, 2027

    Authority: Minister Cyfryzacji (Wykaz KSC) · Source

  • PortugalIn force
    • In force since April 3, 2026
    • Act: Decree-Law 125/2025 (RJC)

    Authority: CNCS · Source

  • BulgariaIn force
    • In force since February 13, 2026
    • Act: Cybersecurity Act amendment (State Gazette No 17/2026)

    Authority: Ministry of e-Government · Source

  • MaltaIn force
    • In force since January 23, 2026
    • Act: S.L. 460.41

    Authority: Critical Infrastructure Protection Department · Source

  • SwedenIn force
    • In force since January 15, 2026
    • Act: SFS 2025:1506

    Authority: NCSC-SE · Source

  • EstoniaIn force
    • In force since January 1, 2026
    • Act: Cybersecurity Act (KüTS) amendment
    • Registration within 3 months

    Authority: RIA · Source

  • GermanyIn force
    • In force since December 6, 2025
    • Act: NIS2UmsuCG
    • Registration due March 6, 2026
    • 17,729 registered by June 30, 2026

    Authority: BSI · Source

  • CzechiaIn force
    • In force since November 1, 2025
    • Act: Act No 264/2025 Coll.
    • Registration within 60 days

    Authority: NÚKIB · Source

  • DenmarkIn force
    • In force since July 1, 2025
    • Act: NIS 2 Act No 434 of 6 May 2025
    • Registration due October 1, 2025

    Authority: Danish Agency for Societal Security · Source

  • SloveniaIn force
    • In force since June 19, 2025
    • Act: ZInfV-1 (OG 40/25)
    • Registration within 30 days

    Authority: URSIV · Source

  • CyprusIn force
    • In force since April 25, 2025
    • Act: Law 60(I)/2025

    Authority: Digital Security Authority · Source

  • FinlandIn force
    • In force since April 8, 2025
    • Act: Cybersecurity Act 124/2025
    • Registration due May 8, 2025
    • Measures due July 8, 2025

    Authority: Traficom (NCSC-FI) · Source

  • HungaryIn force
    • In force since January 1, 2025
    • Act: Act LXIX of 2024

    Authority: SZTFH · Source

  • SlovakiaIn force
    • In force since January 1, 2025
    • Act: Act No 366/2024 Coll.
    • Registration within 60 days

    Authority: NBÚ · Source

  • RomaniaIn force
    • In force since December 31, 2024
    • Act: GEO 155/2024 (Law 124/2025)
    • Registration within 30 days

    Authority: DNSC · Source

  • GreeceIn force
    • In force since November 27, 2024
    • Act: Law 5160/2024 (Gazette A' 195)

    Authority: National Cybersecurity Authority · Source

  • BelgiumIn force
    • In force since October 18, 2024
    • Registration due March 18, 2025

    Authority: CCB · Source

  • LithuaniaIn force
    • In force since October 18, 2024
    • Act: Law No XIV-2902

    Authority: NCSC (MoND) · Source

  • ItalyIn force
    • In force since October 16, 2024
    • Act: D.Lgs. 138/2024
    • Baseline measures due by October 2026 (entities listed in 2025)

    Authority: ACN · Source

  • LatviaIn force
    • In force since September 1, 2024
    • Act: National Cybersecurity Law

    Authority: National Cybersecurity Centre · Source

  • CroatiaIn force
    • In force since February 15, 2024
    • Act: Cybersecurity Act (OG 14/2024)

    Authority: NCSC (SOA) · Source

  • FranceNot yet transposed
    • Senate adopted the law on March 12, 2025
    • Regulator published its framework on March 17, 2026
    • Referred to the Court of Justice on July 8, 2026
    • Pre-registration open

    Authority: ANSSI · Source

  • SpainNot yet transposed
    • Draft bill approved on January 14, 2025
    • Referred to the Court of Justice on July 8, 2026
    • The NIS1 regime still applies

    Authority: CCN / INCIBE · Source

  • IrelandNot yet transposed
    • Referred to the Court of Justice on July 8, 2026
    • Bill not yet enacted

    Authority: NCSC Ireland · Source

Status as of September 28, 2026. Other member states: see the country-by-country timeline.

The group IT trap: shared services undo independence

Here is where MSPs need to pay attention. The independence argument almost always fails on shared IT.

If the subsidiary uses the group's Microsoft 365 tenant, joins the group's Active Directory, or is managed by the group IT department, it is not independent under the German, Austrian, Belgian or Italian tests. In Germany, the BSI's test is whether the parent has a decisive influence over how IT is procured, operated and configured.

Italy goes a step further. Under Article 3(10) of D.Lgs. 138/2024, a linked company that runs the network and information systems or provides ICT services to an NIS entity is itself in scope, regardless of its size. A five-person group IT company can be pulled in this way.

Germany has a counterweight. § 28(3) BSIG lets activities that are negligible relative to the whole business be disregarded when classifying an entity. The BSI treats group-internal IT services as negligible below 50 staff and 10% of turnover and balance sheet.

A five-step method for your client file

When a client in a group asks whether NIS2 applies, document this:

  1. Map ownership. Shareholder register, voting agreements, board appointment rights. Go up and down the chain.
  2. Classify each relationship as autonomous, partner or linked. Check the Article 3(2) investor exceptions.
  3. Aggregate using the last two closed financial years. Apply the two-year rule before you change status.
  4. Test independence only where national law allows it, against that country's specific wording. Collect evidence: separate tenants, identity stores, contracts, management tooling.
  5. Record the calculation and keep it with the registration. Regulators ask how size was determined, and "we only counted our own payroll" is not an answer.

If you want a structured starting point for the rest of the client's position, our Quick Scan produces a readiness baseline in minutes, which you can extend with the group calculation above.

What may change

The Commission's January 2026 proposal to amend NIS2 introduces a small mid-cap category and is still at committee stage in the European Parliament. It does not yet change how linked enterprises are counted, and current national law applies until any amendment is adopted and transposed. Our overview of the 2026 amendment proposal tracks the details.

Until then, the rule is simple: never accept a client's headcount without seeing who owns them.

Still have a question?

Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.