Skip to content

Need urgent help? Call +48 732 059 711 (answered around the clock) or email pilne@cydefen.com.

Cydefen
Language:

Language

Choose your edition

The editions are not translations of one another. Each is written for its own reader, so the emphasis and the examples differ.

9 April 2026

NIS2 is one directive and many national laws. What should a group ask each entity?

A group-level briefing on NIS2 for organisations with entities in several member states, covering entity classification, control ownership, incident reporting and supplier reach.

NIS2 is often discussed as though it were a single rulebook. It is not. Directive (EU) 2022/2555 sets the common floor; each member state transposes it into national law, and it is that national law — not the directive — that creates an enforceable duty for a given legal entity. A group operating in six member states is therefore reading six statutes that agree on the shape of the obligation and differ on registration mechanics, supervisory contacts, sanction regimes and, in places, on who is in scope at all.

For a group security function, the hard part is no longer tracking the directive. It is deciding how each legal entity, the central security team and the shared service providers divide the work — and being able to show that decision to a regulator that only has jurisdiction over one of them.

This article is an operating prompt, not legal advice. Applicability and statutory interpretation need to be confirmed against the national legislation in force and advice appropriate to each entity.

A group-level scoping exercise is not a substitute for entity-level reasoning. Classification turns on the sector, the activity actually performed and the size criteria set out in the annexes to the applicable national act — and those criteria are applied to the entity, not the brand.

For each entity, record the activities considered, the sector assigned, the size test applied, the exceptions examined and the entities whose status was determined separately. Then separate two things that are easy to conflate: duties the entity owes locally, including registration where the national regime requires it, and services it happens to consume from a parent or a sister company.

Who owns the control when the service is centralised?

An entity may consume identity, monitoring, cloud, procurement or incident response from a group platform. That does not make ownership obvious, and “the group runs it” is not an answer a supervisor can act on. For each control that matters, document:

  • the accountable owner inside the regulated entity;
  • the team operating the service, wherever it sits;
  • the evidence the local entity can obtain without escalating;
  • the decision route when the control fails; and
  • any supplier or data-location dependency.

That mapping is far more informative than copying a group control catalogue into a local compliance spreadsheet and marking it green.

Can the local team report without waiting for group certainty?

National transpositions set a staged notification sequence, beginning with an early warning and followed by fuller reporting as the picture firms up. The deadlines and the receiving authority are defined by national law, so confirm both per entity rather than assuming one group standard.

The operational question underneath is the same everywhere: the first hours of an incident rarely produce a complete picture, and the duty to notify does not wait for one. Exercise how local and central teams classify an event, preserve evidence, involve legal and communications, and authorise a notification while the facts are still moving. Test the contact details and the access credentials for each reporting channel, not just the written procedure.

Does supplier governance reach the services that can stop the operation?

Global vendor tiering is built around group spend and group risk. It frequently misses a single point of failure that is local, small and load-bearing — a regional payment processor, one integrator with privileged access, a hosting provider serving a single market.

Start from the critical processes of each entity and trace the technology, data and service providers they actually depend on. Then check whether the contracts and the operating procedures produce timely incident information and genuine cooperation, rather than a general security schedule that nobody has tested.

What evidence can management actually review?

Management needs more than a traffic-light dashboard. A decision pack should connect the obligation, the risk scenario, the control in place today, the evidence gap, the accountable owner and the decision being requested. Where remediation depends on a group platform, make that dependency and its escalation path visible — otherwise the entity carries a duty it has no mechanism to discharge.

A defensible cross-border outcome

The objective is not a separate security programme per member state. It is a defensible mapping between each entity’s local duties and the controls, people and evidence that already exist across the group, with the local gaps stated rather than averaged away.

Two failure modes are worth naming. A group that assumes uniformity will be surprised by the member state whose transposition is stricter than the directive. A group that treats every entity as a special case will build the same control six times and be unable to answer a simple question about any of them. The workable position sits between: one control model, one evidence pipeline, and an explicit per-entity annex for what national law does differently.

Turn the next security review into a working plan

Use the free readiness checklist to connect governance, critical services, controls, response, recovery and evidence.