Join our Newsletter — 33% off our NHI Course
Home› Guides› Germany NIS2 Implementation Guide: NIS2UmsuCG and the revised…
Guide Regulations & Frameworks

Germany NIS2 Implementation Guide: NIS2UmsuCG and the revised BSIG

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Germany implemented NIS2 late but in full, and since 6 December 2025 companies in the sectors listed in the BSIG annexes have had to register with the BSI, report incidents within 24 hours and prove that their management has been trained. The NIS-2 Implementation and Cybersecurity Strengthening Act (NIS2UmsuCG, BGBl. 2025 I Nr. 301) rewrote the BSI Act (BSIG) and replaced the old KRITIS-only model with two categories of regulated entity. The obligations sit in the BSIG itself, so the section numbers matter more than the Directive's article numbers when you deal with the BSI. This guide covers who is in scope under section 28, the section 30 measures, reporting under section 32, registration under section 33, manager duties under section 38, the extra duties for operators of critical installations and the section 65 fines. It is for CISOs, compliance leads and identity teams at German entities and at foreign groups with German subsidiaries, and builds on the NIS2 Directive Guide rather than repeating it.

Status checked 27 October 2026. The law was signed on 2 December 2025, published on 5 December 2025 and entered into force on 6 December 2025 without a general transition period. The statutory registration window under section 33 has passed, according to the BSI. The KRITIS umbrella law (KRITIS-Dachgesetz) is referenced in the BSIG for critical installations; check its current status separately. This page is not legal advice.

Key takeaways

  • Two categories, set by the BSIG: besonders wichtige Einrichtungen (essential) and wichtige Einrichtungen (important) under section 28, with thresholds of 250 staff or EUR 50 million turnover and EUR 43 million balance sheet, and 50 staff or more than EUR 10 million in both.
  • Registration is a hard duty: section 33 requires registration within three months of qualifying, through the joint BSI and BBK facility, using an ELSTER organisation certificate and the BSI portal.
  • Four reporting stages: an early report within 24 hours, a notification within 72 hours, interim reports on request and a final report within one month, to the joint reporting point (section 32).
  • Management carries personal duties: section 38 obliges the Geschäftsleitung to implement and oversee the measures, makes managers liable to the entity for culpable breaches and requires regular training.
  • Fines mirror the Directive: up to EUR 10 million or 2% of worldwide turnover for essential entities and EUR 7 million or 1.4% for important ones, with the turnover caps applying above EUR 500 million (section 65).

Scope: who and what is covered

Section 28 sorts entities that offer goods or services for payment in an Annex 1 or Annex 2 sector of the BSIG. The size test uses the EU SME Recommendation 2003/361/EC, but section 28(4) allows partner and linked enterprise data to be ignored where the entity is independent in its IT systems, components and processes, a German departure from the Directive that groups should document carefully.

CategoryWho (section 28)Size test
Besonders wichtige Einrichtung (essential)Operators of critical installations; qualified trust service providers; TLD registries; DNS service providers; public telecom providers and networks above the threshold; other Annex 1 entities above the large thresholdTelecom: at least 50 staff, or turnover and balance sheet both above EUR 10 million. Other Annex 1: at least 250 staff, or turnover above EUR 50 million and balance sheet above EUR 43 million
Wichtige Einrichtung (important)Non-qualified trust service providers; smaller telecom providers; other Annex 1 or Annex 2 entities above the medium thresholdAt least 50 staff, or turnover and balance sheet both above EUR 10 million
Excluded or reducedFederal administration (separate rules unless it operates a critical installation); some telecom and energy entities for overlapping duties; DORA financial entities for sections 30 to 32, 35, 36, 38 and 39; specified health telematics entitiesSection 28(1), (2), (5) to (8)
  • Negligible activities: section 28(3) lets business activities that are negligible compared with the entity's total activity be disregarded when assigning a sector. Record the reasoning if you rely on it.
  • Self-assessment: the BSI offers an online NIS-2 Betroffenheitsprüfung to help entities decide whether they are affected. It is guidance, not a legal determination.
  • Foreign groups: a German subsidiary is assessed on its own data unless it shares IT with the group; jurisdiction rules for cloud, data centre, MSP and similar digital providers follow the Directive's main establishment principle. See the NIS2 Directive Guide.

Key obligations

