Implementation Guide 8 min read· 16 October 2026

NIS2 and ISO/IEC 27001: Reuse Controls, Check Legal Gaps

See how ISO/IEC 27001 supports NIS2 risk management, and where legal and reporting gaps remain. Start with the free documentation kit.

Aegora GRC Advisory Team

ISO/IEC 27001 implementation guidance

The Network and Information Security Directive (NIS2) has significantly raised the stakes for cybersecurity across the European Union. Replacing the original 2016 NIS Directive, NIS2 expands the scope of covered entities and introduces stricter security requirements, mandatory reporting timelines, and management accountability under applicable national rules.

For organisations already maintaining an Information Security Management System (ISMS) based on ISO/IEC 27001, the transition to NIS2 is not a leap into the unknown. Instead, it is an exercise in alignment. This article explores how the ISO/IEC 27001 control set overlaps with NIS2 obligations and how practitioners can leverage their existing documented ISMS to address the same risk areas.

What is NIS2?

NIS2 (Directive (EU) 2022/2555) is the EU's latest legislative framework designed to achieve a high common level of cybersecurity across the Union. It applies to "Essential" and "Important" entities across sectors such as energy, transport, banking, health, and digital infrastructure.

The directive mandates that these entities implement "appropriate and proportionate technical, operational and organisational measures" to manage cybersecurity risks. Its practical application depends on the entity, sector and national implementing law. Assess scope and obligations with qualified legal advice rather than relying on a certification badge.

The Synergy: ISO/IEC 27001 as a Foundation

ISO/IEC 27001 is the international standard for information security management. While NIS2 is a legal directive and ISO/IEC 27001 is a voluntary standard, they share the same DNA: a risk-based approach to security.

In many cases, the requirements of NIS2 Article 21—which lists the minimum security measures required—can be mapped directly to the Annex A controls of ISO/IEC 27001:2022. This offers a useful starting point for reviewing reusable controls, but a mapping does not establish that every legal requirement is addressed or operating effectively.

1. Risk Management and Information Security Policies

NIS2 Article 21(2)(a) requires policies on risk analysis and information system security. This is the bedrock of ISO/IEC 27001.

How it overlaps: ISO/IEC 27001 requires the establishment of a risk management framework (Clause 6.1) and the documentation of security policies.

Relevant Controls: A.5.1 — Information Security Policies addresses this risk area by ensuring that policies are defined, approved, and communicated.

2. Incident Management and Reporting

Article 21(2)(b) focuses on incident handling. This is where NIS2 adds significant prescriptive weight, particularly through Article 23 reporting obligations for significant incidents. The general deadlines run from awareness: a 24-hour early warning and a 72-hour incident notification, subject to the applicable rules and specific exceptions.

How it overlaps: ISO/IEC 27001 focuses on the readiness and response capability.

Relevant Controls: A.5.24 — Information Security Incident Management Planning addresses the requirement for a structured response. While ISO/IEC 27001 does not mandate the 24-hour reporting window, it provides the process (A.5.26 and A.5.28) necessary to identify and report incidents to authorities.

3. Business Continuity and Crisis Management

NIS2 Article 21(2)(c) mandates business continuity, such as backup management and disaster recovery.

How it overlaps: This area addresses the 'Availability' pillar of the CIA triad.

Relevant Controls: ISO/IEC 27001 covers this through A.5.29 (Information security during disruption) and A.5.30 (ICT readiness for business continuity). These controls ensure that the organisation has documented procedures to maintain operations during an incident.

4. Supply Chain Security

Supply chain security is a major pillar of NIS2 (Article 21(2)(d)), requiring organisations to assess the security of their suppliers and service providers.

How it overlaps: ISO/IEC 27001 includes a dedicated section for supplier relationships.

Relevant Controls: A.5.19 (Information security in supplier relationships) and A.5.21 (Managing information security in the ICT supply chain) cover this area. They require organizations to define and implement security requirements for suppliers, addressing the same risk area as NIS2.

5. Cryptography and Encryption

Article 21(2)(h) requires policies and procedures regarding the use of cryptography and, where appropriate, encryption.

How it overlaps: Both frameworks recognize encryption as a primary technical safeguard.

Relevant Controls: A.8.24 (Use of cryptography) addresses the management of cryptographic keys and the implementation of encryption across the estate.

6. Access Control and Asset Management

NIS2 Article 21(2)(i) covers human resources security, access control policies, and asset management.

