Back to the journal
IT-Sicherheit November 2026

NIS-2 Is Now Law in Germany: Registration Is Only the Beginning

Germany's NIS2UmsuCG has been in force since 6 December 2025. Around 29,500 entities now fall under BSI supervision. Registration by 6 March 2026 is a formality; the real work starts afterwards.

When did NIS-2 take effect in Germany, and what does the NIS2UmsuCG regulate?

Germany's NIS-2 Implementation and Cybersecurity Strengthening Act, known as NIS2UmsuCG, entered into force on 6 December 2025 and transposes the EU's NIS-2 Directive into German law. There is no transition period. If you are in scope, the obligations apply now.

The core of the law is a substantial amendment to the BSI Act. The BSI, Germany's Federal Office for Information Security, becomes the supervisory authority for a much larger group of entities. New obligations include registration, reporting of significant security incidents, technical and organisational risk management measures, supply chain security, and explicit responsibility for management bodies.

For context: NIS-2 is not a recommendation or a framework from which you pick individual building blocks. It is a law with supervision, evidence requirements and sanctions. If you have worked voluntarily according to ISO 27001, you bring a solid foundation; the obligations themselves do not fulfil themselves.

How many companies are affected, and how has the scope changed?

The regulated group grows from roughly 4,500 organisations previously covered by the BSI Act, mostly operators of critical infrastructure, to around 29,500 entities. Other estimates cite about 30,000 companies and institutions across 18 sectors. The order of magnitude matters more than the exact number.

Two criteria determine whether you are in scope: size and sector. Thresholds are 50 employees or EUR 10 million in annual revenue. Sectors include energy, transport, health, digital infrastructure, wastewater, food, and parts of manufacturing. Medium and large companies in waste management or food production are also covered.

The BSI structures implementation in phases, from analysis and fundamental clarification through organisation and responsibility to risk assessment, resources, core measures and consolidation. This structure is helpful because it shows that registration is only one step in a longer chain.

Our position: the jump from 4,500 to around 29,500 entities changes supervisory practice. Many organisations will meet a regulator that wants to see evidence for the first time. If you have worked without a regulatory counterpart so far, you underestimate the cultural shift.

What obligations follow from the amended BSI Act?

The obligations fall into five blocks that interact and cannot be fulfilled in isolation.

  • Registration with the BSI: Entities in scope must register. The deadline is 6 March 2026.
  • Risk management: Risk analysis, information security policy, incident response, business continuity management, supply chain security, and procurement and development processes must be implemented and documented.
  • Reporting: Significant security incidents must be reported, with staged deadlines.
  • Supply chain security: The security of service providers and products in the supply chain becomes your own concern.
  • Management responsibility: The leadership level is responsible for risk management and must approve and monitor corresponding measures.

The seven obligation areas addressed by the law include risk analysis and information security policy, incident response, business continuity management, supply chain security, and procurement and development processes. In practice, this means an emergency plan in a drawer is not enough. Processes must be exercised, evidence must be findable, and responsibilities must be clear.

One point that is often underestimated: these obligations are not newly invented; they reflect recognised practice. If you take them seriously, you gain not only compliance but a resilient foundation for operations. If you treat them as a paper exercise, you will see the gap at the latest during the first audit or the first incident.

Which deadlines apply for registration and reporting?

The BSI registration deadline is 6 March 2026. For reporting significant security incidents, three staged deadlines apply: an initial notification within 24 hours, updated information within 72 hours, and a final report after one month.

These deadlines are not a formality. If you notice an incident only days later, you cannot meet the 24 hours. If you have no prepared processes, you will improvise during the crisis, and improvisation is the most expensive path.

Incident response thus becomes an organisational question, not a tooling question. A ticketing system and a forensics provider are useful, but they do not replace defined decision paths, named contacts and practised communication. If you first have to clarify who files the report during an emergency, you have already lost time.

Our position: the reporting obligations are the hardest part of the law because they cannot be delegated. They hit the organisation at a moment when it is already under stress.

Why does the threat landscape leave no room for complacency?

The situation is tense, and the numbers support this assessment. In 2026, the BSI registered more than 144,000 cybersecurity incidents, an increase of 38 percent over the previous year. This order of magnitude shows that exposure is a question of when, not if.

Concrete warnings underline this. In November 2026, the BSI warned about vulnerabilities in Danfoss AK-SM 800A controllers used in industrial refrigeration systems. Security researchers found six vulnerabilities in version 5.3.2 that could enable full takeover, persistent access and permanent failure. The recommendation: do not connect affected devices to the internet, and use at least a VPN for remote maintenance.

In August and September 2026, an attack on Berlin's state network became known, in which sensitive data leaked. Affected were the Senate Department for Urban Development, Building and Housing and the Senate Department for Mobility, Transport, Environment and Climate Protection, which were isolated from the state network. The BSI expressed alarm about risks to affected individuals from the leak of partly personal and sensitive data.

These examples show a pattern: attacks hit systems long considered unspectacular, and they hit data whose protection should be a given. If you treat NIS-2 as an annoying duty, you misread the occasion.

What should you build after registration?

After registration, the real work begins. Four building blocks are central in our view, and they build on each other.

  1. Sharpen the risk picture: Identify which systems and data are critical for delivering your services, and assess risks by likelihood and impact. Without this picture, all further measures remain arbitrary.
  2. Define and exercise processes: Define who detects an incident, who assesses it, who reports it and who communicates. Exercise these processes before you need them. A process that exists only on paper is not a process in an emergency.
  3. Build evidence: Document measures so that they are findable and understandable during an audit. Evidence is created in operations, not shortly before an audit.
  4. Include the supply chain: Clarify which service providers and products are relevant to your security, and make security requirements part of contracts and procurement.

Add the leadership level. Management responsibility is not a decorative sentence in the law. It means decisions on resources, priorities and risk acceptance must be made where the responsibility lies. Delegating information security solely to the IT department does not meet this responsibility.

The BSI describes implementation as a phase model, from analysis through organisation and responsibility to risk assessment, resources, core measures and consolidation. This model is a useful compass because it structures the path without shortening it.

Our position: if you treat registration as the goal, you have not read the law. Registration is a formality; the obligations behind it are the real work. Mountain Road supports organisations on this path, and we consider the sequence decisive: first the risk picture, then the processes, then the evidence.

What does this mean in practice?

NIS-2 has arrived in Germany, and it comes without a grace period. Registration by 6 March 2026 is the most visible step, but it is the beginning of a chain. If you start now, you have time to exercise processes, build evidence and involve leadership. If you wait, you will not be able to meet the deadlines in an emergency.

The good news: the obligations reflect recognised practice, and they can be implemented step by step. The bad news: they cannot be simulated. An exercised process, a clear risk picture and an involved management are the three factors that make the difference in an emergency.

Frequently asked questions

When did NIS-2 take effect in Germany?

The NIS2UmsuCG entered into force on 6 December 2025 and transposes the EU's NIS-2 Directive into German law. There is no transition period.

How many companies are affected by NIS-2?

The regulated group grows from roughly 4,500 to around 29,500 entities across 18 sectors. Other estimates cite about 30,000 companies.

Which deadlines apply for registration and reporting?

BSI registration is due by 6 March 2026. Significant security incidents must be reported within 24 hours, updated information within 72 hours, and a final report after one month.

What should companies build after registration?

A robust risk picture, exercised incident response processes, findable evidence and an included supply chain. Management bears responsibility for risk management.