BSIG sectionObligationWhat it requires in practiceNIS2 article
30(1)Risk-management measures"Geeignete, verhältnismäßige und wirksame" technical and organisational measures, proportionate to exposure, size, cost and impact, and documented proof of compliance21(1)
30(2)Minimum measuresTen areas, from risk analysis to multi-factor authentication, following an all-hazards approach and the state of the art21(2)
30(3), (4)EU implementing actsImplementing Regulation (EU) 2024/2690 takes priority for DNS, cloud, data centre, MSP, MSSP, marketplace and similar providers21(5)
32Incident reportingFour-stage reports to the joint BSI and BBK reporting point; critical installations add the installation type and affected service23
33RegistrationRegister within three months; report changes within two weeks3(4), 27
35Informing customersDuties to inform recipients of services (check the section text for triggers)23(1), (2)
38Management dutiesImplement, oversee, liability to the entity, regular training20
39Proof for critical installationsAudits, inspections or certifications every three years, results to the BSIBeyond the Directive (continues former KRITIS duty)

The ten minimum measures in section 30(2)

  1. Risk analysis and IT security concepts.
  2. Incident handling.
  3. Business continuity, including backup management, disaster recovery and crisis management.
  4. Supply chain security, including relationships with direct suppliers and service providers.
  5. Security in acquisition, development and maintenance, including vulnerability handling and disclosure.
  6. Policies and procedures to assess the effectiveness of the measures.
  7. Basic cyber hygiene training and awareness.
  8. Cryptography and encryption policies.
  9. Personnel security, access control and management of ICT systems, products and processes.
  10. Multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communications where appropriate.

For mapping these to evidence, the BSI publishes material that links ISO/IEC 27001 and IT-Grundschutz to the NIS-2 duties. See the BSI IT-Grundschutz Guide.

Reporting under section 32

StageDeadlineContent
Frühe Erstmeldung (early report)Without undue delay, at the latest within 24 hours of becoming awareWhether unlawful or malicious acts are suspected; possible cross-border effects
Meldung (notification)Within 72 hoursConfirms or updates the early report; initial assessment of severity and impact; indicators of compromise where available
Zwischenmeldung (interim)On BSI requestRelevant status updates
Abschlussmeldung (final)No later than one month after the notificationDetailed description, threat type or root cause, remedial measures, cross-border effects
Fortschrittsmeldung (progress)Instead of the final report if the incident is ongoingStatus; final report follows when handling ends

The BSI sets the procedure and content after consulting industry and publishes it on its website; it forwards reports to the competent federal supervisors. A personal data breach still needs a separate GDPR Article 33 notification to the data protection authority.

Timeline and current status

DateEvent
17 October 2024NIS2 transposition deadline missed by Germany
7 May 2025European Commission reasoned opinion to Germany and 18 other Member States
13 November 2025Bundestag adopts the NIS2UmsuCG
2 December 2025Law signed (Ausfertigung)
5 December 2025Published as BGBl. 2025 I Nr. 301
6 December 2025Revised BSIG in force; duties apply without a general transition period
Within three months of qualifyingSection 33 registration deadline for each entity
BSI-set date, at least three years after qualifyingFirst section 39 proof for operators of critical installations; then every three years

Enforcement and penalties

The BSI supervises and can order measures, request records and, where an entity fails to register, register it itself (section 33(3)). Section 65 sets the fine ceilings.

Breach (section 65)Maximum fine
Section 30(1) measures missing, incorrect, incomplete or late, missing documentation; section 32 reports missing or late; some section 35 and 36 orders (essential entity)EUR 10 million, or up to 2% of worldwide group turnover where turnover exceeds EUR 500 million
Same breaches (important entity)EUR 7 million, or up to 1.4% of worldwide group turnover above EUR 500 million
Section 39 proof not provided or lateEUR 1 million
Section 33 registration details incomplete or lateEUR 500,000
Reachability failures under section 33(2), negligent breaches of some dutiesEUR 100,000
  • Turnover basis: the worldwide turnover of the undertaking in the business year before the decision, which may be estimated (section 65(8)).
  • No double fines with GDPR: conduct already fined under GDPR Article 58(2)(i) is not fined again under the BSIG (section 65(11)).
  • Personal liability: managers who breach section 38(1) are liable to the entity for culpably caused damage under the company law of its legal form (section 38(2)). For a GmbH or AG, that means the existing directors' liability rules apply to cyber failures. See the Board and Director Cyber Liability Guide.

What it means for AI agents and non-human identities

Section 30(2) numbers 9 and 10 are the identity measures, and for digital providers the Implementing Regulation's section 11 makes them specific. Machine identities are where German audits are most likely to find gaps.

  • Unique, owned identities: service accounts, API keys, workload identities and AI agent credentials need a named owner and a lifecycle, and unneeded ones must be deactivated. See the Service Account Security Guide.
  • Privileged automation: agents and scripts with administrative rights fall under the same expectation as human administrators: separate privileged credentials, restricted scope and periodic review. See the Privileged Access Management Guide.
  • Supply chain: number 4 covers direct suppliers and service providers, which includes SaaS platforms, MSPs and AI providers that hold tokens into your environment.
  • Reporting triggers: a stolen machine credential used for unauthorised access can be a significant incident; your 24-hour clock starts on awareness, so secret leak alerts need an owner who can decide quickly. See the Secrets Management Guide.

