Simplify Data Logo
  • Services
      • App Development
      • Web Development
          • Wordpress Development
          • Wordpress Support
          • Accessibility
      • Software Development
      • IT Consulting SME
          • Legacy modernisation
      • Business Analytics
          • Power BI
          • Metabase
      • Artificial Intelligence
      • SEO & AI visibility
      • Maintenance & Support
  • Managed Services
      • Zero-Trust Networking VPN
      • Managed email & groupware
  • Products
      • QRFlow
      • WooCommerce Interface
      • Open Source Projects
  • About us
      • Career
  • Blog
  • Contact
Cybersecurity

NIS2: Catching up on registration and the 10 measures in Section 30 BSIG

Simplify Data Team
November 16, 2026
5 Min. Read
NIS2: Catching up on registration and the 10 measures in Section 30 BSIG
Simplify Data
Simplify Data GmbH
www.simplify-data.de
NIS2: Catching up on registration and the 10 measures in Section 30 BSIG

Simplify Data Team • November 16, 2026 • 5 min Lesezeit

The German NIS2 implementation act has been in force since 6 December 2025. Companies that were already affected on that date had to register with the BSI (Germany's Federal Office for Information Security) by March 2026, and many have missed that deadline. The second part is far more work: affected entities must implement and document the measures in Section 30 BSIG. This article shows how to catch up on registration and then walks through what each measure means in practice (as of November 2026).

Please note: this article is general information, not legal advice. Whether your company is affected should be checked against the BSIG and, where in doubt, with legal support. For an overview of who is affected, see our article "NIS2: Who is affected and which obligations apply".

Catching up on registration

Under Section 33 BSIG, affected entities must register with the BSI no later than three months after they first (or again) fall under the law. For companies already affected on 6 December 2025, that was March 2026. The BSI expects missed registrations to be completed without undue delay.

The route in two steps

  1. Create an account with Mein Unternehmenskonto (MUK) using an ELSTER organisation certificate.
  2. Register in the BSI portal: name, legal form, contact details, public IP ranges, sector and type of entity.

Changes must be reported without undue delay, at the latest within two weeks. The ELSTER certificate is usually the bottleneck because issuing it can take a few days. Apply for it first, and do not wait for the authority to ask.

The ten measures in Section 30 BSIG

Affected entities must take appropriate, proportionate and effective technical and organisational measures and document them. The yardstick is an all-hazards approach that takes the state of the art into account. The table translates the ten areas into everyday IT examples.

No. Area under Section 30(2) Typical technical implementation
1 Risk analysis and information security Asset list, risk register, annual review
2 Handling security incidents Alerting, escalation plan, logging
3 Business continuity and crisis management Backups, restore tests, emergency plan
4 Supply chain security Supplier list, contractual requirements
5 Security in acquisition, development, maintenance Patch management, vulnerability scans
6 Assessing effectiveness Audits, penetration tests, metrics
7 Cyber hygiene and training Awareness training, phishing exercises
8 Cryptography Encrypted drives, TLS, key management
9 Personnel, access control, assets Role concept, offboarding, device inventory
10 MFA and secured communication MFA, encrypted mail and video communication

Risk analysis and incident handling

Start with an inventory: which systems, data and services keep the business running? That becomes a risk register with owners. For incidents you do not need an 80-page policy but a procedure someone can follow at two in the morning: who gets called, what gets isolated, who decides on the report.

Backup, patching and cryptography

Backup does not mean a copy on the same disk. What is required is business continuity: the 3-2-1 rule, one copy outside the network, a tested restore and clear responsibility. Without a restore test, a backup is only an assumption. For patch management, a fixed rhythm with deadlines by severity is what counts. Cryptography covers disk encryption, current TLS versions and who manages keys and certificates.

Access, MFA and training

MFA can be rolled out quickly and stands out immediately in any review. For Microsoft 365, VPN, email and admin access there should be no exception without a documented reason. Add a role concept with least privilege and an offboarding process that disables accounts on the last working day. Training is short, role-based and documented with date and participants.

The reporting process in practice

For significant security incidents, Section 32 BSIG sets out a staged procedure.

Report Deadline
Early warning without undue delay, at the latest 24 hours after becoming aware
Report with initial assessment without undue delay, at the latest 72 hours after becoming aware
Final report at the latest one month after the report with initial assessment

You can only meet these deadlines if it is settled beforehand who decides, who reports, and which contacts, IP ranges and portal credentials are ready. Rehearse the process once a year with a tabletop exercise. Record during the incident when you learned of what, because the deadlines run from that moment.

Evidence and management

ISO 27001 or IT-Grundschutz make it easier to show compliance but, according to the BSI, do not replace checking against the Section 30 catalogue. Create a gap analysis: for each area the current state, the gap, the measure and a responsible person.

Management must approve the measures and oversee their implementation (Section 38 BSIG). This cannot simply be delegated to IT. Training for management is also provided for. Plan regular reporting, for example one page per quarter on open measures and incidents.

Checklist

  1. Document whether you are affected, even if the answer is "not affected".
  2. Create the MUK account and catch up on BSI registration.
  3. Compare the ten areas with your current state (gap analysis).
  4. Enable MFA for all privileged accounts and remote access.
  5. Schedule a backup including a restore test.
  6. Write down and rehearse the incident process with the 24/72-hour sequence.
  7. Review contracts with IT providers for supply chain requirements.
  8. Train management and set a reporting rhythm.

How Simplify Data can help

We implement the technical parts that are missing from almost every gap analysis: multi-factor authentication, zero-trust access, backup tests and documented operating processes. We do not replace the legal assessment of whether you are affected. Learn more about Managed Services, Zero Trust VPN and IT consulting. For a first conversation, use the contact page.

Sources

  • BSI: Questions and answers on NIS-2 (German)
  • BSI: NIS-2 obligations (German)
  • Federal Law Gazette: BGBl. 2025 I No. 301 (German)
  • BSIG Section 30: Risk management measures (German)
  • BSIG Section 32: Reporting obligations (German)
  • BSIG Section 33: Registration obligation (German)
  • BSIG Section 38: Duties of management (German)

This article is for general information only and is not legal advice; for your specific case, please consult a lawyer.

© 2026 Simplify Data GmbH www.simplify-data.de
Back to Blog

Table of Contents

  • 1.Catching up on registration
  • –The route in two steps
  • 2.The ten measures in Section 30 BSIG
  • –Risk analysis and incident handling
  • –Backup, patching and cryptography
  • –Access, MFA and training
  • 3.The reporting process in practice
  • 4.Evidence and management
  • 5.Checklist
  • 6.How Simplify Data can help
  • 7.Sources

Actions

Our services
  • App Development
  • Web Development
  • Software Development
  • IT Consulting SME
  • Business Analytics
  • Artificial Intelligence
  • SEO & AI visibility
  • Maintenance & Support
  • IT services Kiel & Hamburg
Service & Legal
  • Legal notice
  • Privacy policy
Contact
  • Simplify Data GmbH
  • Königsweg 48, 24114 Kiel
  • Phone: 0431 705 770 24
  • Email: info@simplify-data.de

Copyright © 2026 Simplify Data GmbH