SDG data protection blog

Laws & regulationIT security

NIS2 and ISO 27001: Is Certification Enough?

12 November 2026 by Sebastian Baier · Reading time approx. 10 minutes

No, not automatically. When implemented comprehensively, an ISMS based on ISO/IEC 27001 covers a large part of the measures required by Section 30 BSIG (the BSI Act) and is therefore a solid foundation for NIS2. However, the BSI (Federal Office for Information Security) makes clear that certification does not fulfil all legal requirements: the scope must cover the entire entity, risks may not be accepted at will, and registration, reporting deadlines and management's duties come on top.

Our recommendation is therefore: carry out a mapping. In our experience, an implemented ISMS based on ISO 27001 usually covers 90 to 95 % of the NIS2 requirements in this way. You then deal with the remaining open points one by one to achieve NIS2 compliance. This article shows how. You will find an overview of all NIS2 obligations on the page NIS2 consulting.

What the BSI says about ISO 27001 and NIS2

In April 2026 the BSI published a one-pager on ISO/IEC 27001 in the context of NIS2/BSIG. The key statements:

  • ISO 27001 certification can be a solid foundation and, when implemented comprehensively, regularly covers a large part of the measures under Section 30 BSIG.
  • However, it does not automatically fulfil all legal requirements.
  • The way to implement is open. Responsibility for the level of security required by law lies entirely with company management.

The BSI's recommended course of action: check applicability, assess the degree of implementation, close gaps systematically, document management responsibility and ensure that evidence can be provided to the BSI.

On its information page on NIS2 and ISO 27001, the BSI is even clearer:

  • An ISO 27001 certificate cannot serve as evidence of NIS2 compliance within the meaning of Section 61 BSIG, because it covers the requirements of Sections 30, 31, 32 and 38 BSIG only partly or not at all.
  • It is, however, a structured starting point that can significantly reduce the effort for NIS2.
  • The BSI recommends that companies already certified check their scope, carry out a gap analysis against Section 30 BSIG and add missing elements.

Where ISO 27001 covers NIS2

The greatest advantage of ISO 27001 lies not in individual controls, but in the management system. This is exactly what many companies lack when they try to implement NIS2 with individual measures:

ISO/IEC 27001:2022 Benefit for NIS2
Clause 4: context and scope legal requirements such as the BSIG are recorded systematically
Clause 5: leadership role of management, policy, responsibilities
Clauses 6 and 8: risk assessment and risk treatment basis for "appropriate, proportionate, effective" under Section 30 (1) BSIG
Statement of Applicability justified selection of measures that can be audited
Clause 7.5: documented information fulfils the documentation obligation under Section 30 (1) sentence 3 BSIG
Clause 9: internal audits, management review assessing effectiveness (Section 30 (2) No. 6 BSIG), monitoring by management
Clause 10: improvement adaptation to new risks and the state of the art

Mapping: Section 30 BSIG and ISO 27001 in detail

With a mapping, you assign each minimum measure under Section 30 (2) BSIG to the existing clauses and controls of your ISMS. This lets you see quickly what is already covered and which points remain open.

  • 90 to 95 % of the NIS2 requirements are covered by an implemented ISMS based on ISO 27001 through the mapping, in our experience

The BSI also provides a simplified mapping of the ten minimum measures to ISO/IEC 27001:2022 on its information page. It is based on an analysis by ENISA and the NIS Cooperation Group and is for information only. The BSI does not give a coverage percentage. The overview of Annex A of ISO 27001 shows which controls are behind it, and you will find the individual measures in the NIS2 checklist. Our overview, with notes on what to look out for with NIS2:

Section 30 (2) BSIG ISO/IEC 27001:2022 (selection) What to look out for with NIS2
No. 1 risk analysis, security policies Clauses 6.1, 8.2, A.5.1 risk analysis for all services of the entity, all-hazards approach
No. 2 incident handling A.5.24 to A.5.28 add criteria for "significant" and reporting deadlines of 24 h / 72 h / 1 month
No. 3 business continuity A.5.29, A.5.30, A.8.13, A.8.14 explicitly cover crisis management and emergency communication
No. 4 supply chain A.5.19 to A.5.23 record direct suppliers and service providers in full
No. 5 acquisition, development, maintenance, vulnerabilities A.8.8, A.8.25 to A.8.29 handling of reported vulnerabilities and disclosure
No. 6 assessing effectiveness Clause 9, A.5.35 report results to management, document monitoring
No. 7 training and awareness Clauses 7.2, 7.3, A.6.3 management training under Section 38 (3) BSIG is additional
No. 8 cryptography A.8.24 review the state of the art regularly
No. 9 human resources, access control, assets A.5.9, A.5.15 to A.5.18, A.6.1 to A.6.6, A.8.2 recertify authorisations regularly
No. 10 MFA, secured communication A.8.5, A.5.14 explicitly provide for secured emergency communication

For certain digital providers, such as cloud services, data centres and managed service providers, the detailed requirements of Implementing Regulation (EU) 2024/2690 also apply. They take precedence over the general catalogue and should be considered separately in the mapping.

The five gaps between ISO 27001 and NIS2

1. Scope

With ISO 27001, the company defines the scope itself, for example only one data centre or one product line. Section 30 BSIG, by contrast, requires measures for the entire regulated entity and all systems it uses for its services. A narrowly scoped certificate therefore only partly covers NIS2.

2. Risk acceptance

