IMScollect
Blue file folder and project plan in front of a clearly visible pair of scales as a symbol of the law, on a light background.
Template

NIS2 with ISO 27001: project plan, gap analysis, reporting

Implementing NIS2 with ISO 27001: an XLSX project plan with gap analysis, action management, evidence and management reporting for companies.

ISO 27001Legal requirementsRisks & opportunitiesProcesses & documentation
Philipp Kappe

Philipp Kappe

Founder of IMScollect

Published 21 September 2026
Contents

ISO/IEC 27001:2022 covers many NIS2 risk management topics. However, it replaces neither the legal applicability assessment nor registration, statutory reporting channels or the responsibility of the management body. This XLSX template makes exactly this dividing line something you can work with.

Since when NIS2 has applied in Germany

The German NIS2 Implementation Act (NIS-2-Umsetzungsgesetz) was promulgated on 5 December 2025 and, as a rule, entered into force on 6 December 2025. The core obligations for important and particularly important entities are set out in the amended BSI Act (BSI-Gesetz, BSIG). Companies must assess for themselves whether they are affected. Decisive factors include the type of entity, sector, size and, where applicable, the classification of affiliated companies.

A blanket statement such as “ISO 27001 fulfils NIS2” therefore falls short. An ISMS can considerably speed up technical and organisational implementation. Whether the law applies and which statutory procedural obligations must be met is, however, not answered by certification.

Where ISO/IEC 27001:2022 effectively supports NIS2

Section 30 BSIG requires appropriate, proportionate and effective technical and organisational measures. The ten statutory topic areas overlap significantly with an ISMS under ISO/IEC 27001:2022.

NIS2/BSIG topicContribution of ISO/IEC 27001:2022What still needs to be checked
Risk analysis and security conceptRisk assessment, risk treatment and documented ISMS frameworkNIS2 scope, services concerned and statutory proportionality criteria
Security incidentsRoles, detection, assessment, response and learning from incidentsBSI reporting channel, statutory reporting decision and deadlines
Business continuityBackup, recovery, emergency preparedness and continuityspecific criticality of the regulated services and robust exercises
Supply chainSelection, management and monitoring of suppliersdirect suppliers, criticality of services and additional sector-specific requirements
Secure procurement and developmentSecurity requirements, secure development and vulnerability managementmore detailed statutory or sector-specific requirements, where applicable
Effectiveness assessmentMetrics, internal audit, management review and improvementauthority-specific evidence and audit-ready documentation
Training and awarenessCompetence and awareness processesseparate regular training of the management body under Section 38 BSIG
Cryptography, access and MFAAppropriate Annex A controls and risk-based implementationspecific coverage, state of the art and evidence required by law

The most important strength of the standard is not any single control. It creates a repeatable management process: assessing risks, defining measures, appointing responsible people, maintaining evidence and checking effectiveness.

Two limits must be explicitly checked here. First, the certified ISMS scope may be narrower than the legally covered entity and the systems, sites and outsourced processes used for its services. Second, a risk acceptance documented in the ISMS does not automatically replace the obligation to implement appropriate, proportionate and effective measures under the BSIG. Scope deviations and accepted risks therefore belong in the gap analysis as separate check points.

Which NIS2 obligations lie outside ISO certification

Applicability and registration

Classification as an important or particularly important entity follows from the law, not from the certificate. Registration with the Federal Office for Information Security (BSI) with the required master data is also a separate legal obligation. Anyone who is already affected and has not yet registered should not let an ongoing ISMS project delay registration. The article on the missed NIS2 registration deadline explains the separate need for action.

Statutory reporting of security incidents

A working incident response process is the foundation, but is not enough on its own. For significant security incidents, Section 32 BSIG provides for an early warning no later than 24 hours after becoming aware, an incident notification no later than 72 hours and, as a rule, a final report no later than one month after the 72-hour notification. This requires a clear reporting decision, reachable responsible people, portal access, approved content and robust deadline management.

Responsibility of the management body

The management body must implement the risk management measures and monitor their implementation. In addition, there is a regular training obligation. Management review and leadership responsibility under ISO/IEC 27001:2022 help with this, but they do not automatically demonstrate that the statutory obligation has been met.

Supervision, evidence and special rules

ISO audits, internal audits and a certificate can provide valuable evidence. The form, scope and occasion of statutory evidence are nevertheless determined by the BSIG and, where applicable, further regulations. For certain types of digital entity, Implementing Regulation (EU) 2024/2690 also takes precedence. It does not apply across the board to every NIS2 company.

What the project plan in Excel contains

The template translates the overlap between law and standard into seven work areas:

  1. Applicability assessment: document legal entities, sectors, size criteria, affiliated companies, type of entity and registration status.
  2. NIS2/ISO mapping: assess 16 mandatory topics with legal source, ISO support, remaining gap, priority and evidence.
  3. Action plan: manage work packages, responsible people, start, target date, status, progress, dependencies and evidence.
  4. Management dashboard: see open mandatory topics, implementation status, overdue actions and progress at a glance.
  5. Evidence register: bring together documents, responsible people, storage locations, review status and next reviews.
  6. Incident management: keep traceable records of the time of awareness, the 24-hour, 72-hour and one-month deadlines and the reporting status.
  7. Sources and notes: open the official legal and authority sources used directly from the workbook.

Input cells are colour-coded. Formulas and drop-down fields are prepared. Sheet protection prevents accidental changes to formulas, but is expressly not a technical safeguard against manipulation.

How to use the template effectively

Do not start with the control list, but with applicability and scope. Then rate each mandatory topic as implemented, in progress, not started, not assessed or not applicable. Link open items to a specific action and at least one expected piece of evidence.

As a next step, the management body should confirm priorities, resources and target dates. The dashboard is suitable for the regular status report. Roles, action tracking, internal audits and management review can be managed jointly, while the subject-specific and statutory criteria remain clearly separated.

The template is intended as a working basis. The legal classification, sector-specific special rules and the specific state of the art must be checked for each company and kept up to date.

Conclusion

ISO/IEC 27001:2022 is a strong foundation for NIS2, but not a free pass. If you use the processes of the standard and separately add the independent obligations from the BSIG, reporting procedures and, where applicable, sector-specific requirements, you get a robust path to implementation. IMScollect can later bring actions, responsibilities, evidence and effectiveness reviews together in a shared management system structure.

Frequently asked questions

Is ISO 27001 certification enough to comply with NIS2?▾

No. ISO/IEC 27001:2022 supports many technical and organisational risk management measures. The applicability assessment, BSI registration, statutory reporting obligations, obligations of the management body and any sector-specific requirements must still be met separately.

Which German laws implement NIS2?▾

In Germany, Directive (EU) 2022/2555 was implemented primarily through the NIS2 Implementation Act (NIS-2-Umsetzungsgesetz) and the amended BSI Act (BSIG). Further national and European rules may apply to individual sectors or types of entity.

Which reporting deadlines apply to a significant security incident?▾

Section 32 BSIG generally provides for an early warning no later than 24 hours after becoming aware, an incident notification no later than 72 hours and a final report no later than one month after the 72-hour notification. If the incident is still ongoing, a progress report is required first.

What does the NIS2 project plan in Excel contain?▾

The XLSX contains an applicability assessment, NIS2/ISO mapping, action plan, management dashboard, evidence register, incident and deadline management and linked official sources.

Does the template replace legal advice?▾

No. It structures assessment, implementation and evidence. Legal applicability, sector-specific special rules and the appropriate measures must be checked for the specific company.

Sources