Germany NIS 2 Compliance Management
NIS 2 Compliance Management for Germany
Manage NIS 2 requirements, cybersecurity risks, controls, incidents and evidence in one structured GRC environment.
Request a demoWhat is NIS 2?
The NIS 2 Directive (EU) 2022/2555 establishes a common framework for a high level of cybersecurity across the European Union. It expands the scope of the original NIS Directive and introduces stronger requirements for cybersecurity risk management, incident reporting, business continuity, supply-chain security and management accountability.
In Germany, NIS 2 was implemented primarily through the NIS2 Implementation Act, which substantially revised the BSI Act (BSIG). The German implementation entered into force on 6 December 2025. Organisations should therefore assess their obligations against the applicable German legislation, rather than relying on the EU Directive alone.
NIS 2 is not simply an IT security checklist. It requires organisations to establish a demonstrable approach to managing cybersecurity risks, assigning responsibilities, implementing appropriate controls and maintaining evidence of compliance.
Who needs to consider NIS 2?
NIS 2 covers organisations operating in designated sectors and meeting the relevant applicability criteria. The assessment generally considers the organisation's sector, size and specific role in the provision of services. Certain entities may be covered regardless of size.
Essential entities
Organisations in particularly critical sectors and categories, subject to more intensive supervisory requirements.
Important entities
Other in-scope organisations that fall within the relevant sectors and applicability criteria.
Classification and applicability must be assessed against the current BSIG, including its sector definitions, thresholds, exceptions and special rules. A general company-size test alone is not sufficient.
Sectors covered by NIS 2
The Directive distinguishes between highly critical sectors and other critical sectors. Examples include:
Highly critical sectors
- Energy
- Transport
- Banking
- Financial market infrastructure
- Healthcare
- Drinking water
- Wastewater
- Digital infrastructure
- ICT service management
- Public administration
- Space
Other critical sectors
- Postal and courier services
- Waste management
- Chemicals
- Food production and distribution
- Manufacturing
- Digital providers
- Research organisations
These are sector examples, not a complete legal classification. The precise scope depends on the relevant legal definitions and national implementation.
Core NIS 2 requirements
NIS 2 requires in-scope organisations to implement appropriate and proportionate technical, operational and organisational measures to manage risks to the security of their network and information systems.
1. Risk analysis and security policies
Establish documented risk analysis processes, information security policies, risk ownership and a systematic approach to managing cybersecurity risks.
2. Incident handling
Define processes for detecting, recording, assessing, responding to and learning from cybersecurity incidents.
3. Business continuity
Prepare for disruption through backup management, disaster recovery, crisis management and tested continuity arrangements.
4. Supply-chain security
Assess cybersecurity risks arising from suppliers and service providers, including the security of relevant contractual and operational relationships.
5. Secure systems and vulnerability management
Address security throughout the acquisition, development, operation and maintenance of systems, including vulnerability handling and disclosure.
6. Effectiveness of security measures
Establish policies and procedures to assess whether cybersecurity risk-management measures are implemented and effective.
7. Cyber hygiene and training
Implement appropriate cyber hygiene practices and cybersecurity awareness and training for relevant personnel.
8. Cryptography and encryption
Establish appropriate policies and procedures for the use of cryptography and, where appropriate, encryption.
9. Access and asset management
Manage assets, access rights and human resources security to reduce the risk of unauthorised access and misuse.
10. Multi-factor authentication
Use multi-factor authentication or continuous authentication solutions, secure communications and emergency communication systems where appropriate.
Management accountability is a central requirement
NIS 2 makes cybersecurity a management responsibility. Management bodies must approve the cybersecurity risk-management measures and oversee their implementation. They must also undertake appropriate training and promote relevant training for employees.
In Germany, the revised BSIG contains specific management-related duties and liability provisions. Organisations should document decisions, responsibilities, oversight activities and the evidence supporting their cybersecurity measures.
Incident reporting and response
NIS 2 establishes a staged reporting process for significant incidents. Organisations need clear escalation paths, defined responsibilities and the ability to assess whether an incident meets the applicable reporting criteria.
Early warning
Initial early warning after becoming aware of a significant incident.
Incident notification
A more detailed incident notification, including an initial assessment.
Final report
A final report after the incident notification, subject to the applicable reporting rules.
These are the general NIS 2 reporting stages. The applicable national reporting channel, legal requirements, incident criteria and any sector-specific rules must be checked before operational use.
How Cetbix GRC supports NIS 2 management
NIS 2 compliance requires more than policies and isolated technical controls. Organisations need to connect obligations to risks, controls, accountable owners, evidence, incidents and improvement activities.
Requirements management
Maintain a structured register of NIS 2 and applicable national requirements, with links to internal policies, processes and controls.
Risk management
Identify, assess and prioritise cybersecurity risks. Assign risk owners, define treatments and track residual risks.
Control management
Document technical and organisational controls, responsible teams, implementation status and review cycles.
Evidence management
Connect policies, records, test results, approvals and other evidence to the requirements and controls they support.
Incident and action tracking
Track incidents, findings, corrective actions, owners, deadlines and follow-up activities in a consistent process.
Management reporting
Provide structured visibility into risk exposure, control status, open findings and progress against compliance objectives.
NIS 2 and related frameworks
NIS 2 can be managed alongside established security, risk and resilience frameworks. These frameworks can provide useful methods and control structures, but they do not automatically establish compliance with NIS 2 or the German BSIG.
ISO/IEC 27001
Provides an information security management system framework for managing information security risks, controls, responsibilities and continual improvement.
ISO/IEC 27002
Provides guidance on information security controls that can support the design and operation of NIS 2-related measures.
ISO 22301
Supports business continuity management, including preparedness, response, recovery and resilience.
ISO 31000
Offers principles and guidance for integrating risk management into organisational governance and decision-making.
BSI IT-Grundschutz
Provides a structured approach to information security management and implementation of security safeguards.
DORA
Establishes digital operational resilience requirements for financial entities. Its relationship with NIS 2 must be assessed under the applicable sector-specific rules.
Example: Mapping NIS 2 requirements to GRC controls
A structured mapping helps organisations demonstrate how legal requirements are translated into operational measures and verifiable evidence.
| NIS 2 topic | Example control | Evidence | GRC record |
|---|---|---|---|
| Risk analysis | Documented cybersecurity risk assessment | Risk register, assessment results, approvals | Risk and requirement |
| Incident handling | Incident response and escalation process | Incident records, exercise results, response plans | Process and evidence |
| Business continuity | Backup and recovery arrangements | Backup logs, recovery tests, continuity plans | Control and test |
| Supply-chain security | Security assessment of relevant suppliers | Supplier assessments, contracts, review records | Third-party risk |
| Access control | Role-based access and periodic access reviews | Access lists, review approvals, access logs | Control and evidence |
| Training | Cybersecurity awareness programme | Training records, attendance, awareness tests | Control and activity |
Practical example: Cybersecurity incident at a critical supplier
An organisation relies on an external IT service provider for a business-critical application. The provider experiences a cyber incident that disrupts service availability and may affect the confidentiality or integrity of data.
How the GRC process can support the response
- Identify the dependency: Record the supplier, service, business owner and affected systems.
- Assess the risk: Evaluate the impact on availability, integrity and confidentiality, including potential business consequences.
- Activate response processes: Assign incident ownership, follow escalation procedures and coordinate with relevant internal and external stakeholders.
- Assess reporting obligations: Determine whether the incident meets the applicable significant-incident criteria and follow the required reporting process.
- Collect evidence: Link incident records, communications, supplier information, decisions and recovery test results.
- Track remediation: Assign corrective actions, owners and deadlines, and verify that agreed improvements are implemented.
A GRC platform can provide the traceability between the supplier risk, affected requirements, relevant controls, incident records and remediation activities.
A structured NIS 2 compliance workflow
Determine scope
Assess whether the organisation falls within the applicable NIS 2 and national requirements.
Identify gaps
Compare existing processes and controls with applicable obligations.
Assess risks
Evaluate threats, vulnerabilities, dependencies and potential business impact.
Implement controls
Define measures, responsibilities, implementation plans and review cycles.
Monitor and evidence
Maintain evidence, test effectiveness and monitor outstanding actions.
Review and improve
Report to management, address findings and improve the security programme.
NIS 2 in Germany: regulatory context
The German NIS 2 implementation is based primarily on the revised BSI Act (BSIG), introduced through the law published in the Federal Law Gazette as BGBl. 2025 I No. 301.
Key dates
- 17 October 2024: EU deadline for Member States to transpose NIS 2.
- 6 December 2025: German implementation entered into force.
- 6 March 2026: Three-month point following entry into force, relevant to the initial registration requirement for entities already in scope.
The Bundesamt für Sicherheit in der Informationstechnik (BSI) is the central German authority for the relevant NIS 2 responsibilities. In-scope organisations should check the current BSI guidance and applicable BSIG provisions for registration, reporting, supervision and evidence requirements.
Organisations operating in more than one EU Member State should also assess the relevant national implementation rules and jurisdictional requirements.
Frequently asked questions
Is NIS 2 relevant only for large companies?
No. Size is an important part of the general applicability assessment, but specific categories of organisations may be covered regardless of size. Sector, service, role and national rules must also be considered.
Does ISO 27001 certification mean that an organisation is NIS 2 compliant?
No. ISO/IEC 27001 can provide a strong management-system foundation, but certification does not automatically demonstrate compliance with every NIS 2 or national BSIG obligation. A requirement-by-requirement assessment is still necessary.
Does NIS 2 apply to suppliers?
Some suppliers may be directly in scope based on their own sector and circumstances. In addition, in-scope organisations must address relevant supply-chain security risks involving suppliers and service providers.
What is the relationship between NIS 2 and DORA?
DORA is a sector-specific EU regulation for financial entities. NIS 2 includes rules addressing the relationship with sector-specific Union legal acts. Organisations in the financial sector should assess the relevant legal provisions rather than assume that one framework simply replaces the other.
What evidence should an organisation maintain?
Relevant evidence may include risk assessments, policies, control records, supplier assessments, incident documentation, training records, test results, management approvals and remediation tracking. The evidence required depends on the applicable obligations and the organisation's circumstances.
Can GRC software guarantee NIS 2 compliance?
No software can guarantee legal compliance. A GRC platform can help structure requirements, risks, controls, responsibilities and evidence, but the organisation remains responsible for determining its obligations and implementing effective measures.
Bring your NIS 2 compliance activities together
Connect cybersecurity requirements, risks, controls, evidence and remediation in a structured GRC environment. Improve visibility and support consistent management oversight.
Contact usDisclaimer: This page provides general information about NIS 2 and its German implementation. It does not constitute legal advice or a determination that a particular organisation is in scope. Applicability, classification, reporting obligations and required measures must be assessed against the current applicable legislation and competent-authority guidance.