How it overlaps: ISO/IEC 27001 provides a granular set of controls for the entire employee lifecycle and technical access.

Relevant Controls: A.5.15 — Access Control Policy ensures that access is granted on a need-to-know basis. This is supported by controls like A.5.16 (Identity management) and A.8.2 (Privileged access rights).

7. Vulnerability Management

NIS2 Article 21(2)(e) expressly addresses security in acquisition, development and maintenance, including vulnerability handling and disclosure. Article 21(2)(f) addresses assessment of the effectiveness of cybersecurity risk-management measures.

How it overlaps: Modern ISMS practitioners treat vulnerability management as a core operational requirement.

Relevant Controls: A.8.8 — Management of Technical Vulnerabilities supports the same vulnerability risk-management area. It requires organisations to obtain information about technical vulnerabilities of information systems and take appropriate measures.

The Regulatory Radar: Visualising Your Coverage

Understanding the overlap is easier when you can see it. On the Blueprint platform, the regulatory radar provides an indicative mapping of how your ISO/IEC 27001 control set addresses other frameworks.

The public radar assumes all 93 Annex A controls are implemented. The signed-in dashboard instead uses your self-reported Statement of Applicability status. Both use Secure Controls Framework (SCF) mappings to indicate overlap, not to determine whether your organisation is meeting NIS2 obligations. Legal scope, national reporting routes and operating evidence need separate review. This "single set of controls" approach prevents the duplication of effort and ensures that your compliance program scales with your business.

Important Caveats

While the overlap is significant, organisations must be aware of two critical distinctions:

1. Certification is not Compliance: Achieving ISO/IEC 27001 certification does not automatically constitute NIS2 compliance. NIS2 is a legal obligation with specific jurisdictional requirements (such as registering with national authorities) that go beyond the scope of a standard audit.

2. Reporting Obligations: NIS2 is much more prescriptive about *when* and *to whom* you must report incidents. ISO/IEC 27001 requires you to have a process for reporting, but NIS2 dictates the clock (24 hours for the early warning). Your ISMS must be updated to include these specific legal timelines.

Check the reporting workflow against national requirements

The official NIS2 directive is the starting point, together with the law and competent authority guidance applicable to your entity. Article 23 generally requires a final report within one month of the incident notification. If the incident is still ongoing, the reporting sequence includes a progress report and a final report after handling is completed. Trust service providers have a specific 24-hour incident-notification rule. Your response procedure must therefore identify the applicable path rather than assume that every entity follows identical timing.

Record who decides whether an incident is significant, who starts the awareness timeline, who approves notifications and who acts as deputy. Test a scenario outside normal working hours. Confirm the actual submission channel and the information required; a telephone contact list alone does not prove that the team can prepare and submit the notice. Keep decisions and timestamps even when an event is assessed as not reportable.

Reuse evidence without overstating coverage

For each relevant legal requirement, identify the control activity, accountable owner and operational evidence. A supplier policy may support a requirement, but it does not prove that a critical supplier was assessed or that contract terms are enforceable. Link supplier relationships and ICT continuity to completed assessments and recovery exercises. Track gaps explicitly rather than colouring a requirement complete because a document exists.

Review the mapping after organisational or legal changes, and retain the rationale for the scope and applicability decisions. This separates reusable security work from the legal conclusions that require specialist judgement.

Conclusion

ISO/IEC 27001 can provide a structured foundation for organising NIS2-related security work. Because the standard addresses the same risk areas as the directive—risk management, incident handling, supply chain, and business continuity—it allows you to reuse relevant control activities while checking the additional legal requirements separately. By maintaining auditor-ready documents within a documented ISMS, you create a foundation that can withstand both certification audits and regulatory scrutiny.

Get the Free ISO/IEC 27001 Documentation Kit

Blueprint by Aegora GRC provides an editable documentation foundation for your ISMS. Our free kit includes 109 tailored documents, including 19 core documents flagged in the kit; the standard requires documented information rather than a fixed number of separate files.

109 Tailored Documents: Policies, procedures, and registers.

93 Annex A Controls: Fully mapped and ready for implementation.

Free with an account: No credit card, no trial limits, and no watermarks.

**Get Your Free Kit Now** | **Book a Free 1-Hour Consultation**

Start with the free documentation kit

Get 109 editable documents with a free account. Adapt them, implement selected controls and retain real evidence of operation.

More articles