- ClassificationCategoryCybersecurityDomainCybersecurityFramework FamilyOther
- Regulatory ContextTypeRegulationLegal InstrumentDirectiveSectorCross-SectorIndustryCross-Industry
- Region / PublisherRegionEuropean UnionRegion DetailEuropean UnionPublisherEuropean Parliament and Council of the European Union
- VersioningVersionDirective (EU) 2022/2555Effective DateJanuary 16, 2023 (entry into force); national measures apply from October 18, 2024Issue DateDecember 14, 2022 (signed); published December 27, 2022
- AdoptionAdoption ModelRegulatory ComplianceImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
The Directive is EU law published in the Official Journal and is included with the platform for reference.
Framework text is licensed by its publisher and is included only where stated above.
- The NIS2 Directive requires medium-sized and large entities in critical sectors to manage cybersecurity risk and report significant incidents.
- Adopted December 14, 2022, it replaced the 2016 NIS Directive; national measures apply from October 18, 2024.
- Entities are sorted into essential and important entities by sector, with some types in scope regardless of size.
- Significant incidents are reported within 24 and 72 hours, and management bodies approve the measures and can be held liable.
- Because transposition differs by country, organizations check the national law of each Member State where they operate.
Overview
The NIS2 Directive (Directive (EU) 2022/2555) requires medium-sized and large entities in sectors of high criticality and other critical sectors to manage cybersecurity risk, report significant incidents within 24 and 72 hours, and accept supervision, with management bodies held accountable. Member States had to adopt and publish national measures by October 17, 2024 and apply them from October 18, 2024.
The European Parliament and the Council adopted it on December 14, 2022 and it replaced the 2016 NIS Directive. Because it is a directive, each Member State enacts national law and a competent authority and CSIRT supervise it. It sorts in-scope organizations into essential and important entities (Article 3), listed by sector in Annexes I and II, with some types in scope regardless of size (Article 2(2)).
Entities apply the risk-management measures of Article 21, management approval and training under Article 20, the reporting steps of Article 23 and the supply chain checks Article 21(3) calls for, and they register with their authority where the national law requires it (Article 27).
Why does it matter?
NIS2 widens the earlier regime to many more sectors and sizes and ties the duties to named people: the management bodies approve the measures, oversee them and can be held liable (Article 20). Because transposition differs by country, an organization must check the national law of each Member State where it operates.
Key benefits include:
- A wide sector list
Annex I covers sectors of high criticality, such as energy, transport, banking, health, digital infrastructure and public administration. Annex II covers other critical sectors, such as manufacturing, food, chemicals and digital providers.
- Management accountability
Management bodies approve and oversee the risk-management measures, can be held liable for infringements and must train (Article 20).
- Ten minimum measures
Article 21(2) lists at least ten areas, from risk analysis policies to multi-factor authentication.
- A staged reporting duty
Significant incidents are reported through an early warning within 24 hours, a notification within 72 hours and a final report within one month (Article 23(4)).
- Fines with a floor
For essential entities the maximum fine is at least EUR 10 million or 2 percent of worldwide turnover, and for important entities at least EUR 7 million or 1.4 percent (Article 34).
How does it work?
The Directive sets duties for Member States and for entities. Member States adopt a national cybersecurity strategy (Article 7), designate competent authorities and single points of contact (Article 8) and CSIRTs (Article 10), and cooperate through the Cooperation Group and the CSIRTs network (Articles 14 and 15). Entities carry the obligations in Chapter IV: governance (Article 20), risk-management measures (Article 21), reporting (Article 23), use of certification schemes (Article 24) and the jurisdiction rules (Article 26).
Essential entities include those in Annex I that exceed the medium-sized ceilings, plus qualified trust service providers, top-level domain registries and DNS providers. Important entities are those in Annex I or II that do not qualify as essential. Supervision is stronger for essential entities, including ex ante supervision, while important entities face mainly ex post supervision (Articles 32 and 33).
An entity assesses whether it is in scope in each Member State, adopts the Article 21 measures proportionate to its risk and size, sets up incident detection and the Article 23 reporting chain, flows security requirements to suppliers, and keeps evidence for audits, inspections and requests for information.
Key Elements
- Scope and entity types (Articles 2 and 3)
Medium-sized and large entities in Annexes I and II, and some entities regardless of size, such as DNS and domain registries and providers of public electronic communications.
- Governance (Article 20)
Management bodies approve the cybersecurity risk-management measures, oversee them and follow training.
- Risk-management measures (Article 21)
Policies on risk analysis and system security, incident handling, business continuity, supply chain security, secure acquisition and development, effectiveness assessment, cyber hygiene and training, cryptography, human resources and access control, and multi-factor authentication.
- Incident reporting (Article 23)
Early warning in 24 hours, incident notification in 72 hours, an intermediate report on request and a final report within one month of the notification.
- Supervision and enforcement (Articles 31 to 36)
Inspections, audits, security scans and information requests, binding instructions, and administrative fines, with penalties for infringements that lead to personal data breaches addressed in Article 35.
- Registries and information sharing (Articles 27 to 30)
Registry of entities, domain name registration data, voluntary information-sharing arrangements and voluntary notification.
What does it cover?
NIS2 applies to public and private entities of the types listed in Annexes I and II that are medium-sized or larger and provide services or carry out activities in the Union, and, regardless of size, to certain entities such as DNS service providers, top-level domain registries, trust service providers and public electronic communications providers (Article 2). Member States may extend it to more entities. Where sector-specific Union acts impose risk-management or incident notification duties of at least equivalent effect, the corresponding NIS2 provisions do not apply (Article 4).
What are its objectives?
NIS2 aims for a high common level of cybersecurity across the Union.
Raise the cybersecurity risk management of entities in critical sectors.
Hold management bodies accountable for approving and overseeing the measures.
Standardize incident reporting to national authorities and CSIRTs.
Improve cooperation and information sharing between Member States.
Provide supervision and penalties that are effective, proportionate and dissuasive.
Framework in Context
NIS2 sits within the Union cybersecurity framework alongside the Cybersecurity Act and sector rules. For financial entities, DORA sets sector-specific ICT risk and incident rules, and Article 4 of NIS2 disapplies the corresponding NIS2 provisions where a sector act has equivalent effect. The Cyber Resilience Act protects products, while NIS2 protects the entities that operate services. Implementation differs by Member State because national laws transpose the Directive.
Common Framework Mappings
>Common Framework Mappings
Organizations map these complementary EU, international and US frameworks to NIS2 to harmonize controls, demonstrate cross-border compliance, simplify audits, and integrate data protection and resilience requirements.
Mapped frameworks include:
Directive (EU) 2016/1148 — NIS Directive
Digital Operational Resilience Act (DORA)
EU Cybersecurity Act (Regulation (EU) 2019/881)
General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679)
ISO/IEC 27001
ISO/IEC 27002
NIST Cybersecurity Framework
NIST SP 800-53
How SmartSuite Supports NIS2 Directive
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Compliance Management and Cyber & IT Risk to hold the Article 21 measures, management approvals and evidence for each in-scope Member State, Operational Resilience & Business Continuity for incident and recovery plans, and Third Party Risk Management for supplier security.
Scope and Entity Register
Record each legal entity, sector and size test, its essential or important status and the Member State laws that apply (Articles 2 and 3).
Article 21 Measure Library
Map each of the ten measure areas to controls, owners, evidence and review dates (Article 21(2)).
Management Approval and Training
Record management body approvals of the measures, training sessions and oversight reviews (Article 20).
Incident Reporting Workflow
Time significant incidents against the 24-hour early warning, 72-hour notification and one-month final report (Article 23).
Supplier Security Review
Assess direct suppliers' vulnerabilities and practices and record the results and contract terms (Article 21(3)).
Supervision and Findings
Keep authority requests, audit results, corrective measures and registry details for each Member State (Articles 27 and 31 to 33).
Related frameworks