ISO 27001 allows risks to be accepted or transferred, for example to an insurer. According to the BSI, blanket risk acceptance and risk transfer are ruled out under the BSIG. You may only accept risks that are not relevant to your services. Decisions for or against measures must be justified in a way that is traceable and can be audited.

3. Registration

Registration with the BSI under Section 33 BSIG is not part of the standard. It has to be carried out in addition. Details in the article NIS2 registration with the BSI.

4. Reporting deadlines

ISO 27001 requires incident management, but no reporting to authorities. The deadlines under Section 32 BSIG (24 hours, 72 hours, one month) and the criteria for a significant security incident must be added. More in the article NIS2 reporting obligations.

5. Management and training

ISO 27001 requires leadership and commitment from top management. The BSIG goes further: the duty to implement and monitor, liability under company law and a regular training obligation for all members of management (Section 38 BSIG). More in the article NIS2 and management.

How to extend an existing ISMS to NIS2

  1. Clarify applicability and category Particularly important or important entity? See Checking NIS2 applicability.
  2. Check the scope Does the ISMS cover all services, sites and systems of the regulated entity? If not, extend it.
  3. Include the BSIG as a legal requirement in the context and interested parties (Clause 4), with reference to the specific sections.
  4. Add to the mapping and the Statement of Applicability Assign each minimum measure under Section 30 (2) BSIG to one or more controls and close the gaps.
  5. Revise the risk acceptance criteria with a view to the requirements of the BSIG.
  6. Extend the reporting process Assessment criteria, deadlines, responsibilities, templates, exercises.
  7. Involve management Reporting lines, recorded decisions, training plan with evidence.
  8. Registration Complete it if you have not already done so.
  9. Internal audit and management review Extend them to include the BSIG requirements.

No ISMS yet? How to proceed

If you are starting from scratch, you should tackle NIS2 and ISO 27001 together rather than one after the other: the ISMS is built from the outset with the BSIG as a legal requirement, a scope covering the entire entity and the reporting deadlines. Whether this ends with certification is a separate decision: ISO 27001 certification is not mandatory for NIS2. An ISMS based on ISO 27001 without a certificate saves a fair amount of cost, for example for certification and surveillance audits. However, some customers or insurers require a certificate, and you should check this in detail. The article ISO 27001 certification shows when an ISMS without a certificate is sufficient.

Depending on the use case, an ISMS without certification or an implementation based on BSI IT-Grundschutz (the BSI's baseline protection methodology) may also be the more suitable route, for example for smaller important entities. Also check whether there is an industry-specific security standard (B3S) for your sector: particularly important entities and their industry associations can propose such standards, and the BSI determines whether they are suitable (Section 30 (8) BSIG). A B3S adds specific industry requirements to the ISMS; there is no obligation to apply one. The page ISO 27001 consulting describes the roadmap to an ISMS and the models for working together.

How SDG supports you

  • Applicability assessment together with lawyers from our team
  • Mapping of an existing ISMS against Section 30 BSIG with a prioritised action plan for the open points, through to NIS2 compliance
  • Building an ISMS based on ISO 27001 with integrated NIS2 requirements, as an all-inclusive package or classic consulting
  • Reporting process and management training under the BSIG
  • External information security officer who steers the ISMS and NIS2 obligations on an ongoing basis: external information security officer
  • Friendly audit as a dress rehearsal before certification audits or supervisory audits

Frequently asked questions about NIS2 and ISO 27001

Is ISO 27001 certification enough for NIS2?

Not automatically. According to the BSI, when implemented comprehensively it covers a large part of the measures under Section 30 BSIG, but does not fulfil all requirements. In particular, a scope covering the entire entity, registration, reporting deadlines and management's duties must be added.

Is ISO 27001 mandatory for NIS2?

No. The BSIG does not prescribe a specific standard and leaves the way to implement open. However, it does require relevant standards to be taken into account. ISO 27001 is the obvious basis for this.

Why is an ISO 27001 certificate with a narrow scope not enough?

Because Section 30 BSIG requires measures for the entire regulated entity and all systems it uses for its services. A certificate that only covers one site or one department leaves the rest of the entity uncovered.

What is missing from ISO 27001 compared with NIS2?

According to the BSI, mainly the registration obligation, the statutory reporting deadlines, management's responsibility and its training obligation. In addition, ISO 27001 allows more extensive risk acceptance than the BSIG.

Does the BSI recognise ISO 27001 certificates as evidence?

Not as evidence of NIS2 compliance. According to the BSI, an ISO 27001 certificate cannot serve as evidence within the meaning of Section 61 BSIG, because it covers the requirements of Sections 30, 31, 32 and 38 BSIG only partly or not at all. It remains valuable as a starting point.

Should I implement NIS2 first and then ISO 27001?

It is better to do both together. An ISMS that takes the BSIG into account as a legal requirement from the outset avoids duplicate work. Whether to certify afterwards can be decided separately.

How much of NIS2 does ISO 27001 cover?

The BSI does not give a percentage. In our experience, an implemented ISMS based on ISO 27001 usually covers 90 to 95 per cent of the NIS2 requirements. We therefore recommend a mapping against Section 30 BSIG. You then deal with the remaining open points, such as registration, reporting deadlines and management's duties, one by one.

Sources: BSI: ISO/IEC 27001 in the context of NIS2/BSIG (version 1.0, 1 April 2026, in German), BSI: NIS2 and ISO 27001 (information package with mapping, in German), Section 30 BSIG, ISO/IEC 27001:2022

Note: This article provides general information and does not replace legal advice in individual cases.