NIS2: who is in scope, the ten measures and the reporting clocks
NIS2 widened EU cybersecurity law from a few hundred operators to tens of thousands of organisations across eighteen sectors, made management personally accountable and set tight incident-reporting deadlines. Because it is a directive, each member state has its own transposing law, but the core obligations are the same everywhere. This guide explains scope, the measures and how to run NIS2 on top of an existing ISO 27001 programme.
NIS2 replaced the 2016 NIS Directive because the original left too much to member states and reached too few organisations. The new directive sets a size cap, lists the sectors, prescribes minimum measures and reporting deadlines, and requires management bodies to approve the measures, oversee them and attend training. Supervisory authorities can audit, order remediation, publish breaches and, for essential entities, temporarily suspend managers.
Scope is determined by sector and size, not by whether an organisation considers itself critical. Energy, transport, banking, financial market infrastructure, health, water, digital infrastructure, ICT service management, public administration and space are Annex I; postal, waste, chemicals, food, manufacturing of medical devices, electronics, machinery and vehicles, digital providers and research are Annex II. Suppliers to in-scope entities are pulled in through the supply-chain measure.
The ten minimum measures (Article 21)
Policies on risk analysis and information system security
A documented approach to assessing and managing cyber risk, approved by management.
Incident handling
Detection, response, recovery and the reporting process that meets the Article 23 deadlines.
Business continuity
Backup management, disaster recovery and crisis management.
Supply chain security
Security aspects of relationships with direct suppliers and service providers, including their vulnerabilities and practices.
Security in acquisition, development and maintenance
Including vulnerability handling and disclosure.
Policies and procedures to assess effectiveness
Measuring whether the risk-management measures actually work.
Basic cyber hygiene practices and training
For staff and, explicitly, for members of the management body.
Cryptography and, where appropriate, encryption
Policies and procedures on their use.
Human resources security, access control and asset management
Joiners, movers and leavers; privileged access; knowing what you have.
Multi-factor or continuous authentication, secured communications and emergency communications
Where appropriate, across the organisation.
The reporting deadlines
- Early warning: 24 hours. Whether the incident is suspected to be caused by unlawful or malicious acts or could have cross-border impact.
- Incident notification: 72 hours. An initial assessment of severity, impact and indicators of compromise.
- Intermediate report. On request of the CSIRT or competent authority, status updates.
- Final report: one month. Detailed description, type of threat or root cause, mitigation applied and measures taken, cross-border impact.
Who it applies to
Medium and large organisations in the eighteen sectors, wherever they are established in the EU, plus smaller ones that are sole providers of a service, that affect public safety or that are specifically named, such as DNS providers, trust service providers and public electronic communications networks. Non-EU providers of certain digital services must designate an EU representative. Suppliers to in-scope entities are not directly regulated but are contractually required to meet the supply-chain measure.
From scope to evidence, in one system
NIS2 measures mapped to ISO 27001 controls
The ten measures are carried as a framework whose requirements map through the crosswalk to ISO 27001 Annex A and the national transposition in scope, so an ISO-certified organisation sees immediately which NIS2 requirements its existing evidence already satisfies.
Incident reporting clocks
Incidents carry the 24-hour, 72-hour and one-month timers with the content each report requires, and the notification record is kept with the incident.
Supply-chain measure as a vendor programme
Suppliers are tiered, assessed and monitored in the third-party module, with the security clauses and assurance evidence the measure requires.
Management accountability made visible
Management approval of the measures, training attendance and oversight reviews are recorded, which is the evidence authorities will ask for when they examine the management body’s role.
Effectiveness measured, not assumed
Control testing schedules and continuous evidence from your cloud, identity and endpoint platforms give the effectiveness assessment the sixth measure requires.
Frequently asked questions
How do we know if we are essential or important?
Large entities (250+ staff or €50 million turnover) in Annex I sectors are essential; medium entities in Annex I and all in-scope entities in Annex II are important, with exceptions for specific types such as qualified trust service providers and DNS operators, which are essential regardless of size. Member states publish registers and some require self-registration.
We have ISO 27001. Are we done?
You are most of the way on the technical measures. NIS2 adds the reporting deadlines, management-body obligations and training, registration with the national authority, and specifics that vary by member state. Map the gap rather than assume.
Does NIS2 apply to our non-EU parent or suppliers?
Not directly, unless they provide in-scope digital services into the EU. But in-scope entities must manage supply-chain risk, so non-EU suppliers are asked for evidence and contractual commitments as a condition of business.
What is the relationship with DORA?
DORA is the sector-specific regulation for financial entities and takes precedence over NIS2 for them. Banks, insurers, investment firms and their critical ICT providers follow DORA; NIS2 applies to the other seventeen sectors.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.