Compliance steps

  1. Confirm scope per legal entity: run the section 28 test, document the size data, the Annex sector and any reliance on section 28(3) or (4). Use the BSI Betroffenheitsprüfung as a cross-check.
  2. Register now if you have not: obtain an ELSTER organisation certificate through Mein Unternehmenskonto (MUK), then register in the BSI portal with the section 33 details: name, legal form, register number, contacts including public IP ranges, sector, Member States and supervisors.
  3. Set up reporting: name who decides significance, who files the 24-hour report and how to reach the joint reporting point out of hours. Time it in a tabletop.
  4. Train and minute the Geschäftsleitung: deliver regular training tied to your services, minute approval of the section 30 measures and record oversight. The BSI has published management training material.
  5. Close the measures gap: score yourself against the ten measures, using ISO/IEC 27001 or IT-Grundschutz as the evidence frame, and keep a dated gap register as the section 30(1) documentation.
  6. Prioritise identity controls: MFA for remote and administrative access, an owner for every non-human identity, and supplier access limited in scope and time. Roll out MFA in report-only mode, then pilot groups, then enforcement, with a break-glass account and a documented rollback.
  7. Critical installations: plan the section 39 audit cycle with a qualified auditor and keep attack detection evidence ready.
  8. Keep records current: report registration changes within two weeks and review the scope test yearly.

Decision guidance

  • Essential or important: duties under sections 30, 32 and 38 are the same; essential entities face more proactive supervision and the higher fine tier.
  • Group IT shared or separate: if the German entity uses group IT, linked enterprise data counts and the group will usually be in scope; if it is IT-independent, document that independence.
  • Former KRITIS operators: keep your existing audit cycle; section 39(3) sets transitional timing from your last proof under the old section 8a(3).
  • Financial entities: DORA replaces sections 30 to 32 and 38 for in-scope financial entities, so do not build a parallel BSIG programme. See the DORA Guide.

Measuring progress

  • Registration accuracy: days since the last check of BSI portal details against reality (target under 90).
  • Reporting readiness: time from detection to significance decision in exercises, against 24 hours.
  • Training coverage: share of Geschäftsleitung members trained in the last 12 months.
  • MFA coverage: percentage of remote, administrative and cloud console access protected.
  • Owned non-human identities: share of service accounts and API keys with a named owner and rotation date.
  • Gap closure: open items in the section 30 gap register past their due date.

Framework mapping

BSIG dutyNIST CSF 2.0ISO/IEC 27001:2022
Section 30(2) no. 1 risk analysisID.RA-01, GV.RM-01Clause 6.1, 8.2
No. 4 supply chainGV.SC-01Annex A 5.19 to 5.22
No. 9 access control and assetsPR.AA-01, PR.AA-05, ID.AM-02Annex A 5.9, 5.15 to 5.18
No. 10 MFAPR.AA-01Annex A 8.5
Section 32 reportingRS.CO-02Annex A 5.24, 5.26
Section 38 management dutiesGV.RR-01, GV.OV-01Clause 5.1, 9.3

Common failure patterns

  • Waiting for the BSI to call: registration is the entity's duty, and the BSI can register non-registrants itself and fine incomplete details.
  • Group scope assumed away: a subsidiary under the threshold that shares group IT is assessed with linked enterprise data.
  • Management training as a one-off: section 38(3) says regularly; a single 2026 session will not stay sufficient.
  • Remote access without MFA: the most common entry point in serious incidents, as the Change Healthcare Breach 2024 showed.
  • Machine identities outside the access policy: shared service accounts and long-lived keys that no access review covers.

Practitioner checklist

  • Run and document the section 28 scope test for each German legal entity.
  • Confirm BSI portal registration and that details are current.
  • Name the significance decision owner and test the 24-hour, 72-hour and one-month reports.
  • Minute Geschäftsleitung approval of the section 30 measures and record training.
  • Keep a dated gap register against the ten section 30(2) measures.
  • Enforce MFA on remote and administrative access, with break-glass and rollback.
  • Give every service account, API key and AI agent credential an owner and rotation date.
  • Add security, reporting and audit clauses to critical supplier contracts.
  • Plan section 39 audits if you operate a critical installation.

Standards and references

Related NHI Mgmt Group resources: NIS2 Directive Guide · NIS2 Transposition Tracker · BSI IT-Grundschutz Guide · NIS2 Readiness Checklist. This guide summarises the German NIS2 implementation law and the revised BSIG and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.