NIS-2: From the EU directive to the German BSI Act
NIS-2 is Directive (EU) 2022/2555 on measures for a high common level of cybersecurity across the Union. It replaces the first NIS Directive of 2016, significantly widens the circle of organisations in scope and harmonises obligations, reporting channels and sanctions across all member states. The directive entered into force on 16 January 2023 (Article 45). Member states had to transpose it into national law by 17 October 2024 (Article 41).
As a directive, NIS-2 has no direct effect on companies. What is binding in Germany is the implementation act: the NIS-2 Implementation and Cybersecurity Strengthening Act (NIS2UmsuCG), usually referred to as the NIS-2 Implementation Act. It was promulgated in the Federal Law Gazette on 5 December 2025 and entered into force on 6 December 2025. The core of this omnibus act is Article 1, a complete revision of the Act on the Federal Office for Information Security, the German BSI Act (BSIG). Wherever sections are cited on this page, they refer to the BSIG in its 2025 version.
Important in practice: the BSIG provides no transition period for the risk management and reporting obligations. They have applied since 6 December 2025. Only registration (Section 33) had its own three-month deadline, which expired on 6 March 2026. The German federal government expects around 29,500 entities to be in scope (estimate from the explanatory memorandum to the act; the BSI most recently cited about 29,000).
The competent authority is the BSI, the German Federal Office for Information Security. It acts as registration, reporting and supervisory authority at the same time (Section 59 BSIG). For incident reports and registrations, it operates the BSI portal jointly with the Federal Office of Civil Protection and Disaster Assistance (BBK).
NIS-2 scope: who falls under the BSIG
Whether your company is in scope is decided by Section 28 BSIG in two steps. First: Does the activity belong to an entity type listed in Annex 1 (sectors of high criticality) or Annex 2 (other critical sectors) of the BSIG? Second: Does the entity exceed the size thresholds? Both questions must be answered with yes, unless a special case applies.
Entity types and thresholds (Section 28 BSIG)
| Entity type | Sector | Size threshold | Legal basis |
|---|---|---|---|
| Essential entity (besonders wichtige Einrichtung) | Annex 1 | at least 250 employees or annual turnover above € 50 million and balance sheet total above € 43 million | Sec. 28 (1) no. 4 |
| Important entity (wichtige Einrichtung) | Annex 1 or 2 | at least 50 employees or annual turnover above € 10 million and balance sheet total above € 10 million | Sec. 28 (2) no. 3 |
| Essential (telecommunications) | Annex 1 | operators of public telecommunications networks or providers of publicly available telecommunications services with at least 50 employees or turnover and balance sheet total each above € 10 million | Sec. 28 (1) no. 3 |
| Important (telecommunications) | Annex 1 | the same providers below this threshold | Sec. 28 (2) no. 2 |
The calculation rules come from the EU SME Recommendation 2003/361/EC (Section 28 (4)). Note the or for the employee count: a machinery manufacturer with 60 employees and € 8 million turnover is an important entity because the employee threshold alone is sufficient. Partner and linked enterprises are not added if the entity is independent with regard to its IT systems, components and processes. Negligible ancillary activities are disregarded for the sector classification (Section 28 (3)).
Special cases regardless of size
- Operators of critical facilities (kritische Anlagen) are always essential entities (Section 28 (1) no. 1). Which facilities are critical is determined by the German KRITIS Umbrella Act and its statutory ordinance, essentially based on the degree of supply (previous benchmark: 500,000 persons supplied).
- Qualified trust service providers, TLD registries and DNS service providers are essential entities without any size threshold (Section 28 (1) no. 2).
- Non-qualified trust service providers are important entities without any size threshold (Section 28 (2) no. 1).
- Federal administration does not fall under Section 28 but under Section 29. State and municipal bodies are governed by the law of the respective federal state.
- Sectoral exemptions: For telecommunications providers, energy suppliers under Sections 5c to 5e of the German Energy Industry Act (EnWG) and financial entities under DORA, Sections 30 to 39 do not apply or apply only to a limited extent (Section 28 (5) and (6)); there, the German Telecommunications Act (TKG), the EnWG and DORA take over.
Our NIS-2 applicability check gives you an initial assessment in a few minutes. It reproduces the logic of Section 28 but does not replace legal advice in borderline cases such as group structures or mixed activities.
Sectors in Annex 1 (high criticality)
| Sector | Examples of entity types |
|---|---|
| Energy | Electricity suppliers, grid operators, generation facilities, storage, charging points, district heating, oil and gas infrastructure, hydrogen |
| Transport | Aviation, rail, shipping, road transport (traffic management, intelligent transport systems) |
| Banking and finance | Credit institutions, trading venues, central counterparties |
| Health | Healthcare providers, EU reference laboratories, pharmaceutical manufacturers, medicinal product research, manufacturers of critical medical devices |
| Water | Drinking water supply, waste water disposal |
| Digital infrastructure | Internet exchange points, DNS, TLD registries, cloud, data centres, CDN, trust services, public telecommunications networks and services |
| ICT service management (B2B) | Managed service providers, managed security service providers |
| Space | Operators of ground-based infrastructure for space-based services |
Sectors in Annex 2 (other critical sectors)
| Sector | Examples of entity types |
|---|---|
| Postal and courier services | Providers of postal services under the German Postal Act (PostG) |
| Waste management | Waste management companies under the German Circular Economy Act (KrWG), if this is their main economic activity |
| Chemicals | Manufacturers and importers of chemical substances and mixtures (REACH, NACE 20) |
| Food | Wholesale, industrial production and processing |
| Manufacturing | Medical devices and IVD, computer, electronic and optical products (NACE 26), electrical equipment (NACE 27), machinery (NACE 28), motor vehicles and parts (NACE 29), other transport equipment (NACE 30) |
| Digital providers | Online marketplaces, search engines, social networks |
| Research | Research organisations |
For our target group, Annex 2 is the decisive lever: machinery, automation, electronics and automotive suppliers fall in almost across the board via NACE divisions 26 to 30. Details on each sector are on the page NIS-2 sectors.
NIS-2 obligations under Sections 30, 31 and 35 BSIG
The central provision is Section 30 BSIG. Essential and important entities must take appropriate, proportionate and effective technical and organisational measures to prevent disruptions to the availability, integrity and confidentiality of their IT systems and to minimise the impact of security incidents. The measures must reflect the state of the art, take relevant standards into account and follow an all-hazards approach. That means: not only cyberattacks, but also power outages, flooding, operating errors and supplier failures belong in the risk analysis. Compliance must be documented (Section 30 (1) sentence 3).
Minimum catalogue under Section 30 (2) BSIG
- Policies on risk analysis and information security
- Incident handling (incident response)
- Business continuity: backup management, disaster recovery, crisis management
- Supply chain security including direct suppliers and service providers
- Security in the acquisition, development and maintenance of IT systems, including vulnerability management
- Procedures to assess the effectiveness of risk management measures
- Basic cyber hygiene and training
- Policies and procedures for cryptography and encryption
- Human resources security, access control and asset management
- Multi-factor or continuous authentication, secured voice, video and text communication, and secured emergency communication
The catalogue is deliberately technology-neutral. What counts as "proportionate" depends on risk exposure, size, implementation cost and potential damage (Section 30 (1) sentence 2). In practice, an information security management system based on ISO/IEC 27001 has proven itself as a framework; the BSI has published a one-pager "NIS-2 and ISO 27001" on this. In OT environments, the requirements of IEC 62443-2-1 and 62443-3-3 complement the catalogue because they make zones, conduits and security levels concrete for production networks.
For DNS, cloud, data centres, MSP/MSSP and digital providers, Implementing Regulation (EU) 2024/2690 takes precedence (Section 30 (3) and (4)). Industry associations may propose sector-specific security standards (B3S) (Section 30 (8)).
Section 31: operators of critical facilities
Operators of critical facilities carry additional burdens. For the systems relevant to the facility, measures may be required that go beyond the level of essential entities (Section 31 (1)). Above all, they must deploy attack detection systems that continuously and automatically record and evaluate operating parameters and detect threats (Section 31 (2)).
Section 35: duty to inform customers
In the event of a significant security incident, the BSI may order the entity to inform its customers without delay, including by publication on its own website (Section 35 (1)). Entities in the banking and finance, digital infrastructure, ICT service management and digital provider sectors must also inform their customers of possible countermeasures in the event of a significant cyber threat (Section 35 (2)).
Reporting obligations under Section 32 BSIG: the reporting cascade
A significant security incident (Section 2 no. 11 BSIG) exists if an incident has caused or is capable of causing severe operational disruption or financial loss, or if other persons may be affected by considerable material or non-material damage. If a critical service has failed or is impaired, the incident is always significant. For services covered by Implementing Regulation (EU) 2024/2690, the quantitative criteria of its Article 3 apply.
- Early warning within 24 hours of becoming aware (Section 32 (1) no. 1): indication of whether an unlawful or malicious background is suspected and whether cross-border impact is possible.
- Incident notification within 72 hours (Section 32 (1) no. 2): confirmation or update of the early warning, initial assessment of severity and impact, and indicators of compromise where available.
- Intermediate reports at the request of the BSI (Section 32 (1) no. 3).
- Final report no later than one month after the 72-hour notification (Section 32 (1) no. 4): detailed description, type of threat and root cause, remediation measures taken and ongoing, cross-border impact. If the incident is still ongoing, a progress report replaces the final report (Section 32 (2)).
The deadlines are maximum periods; the BSI expects "speed before completeness". The reporting channel is the BSI portal; entities not yet registered there use the online form of the reporting and information portal in the interim. Operators of critical facilities add details on the affected facility and critical service (Section 32 (3)). How to set up reporting processes so that the 24-hour deadline holds even on weekends is described on our page NIS-2 reporting obligations.
Registration under Sections 33 and 34 BSIG
Every essential and important entity must register with the BSI no later than three months after it first qualifies as such (Section 33 (1)). For entities that were already in scope on 6 December 2025, this deadline expired on 6 March 2026. The data to be submitted includes name and legal form, address and contact details including public IP address ranges, the relevant sector under Annex 1 or 2, the EU member states in which services are provided, and the competent supervisory authorities. Changes must be reported within two weeks (Section 33 (5)).
Deadline passed, grace period expired: register now. According to press reports, only around 11,500 entities were registered by the 6 March 2026 cut-off. The BSI then communicated a grace period until 31 July 2026; by then, around 19,000 registrations had been received (as of 26 October 2026, figures from the trade press, not from the act). Since then, the rule is: anyone in scope who is not registered commits an administrative offence under Section 65 (2) no. 6 BSIG with a fine of up to € 500,000. The BSI may also register the entity itself and request documents (Section 33 (3) and (4)). A late registration is still the better option compared to none.
Registration takes two steps: first, you apply for an ELSTER organisation certificate via the German "Mein Unternehmenskonto" business account, then you use it to register in the BSI portal. Operators of critical facilities register under Section 8 of the KRITIS Umbrella Act (Section 33 (2)).
Certain entity types with EU-wide jurisdiction under Section 60 (DNS services, TLD registries, cloud, data centres, CDN, MSP/MSSP, online marketplaces, search engines, social networks) are subject to the special registration under Section 34. It additionally covers the main establishment and other EU establishments; the BSI forwards the data to ENISA.
Management body (Section 38) and evidence (Section 39)
NIS-2 shifts responsibility upwards. Section 38 BSIG personally obliges the management body (Geschäftsleitung), i.e. managing directors, executive boards and comparable bodies (Section 2 no. 13), to:
- Approve and implement: The management body must implement the risk management measures under Section 30. It may delegate execution, but not responsibility.
- Monitor: It must continuously monitor implementation (Section 38 (1)). This requires a reporting system: key figures, audit results, incident statistics.
- Train: It must regularly attend training in order to be able to assess risks and risk management practices (Section 38 (3)). In April 2026, the BSI published key points for management training on this.
- Liability: If the management body culpably breaches its duties and the entity suffers damage, it is liable under the company law applicable to its legal form, i.e. via Section 43 of the German Limited Liability Companies Act (GmbHG) for a GmbH and Section 93 of the German Stock Corporation Act (AktG) for an AG (Section 38 (2)). This is internal liability towards the company, not external liability towards third parties.
Earlier drafts contained an explicit prohibition on waiving claims for damages against the management body. The promulgated version of Section 38 (2) instead refers to general company law. Have your D&O cover and rules of procedure reviewed in this light.
Evidence under Section 39 BSIG
There is no general audit or certification obligation for important and essential entities. They must document implementation and provide evidence at the request of the supervisory authority (Sections 61, 62). Operators of critical facilities, by contrast, must demonstrate compliance with Sections 30 and 31 through security audits, inspections or certifications: for the first time no later than three years after becoming an operator, and every three years thereafter (Section 39 (1)). Identified deficiencies must be reported; the BSI may require a remediation plan and proof of remediation.
Supervision and fines (Sections 61, 62, 65 BSIG)
The BSI supervises essential entities proactively: it may order audits and security scans, request documents, enter premises and issue binding instructions (Section 61). Important entities are subject to reactive supervision, which only becomes active when there are indications of violations (Section 62).
| Violation (selection) | Essential entity | Important entity | Provision |
|---|---|---|---|
| Risk management measures under Sec. 30 not implemented, implemented incompletely or late; reports under Sec. 32 omitted; customer information under Sec. 35 (2) omitted; certain orders disregarded | up to € 10 million; if total turnover exceeds € 500 million, up to 2 % of worldwide turnover | up to € 7 million; if total turnover exceeds € 500 million, up to 1.4 % | Sec. 65 (5) no. 1, (6) and (7) |
| Registration under Sec. 33 or Sec. 34 not made, incorrect or late | up to € 500,000 | up to € 500,000 | Sec. 65 (2) no. 6, (5) no. 5 |
| Evidence under Sec. 39 not provided or not provided on time (operators of critical facilities only) | up to € 1 million | not applicable | Sec. 65 (2) no. 10, (5) no. 4 |
| Reachability not ensured; information, access or submission refused | up to € 100,000 | up to € 100,000 | Sec. 65 (5) no. 6 |
| Violation of other enforceable orders (depending on type) | € 100,000 to € 2 million | € 100,000 to € 2 million | Sec. 65 (5) no. 3 to 6 |
Two points are frequently misrepresented. First: under the German act, the turnover-based cap (2 % or 1.4 %) applies only if worldwide group turnover exceeds € 500 million (Section 65 (6) to (8)); below that, the fixed amount applies. Second: if a GDPR fine has already been imposed for the same facts, the BSI may not impose an additional fine (Section 65 (11)). A classification of the amounts, worked examples and a fine calculator are available at NIS-2 fines.
How NIS-2 relates to DORA, the KRITIS Umbrella Act and the Cyber Resilience Act
NIS-2 does not stand alone. Three pieces of legislation overlap with the BSIG, and the delineation determines which obligations actually apply to you.
DORA (Regulation (EU) 2022/2554)
For financial entities such as banks, insurers, payment service providers and their ICT third-party service providers, DORA has been the more specific rule since 17 January 2025. Section 28 (6) BSIG exempts these companies from Sections 30 to 39. The supervisory authority is BaFin, not the BSI.
KRITIS Umbrella Act (KRITIS-Dachgesetz)
The German KRITIS Umbrella Act transposes the CER Directive (EU) 2022/2557 and governs the physical resilience of critical facilities: access protection, structural security, personnel, emergency preparedness. The BSIG governs IT security. Both acts share the definition of a critical facility (Section 2 no. 22 BSIG refers to Section 2 no. 3 of the KRITIS Umbrella Act) and the registration (Section 33 (2) BSIG). Until the KRITIS statutory ordinance with facility categories and thresholds enters into force, the transitional rules of Section 66 BSIG apply.
Cyber Resilience Act (Regulation (EU) 2024/2847)
The most important distinction for manufacturers: NIS-2 addresses organisations, the CRA addresses products. NIS-2 asks whether your company operates its own IT securely. The CRA asks whether the products with digital elements you place on the market are developed securely and maintained over the support period. A machinery manufacturer with 300 employees is subject to NIS-2 as an important entity under Annex 2 and, from 11 December 2027, must additionally ship its networked control systems in CRA-compliant form. Both frameworks require vulnerability management, but with a different object: here your own infrastructure, there the product at the customer's site. The side-by-side comparison of deadlines, obligations and sanctions is available at CRA vs. NIS-2.
Implementation roadmap and timeline
Since there is no transition period, sequence matters. From our NIS-2 projects, a four-step approach has proven itself that brings you to a defensible state within six to twelve months.
Check sector classification under Annex 1 and 2, calculate thresholds under Section 28, clarify the group structure, document the result. If in scope, register in the BSI portal immediately.
Assess the current state for each measure area of the minimum catalogue, define the scope including OT and service providers, prioritise gaps by risk and effort.
Work through the action plan: ISMS framework, MFA, backup and recovery, supplier requirements, vulnerability management. Rehearse the reporting process with 24-hour readiness.
Train the management body, set up reporting, measure effectiveness regularly, conduct internal audits, keep documentation ready for the supervisory authority.
Directive (EU) 2022/2555 enters into force 20 days after publication in the Official Journal (27 December 2022).
Deadline for member states under Article 41. Germany misses it; the Commission opens infringement proceedings.
Obligations under Sections 30, 32, 35 and 38 apply immediately, without a transition period.
End of the three-month period under Section 33 (1) for all entities already in scope on 6 December 2025.
Grace period for registration communicated by the BSI. Since then, fines under Section 65 (2) no. 6 may be imposed.
Next steps
Start with the applicability check to determine whether and as which entity type your company falls under the BSIG, and complete any missing registration immediately. A structured gap analysis against Section 30 is then worthwhile before you invest in individual tools. Blue Panther supports you from the scope analysis through action planning to a working reporting and emergency process, including OT under IEC 62443 if required. Find out more on the page NIS-2 consulting.

