Resources › Legislation › NIS2
LEGISLATION

NIS2 Directive

The Network and Information Security Directive

The NIS2 Directive (Directive (EU) 2022/2555) establishes a common cybersecurity framework across the European Union. It replaced the original NIS Directive and extended cybersecurity obligations to more sectors and organisations. In particular, these obligations include risk management, incident reporting, governance and supervision.

In total, NIS2 covers entities across 18 critical sectors. These include energy, transport, health, digital infrastructure and ICT service management. Public administration, manufacturing and other critical activities are also covered.

NIS2 is an EU directive rather than a single compliance law applied identically in every Member State. Each Member State must transpose NIS2 into national legislation. Article 5 also allows countries to adopt or retain stronger cybersecurity rules than those in the Directive. Organisations therefore need to understand both the EU framework and the national law that applies to them.

Publication date 6 October 2026
Legal reference Directive (EU) 2022/2555
Transposition deadline 17 October 2024
01

What is NIS2 and why is it important?

The objective of NIS2 is to achieve a high common level of cybersecurity across the EU. To achieve this, Member States must establish national cybersecurity strategies and competent authorities. They must also designate single points of contact and CSIRTs. The Directive imposes cybersecurity risk-management and incident-reporting duties on essential and important entities.

It also introduces rules for supervision, enforcement, and cybersecurity information sharing.

KEY POINT

NIS2 makes cybersecurity a management responsibility, not just an IT issue.

Under Article 20, management bodies of essential and important entities must approve cybersecurity risk-management measures. They must also oversee implementation and receive cybersecurity training. Compliance therefore requires clear responsibilities and active management involvement.

Compared with its predecessor, NIS2 therefore has a broader scope and applies to more sectors and organisations. The European Commission describes NIS2 as covering 18 critical sectors. In general, the framework applies to medium-sized and large entities operating in those sectors. The Directive also contains exceptions that bring certain organisations into scope regardless of size.

NIS2 makes cybersecurity a responsibility beyond the IT department. Article 20 requires the management bodies of essential and important entities to approve cybersecurity risk-management measures and oversee their implementation. Management bodies must also receive cybersecurity training. In addition, Member States must encourage regular employee training.

In addition, the enforcement framework is significant. Member States must provide for administrative fines for infringements of Articles 21 or 23. For essential entities, the maximum must be at least €10 million or 2% of worldwide annual turnover, whichever is higher. For important entities, the maximum must be at least €7 million or 1.4% of worldwide annual turnover, whichever is higher. However, national law sets out the precise enforcement process.

Member States had to transpose NIS2 by 17 October 2024. However, implementation has not progressed at exactly the same pace across the EU. On 8 July 2026, the European Commission referred four Member States to the Court of Justice of the EU. These were Ireland, Spain, France and the Netherlands. At that time, they had not notified full transposition. Therefore, organisations operating internationally should check the current national position. They should not rely solely on the Directive’s text.

02

Does NIS2 apply to your organisation?

The first question is not simply whether your organisation “does cybersecurity”. Instead, applicability depends on the type of activity, the entity’s size, and specific exceptions or national rules.

1

Check your sector

NIS2 applies to entity types listed in Annex I and Annex II. Annex I covers sectors of high criticality, including energy, transport, banking and financial market infrastructure. It also covers health, drinking water, wastewater, digital infrastructure, ICT service management, public administration and space. Annex II covers additional critical sectors. They include postal and courier services, waste management, chemicals, food, certain manufacturing activities, digital providers and research.
2

Check the size criteria

Under Article 2, NIS2 generally covers medium-sized enterprises and larger entities in Annex I or II. The applicable size ceilings come from the EU SME rules. This distinction matters because the EU SME classification considers financial and organisational factors. It does not rely on a single employee threshold.
3

Check the exceptions

Some organisations fall within the Directive regardless of size. Examples include certain public electronic communications network or service providers, trust service providers, top-level domain registries and DNS service providers. Member States can also designate entities as critical based on their importance to public safety or public health. Systemic risk and essential economic or societal activities may also be relevant.
4

Essential or important entity?

NIS2 distinguishes between essential and important entities. Classification depends on the sector, size, and several special rules. For example, Article 3 treats certain larger Annex I entities as essential. Qualified trust service providers, TLD registries and DNS service providers can also be essential regardless of size. Other in-scope entities that do not meet the essential-entity criteria generally fall into the important category. The distinction mainly affects supervision and enforcement. However, both categories face the core cybersecurity risk-management and incident-reporting requirements.
5

Finally, check the national law

This step is essential. NIS2 is a minimum-harmonisation directive, so Member States may introduce stricter cybersecurity provisions. Registration procedures, competent authorities, national reporting systems, supervisory practices, and other implementation details can therefore differ. For a group operating in several EU countries, assess each relevant entity under its applicable national implementing legislation. The requirements may differ between jurisdictions.
03

Key requirements of NIS2

Management responsibility and training

Cybersecurity governance starts at management level. Management bodies of essential and important entities must approve cybersecurity risk-management measures and oversee their implementation. In addition, management bodies must receive training to understand cybersecurity risks. They must also assess how those risks could affect the organisation’s services.

Approval
management approval and oversight of cybersecurity measures
Training
required for management bodies
21
Article

Cybersecurity risk management

Article 21 requires essential and important entities to adopt appropriate and proportionate technical, operational and organisational measures. These measures must manage risks to network and information systems and prevent or minimise incident impacts. Moreover, measures must reflect the organisation’s exposure to risk and the potential consequences of incidents.

Incident handling and business continuity

Risk-management measures must include incident handling as well as business continuity. For example, the Directive refers to backup management, disaster recovery and crisis management. Organisations therefore need to define responsibilities, escalation procedures and recovery arrangements rather than relying only on preventive controls.