DORA (Regulation (EU) 2022/2554) requires EU financial entities to manage ICT risk, report major incidents, test resilience and control ICT third-party risk, applying from January 17, 2025.

The GDPR (Regulation (EU) 2016/679) sets principles, lawful bases, individual rights and accountability duties for personal data, with fines up to EUR 20 million or 4 percent of turnover.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.
Frequently Asked Questions For EU NIS2 Directive (Network and Information Security Directive (EU) 2022/2555)
Public and private entities of the types in Annex I (sectors of high criticality) or Annex II (other critical sectors) that are medium-sized or larger and provide services or carry out activities in the Union. Some entities, such as DNS service providers, top-level domain registries, trust service providers and public electronic communications providers, are in scope regardless of size (Article 2).
Essential entities include Annex I entities that exceed the medium-sized ceilings and some entities regardless of size (Article 3(1)). Important entities are the other in-scope entities. Essential entities face stronger supervision (Articles 32 and 33) and higher maximum fines (Article 34).
Significant incidents are reported to the CSIRT or competent authority: an early warning within 24 hours of becoming aware, an incident notification within 72 hours, and a final report within one month of the notification (Article 23(4)). Trust service providers have a 24-hour notification duty for incidents affecting trust services.
Article 21(2) lists at least risk analysis and system security policies, incident handling, business continuity and crisis management, supply chain security, secure acquisition, development and maintenance, effectiveness assessment, cyber hygiene and training, cryptography, human resources and access control, and multi-factor authentication where appropriate.
Management bodies must approve the cybersecurity risk-management measures, oversee their implementation, follow training and can be held liable for infringements, subject to national law (Article 20).

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


