Guide
NIS2 requirements: Ten areas and your next steps in Germany
Understand Germany's NIS2 requirements: ten areas under section 30 BSIG, registration, incident reporting and management responsibilities.

NIS2 requires affected organisations to manage their security risks and document their implementation. Registration, incident reporting and management responsibilities add further obligations. Completing a checklist alone does not achieve this.
This guide explains NIS2 requirements for organisations in Germany and the work behind the ten areas in section 30 BSIG. Legal position: 12 November 2026. Other member states have their own implementing laws and reporting channels.
Which NIS2 obligations apply to your organisation?
Start with a reasoned classification: which entity and services are you assessing? Which sector, size criteria, company relationships and special rules matter? The NIS2 applicability calculator provides initial orientation. Borderline cases need a professional assessment.
For essential and important entities, distinguish these responsibilities:
| Obligation | What you need to organise | Legal basis |
|---|---|---|
| Manage risks | Implement and document appropriate, proportionate and effective security measures | Section 30 BSIG |
| Report incidents | Assess significant security incidents and report them within the deadlines | Section 32 BSIG |
| Register the entity | Submit information through the designated channel and keep it current | Section 33 BSIG |
| Involve management | Implement and oversee measures, with regular management training | Section 38 BSIG |
Operators of critical installations and certain digital services have additional or more specific requirements. Section 31 concerns critical installations; section 30(3) addresses the precedence of relevant EU implementing requirements for certain digital services. Check your entity type alongside the general catalogue. The source is the current BSIG.
The ten NIS2 requirement areas under section 30 BSIG
Article 21 of the NIS2 Directive provides the European framework. For implementation in Germany, section 30 BSIG specifies risk management measures. They must address relevant hazards, consider the state of the art and fit the risk exposure. Organisation size and implementation costs are factors, not blanket exemptions.
The following examples support planning. They are not an exhaustive list of legally mandated documents or products.
1. Risk analysis and security policies
Which disruption would seriously affect your operations? Consider a customer portal outage, compromised administrator accounts or the loss of a production formula. Assess impact and likelihood using a consistent method. Decide which risks to reduce, avoid, transfer or accept with a recorded rationale.
Record owners, decisions and review dates. A risk register then supports decisions: management can see outstanding gaps and where resources are needed.
2. Handle security incidents
Define who receives reports, assesses incidents and coordinates the response. A playbook must remain accessible if your normal company network is unavailable. Practise the process, including deputies, authority access and approval of a notification.
Incident handling and statutory reporting are related but distinct. Not every IT ticket is reportable. Our NIS2 reporting guide explains the thresholds and the 24- and 72-hour stages.
3. Maintain and restore operations
A backup only helps if you can restore the required systems and data. Determine how long business processes can be unavailable, which dependencies matter and who authorises recovery.
Test recovery and fallback procedures under realistic conditions. Document results and gaps. A successful backup job is not evidence of a successful restoration.
4. Supply chain security
A cloud provider or IT service provider can disrupt your operations even when your own systems work. Assess direct suppliers and service providers according to their importance to your services, access rights and potential outage impact.
Review suitable evidence and agree security requirements, incident communication and change handling. A supplier certificate is one input, not a complete assessment. The NIS2 supply chain guide walks through this process.
5. Secure acquisition, development and maintenance
Establish security requirements before acquiring or developing a system. Define who assesses vulnerability reports, prioritises updates and tracks end of support. Include software developed internally and the components it uses.
Connect a finding to its affected system, operational importance and remediation decision. If an update is not yet possible, record an interim solution, an owner and a review date.
6. Assess whether measures work
A published policy does not prove compliance with it. Check, for example, whether former employees actually lose access or a recovery test meets the agreed recovery time.
Define how you assess important measures. Keep results, deviations and follow-up work together. This does not establish a general requirement for every organisation to undergo an external audit every two years; specific evidence and supervisory obligations need separate assessment.
7. Train staff and build awareness
Teach the rules people need in their work: reporting suspicious messages, handling data appropriately and recognising unusual access. Match content and delivery to their responsibilities.
Record who received which training and where understanding needs improvement. Include the separate management training obligation under section 38 BSIG.
8. Govern cryptography
Determine which information needs protection in storage and transit. Establish suitable cryptographic procedures and manage keys and certificates. Ownership and renewal matter alongside technical selection.
A blanket product or algorithm list does not replace this decision. Procedures must fit the protection needs, use case and state of the art.
9. Manage people, access and systems
Who can access what, and when is access removed? Organise joining, role changes and leaving so that permissions match actual responsibilities. Review powerful access rights particularly carefully.
A maintained asset inventory helps locate owners and affected systems. It need not contain every technical detail from day one; essential dependencies and outstanding work must be visible.
10. Secure authentication and communication
Address multi-factor or continuous authentication and secure voice, video and text communication. Secure emergency communication may also be needed.
Check the experience in practice: does the second factor work during recovery? Is there an accessible alternative if ordinary email fails? Merely enabling a feature does not answer these questions.
Do you need an ISMS or ISO 27001 certificate for NIS2?
An ISMS organises recurring work: assessing risks, implementing measures, checking results and responding to change. It provides a sound basis for NIS2 implementation. However, section 30 BSIG does not impose blanket ISO 27001 certification on all affected organisations.
If you already have an ISMS, compare its scope and evidence with your NIS2 obligations. Registration, notifications and management responsibilities still need to be addressed. Our NIS2 and ISO 27001 mapping helps with this comparison. Work from IT-Grundschutz or other management systems may also be useful; assess equivalence on its merits.
Kopexa helps you understand the next tasks and organise implementation alongside daily work. Even without an existing ISMS, you can start with templates and a guided approach. Partners and consultants can support setup and ongoing work. The NIS2 product page explains the platform and support available to help you get started.
Turn requirements into a work plan
- Review existing work: What is implemented, for which scope and with what current evidence?
- Describe gaps concretely: For example, “customer portal recovery not tested” instead of “business continuity missing”.
- Assign the work: Establish an owner, required support and a realistic deadline.
- Check the result: Close the task after verifying the agreed implementation.
- Keep it current: Plan for changes and recurring reviews.
Registration and reporting readiness run in parallel. A project plan does not extend a statutory deadline. The NIS2 roadmap and checklist supports sequencing; the registration guide explains the authority process.
Quick answers
Frequently Asked Questions
Still have a question? Find the answers here.
Which NIS2 requirements apply in Germany?
Affected entities must implement and document appropriate, proportionate and effective risk management measures. Further duties include registration, significant incident reporting and management responsibilities. Special rules depend on entity type.
Is ISO 27001 mandatory for NIS2?
Section 30 BSIG does not impose blanket ISO 27001 certification. An ISMS can organise recurring security work. Existing implementation must be checked against specific NIS2 obligations.
Can we start using Kopexa without an existing ISMS?
Yes. Templates and a guided approach help you get started. Reuse existing security work. Partners and consultants can provide support when needed. Reviewing and improving your security work remains an ongoing task after setup.
Can registration and security work be handled sequentially?
Work on registration, reporting readiness and necessary measures in parallel. An unfinished ISMS does not extend the registration deadline; registration does not replace security measures.