Supply chain security

NIS2 explicitly includes supply chain security, which covers cybersecurity aspects of relationships with direct suppliers and service providers. An organisation’s assessment should therefore cover external dependencies as well as internal systems. These dependencies can affect the security or continuity of services.

Secure acquisition, development and vulnerability management

Article 21 also covers security in the acquisition, development and maintenance of network and information systems. This includes vulnerability handling and disclosure. This connects cybersecurity requirements with procurement, software development, maintenance, and vulnerability management processes.

Cyber hygiene, access control and authentication

The Directive requires basic cyber hygiene and training. It also requires policies and procedures for cryptography and encryption. Human resources security, access control policies and asset management are also covered. It also includes the use of multi-factor authentication or continuous authentication solutions where appropriate.

23
Article

Significant incident reporting

Importantly, NIS2 does not require the full regulatory reporting process for every minor security event. Under Article 23, an incident is significant when it causes or could cause severe operational disruption or financial loss. It also qualifies when it causes or could cause considerable material or non-material damage to others.

For significant incidents, the Directive sets three reporting stages. An early warning is due within 24 hours of awareness. An incident notification follows within 72 hours. A final report is due within one month after that notification. In addition, the competent authority may request intermediate reports.

Additional requirements for certain digital entities

For certain digital infrastructure, ICT service management and digital provider entities, Commission Implementing Regulation (EU) 2024/2690 sets additional requirements. In particular, it details technical and methodological measures and criteria for identifying significant incidents.

04

Path to compliance

A practical implementation programme can follow eight steps.

SCOPE

Determine scope and applicable national law

Identify the relevant legal entity, sector and services. Check size and special exceptions, then determine whether the entity is essential or important. Then identify the national legislation implementing NIS2 and the competent authority.

GOVERNANCE

Establish governance and ownership

Define the management body that approves cybersecurity measures. Assign owners for individual risks, controls, regulatory reporting and incident reporting.

ASSETS

Map assets, services, and dependencies

Identify the systems, information, applications, infrastructure, business processes and external providers required to deliver in-scope services.

RISKS

Perform risk and business impact assessments

Assess threats, vulnerabilities, potential disruption, and dependencies. Use the results to prioritise controls and continuity requirements rather than treating every system identically.

CONTROLS

Assess controls against Article 21

Review existing controls for incident management, continuity, backups, supply chain security and vulnerability management. Also examine access control, cryptography, training and other required areas. Article 21 requires measures to be appropriate and proportionate to risk.

REPORTING

Establish the incident-reporting process

Organisations should define who decides whether an incident is significant and who contacts the relevant CSIRT or authority. They should also specify which information to collect and how to meet the 24-hour and 72-hour deadlines.

TESTING

Test continuity and response

For this reason, teams should test their plans in practice. Tests should cover backups, recovery, crisis roles and internal and external communication procedures.

REVIEW

Review effectiveness and retain evidence

Maintain risk assessments, decisions, assigned responsibilities, completed actions, tests and training records. Keep other evidence that shows how the organisation manages cybersecurity measures.

For entities covered by Implementing Regulation 2024/2690, ENISA’s NIS2 Technical Implementation Guidance offers practical support. It includes examples of evidence and mappings to relevant standards and frameworks. ENISA published the guidance in June 2025.

05

How can Blue Octopus help?

Blue Octopus does not replace technical cybersecurity controls, a legal assessment, a competent authority, or an independent audit. Its role is in helping organisations structure the management layer around risks, analyses, responsibilities, and supporting documentation.

NIS2 area
How Blue Octopus can support it
Risk management
Structure, assess and prioritise risks
Ownership
Assign risks and actions to responsible owners
Analysis
Connect findings with risks and priorities
Documentation
Organise relevant documentation alongside analyses and risks
Management overview
Maintain visibility of priorities, responsibilities and open actions
Improvement actions
Track findings and corrective actions over time

Using a management platform does not demonstrate NIS2 compliance. The underlying risk assessments, cybersecurity measures, procedures and evidence still need to satisfy the applicable EU and national requirements.

06
FAQ

Frequently asked questions

Short answers to the most common questions about the scope and requirements of NIS2.

No. Medium-sized and larger organisations in covered sectors form the general scope. However, Article 2 also covers certain entities regardless of size.

Both are subject to core NIS2 requirements, but the Directive distinguishes them for classification, supervision and enforcement. Article 3 sets out the detailed classification rules.

Not by itself. ISO/IEC 27001 provides a framework for an information security management system (ISMS). However, NIS2 adds specific legal duties for governance, risk management, reporting and supervision. Organisations must therefore assess compliance against the applicable NIS2 requirements and national law.

A supplier may or may not independently fall within NIS2. However, in-scope organisations must address supply chain security and their relationships with direct suppliers and service providers. These requirements can also affect suppliers through contracts.

No. The staged Article 23 reporting process applies to significant incidents. The Directive sets the general significance criteria. Meanwhile, Implementing Regulation 2024/2690 adds detailed criteria for certain categories of digital entities.

No. NIS2 is a minimum-harmonisation directive. Member States may impose a higher level of cybersecurity and implement national procedures, authorities, and enforcement arrangements. Organisations should therefore verify the applicable national transposition law.

07

Official sources

08

Next step

NIS2 readiness requires more than a cybersecurity policy. Organisations need a repeatable process that connects risks, critical services, responsible owners, suppliers, controls, incident response and evidence of implementation.

Blue Octopus can help organisations structure risks, analyses, responsibilities and supporting documentation in one place. This gives management a clearer view of outstanding work and responsibility.