Skip to main content

Guide

NIS2 fines: Penalties and management liability under Germany's BSIG

Understand German NIS2 fines: the EUR 10m and 7m limits, turnover thresholds, registration penalties, management liability and supervisory powers.

Julian Köhn
|Updated|Read time: 5 minutes

NIS2 breaches can attract substantial fines in Germany. However, the frequently cited EUR 10 million figure is neither an automatic penalty for every error nor the limit for every offence. The specific breach, entity category and, where relevant, worldwide company turnover determine the applicable framework.

This guide explains NIS2 fines under Germany's BSIG, management responsibility and the distinction between a fine and a supervisory order. Legal position: 12 November 2026.

What NIS2 fines does the law provide for?

The relevant provision is section 65 BSIG. These cases are particularly relevant in practice:

Breach or classificationStatutory fine framework
Certain breaches of risk management, documentation or incident reporting duties by essential entitiesUp to EUR 10 million
Corresponding breaches by important entitiesUp to EUR 7 million
Corresponding cases involving essential entities with total turnover exceeding EUR 500 millionUp to 2% of total turnover
Corresponding cases involving important entities with total turnover exceeding EUR 500 millionUp to 1.4% of total turnover
Missing, incorrect, incomplete or late registration informationUp to EUR 500,000

The first four rows concern the offences specified in section 65(5), first sentence, point 1, and subsections 6 and 7. These include missing or inadequate measures under section 30, inadequate documentation and reporting breaches under section 32. The registration case follows from section 65(2), point 6, and subsection 5, first sentence, point 5.

The law contains further offences with their own limits, including certain evidence and information obligations. This table is not a complete list of administrative offences under the BSIG. A maximum amount is also not a prediction of the actual fine in an individual case.

EUR 10 million or 2%: what does that mean?

The turnover rule increases the possible framework for large companies. Under section 65(6)–(8), the relevant figure is the worldwide turnover of the undertaking to which the entity belongs, in the financial year preceding the authority's decision. Do not assume that only a local company's or affected service's revenue counts.

Two calculations illustrate the boundary:

  • Important entity, EUR 50 million total turnover: 1.4% would be EUR 700,000. This does not establish a general EUR 700,000 ceiling. The specified serious breaches fall within the framework of up to EUR 7 million.
  • Essential entity, EUR 1 billion total turnover: 2% equals EUR 20 million. In the relevant cases, the turnover-based framework can therefore exceed EUR 10 million.

These examples only calculate statutory limits. They do not describe imposed fines or expected penalties.

Which omissions can lead to proceedings?

A cyberattack alone does not prove a legal breach. Conversely, a failure can matter even before damage occurs. Section 65 explicitly covers inadequate implementation and documentation of risk management measures.

SituationWhat you need to establish and document
Registration was missedWhen did the duty arise, what information is missing and how will registration be completed?
A material security gap remains unresolvedWhat assessment, decision and effective interim measure exist?
A significant incident is reported lateWhen did it become known, who was responsible and what was submitted when?
Measures are marked complete but evidence is missingWhat was actually implemented and how was effectiveness assessed?

Late registration or documentation written afterwards does not automatically undo a previous omission. It remains necessary to fulfil the duty and prevent further errors. The registration guide and NIS2 requirements overview support this work.

Can management be personally liable?

Section 38 BSIG requires management bodies of essential and important entities to implement risk management measures and oversee their implementation. Regular training is also required to assess risks and their impacts.

If management breaches these duties, liability for culpably caused damage to the entity follows the applicable company law. Where that law contains no liability rule, section 38(2) provides a separate rule. This is not the same as automatically imposing an organisation's fine on its managing director personally.

Operational tasks can be handled internally or externally. Management responsibility does not disappear. Accountable oversight may require:

  • visibility of material risks and outstanding decisions;
  • a reasoned resource and priority plan;
  • reports on implementation, reviews and significant deviations;
  • recorded decisions and training evidence.

NIS2 management training supports understanding. A training certificate does not replace actual oversight within the organisation.

What can supervisors do besides impose fines?

Sections 61 and 62 BSIG govern supervision and enforcement. Subject to their conditions, these include inspections, evidence requirements and remediation orders. For important entities, a review under section 62 requires facts indicating that the specified duties are not being implemented correctly.

For essential entities, section 61(9) also provides, as a last resort, for temporary suspension of sector-specific authorisations or temporary prohibition of activities by unreliable management. The legal conditions must be met, including failure to comply with orders despite a deadline. This is not a blanket “licence withdrawal for any NIS2 breach”.

A supervisory order requires action. A fine sanctions a breach. Organisations therefore need both an operational response to an order and a legal assessment.

Can NIS2 and GDPR fines be combined?

An incident can affect both information security and personal data. Reporting duties and responsible authorities must then be assessed separately. Fines cannot simply be added together: section 65(11) BSIG excludes an additional BSIG fine for a breach arising from the same conduct for which the competent data protection authority has already imposed a GDPR fine.

This does not generally exclude every parallel proceeding or separate breach. The specific conduct and offence matter.

Reduce avoidable omissions

Start with applicability and the duties that actually apply. Organise registration and reporting capability alongside security work. Assess gaps, appoint owners and check results. Decisions on remaining risks should show who decided what and on which basis.

Kopexa helps track outstanding tasks, related risks and evidence, making missing work and unresolved decisions visible. This is not a guarantee against fines. The NIS2 roadmap provides a practical start; the Kopexa NIS2 solution describes the platform and support.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

How high are NIS2 fines?

For certain breaches, limits reach EUR 10 million for essential entities and EUR 7 million for important entities. Above EUR 500 million total turnover, section 65 BSIG provides for up to 2% or 1.4% respectively in those cases. Other offences have separate limits.

Are executives personally liable for NIS2 breaches?

Section 38 BSIG governs management duties and liability for culpably caused damage to the entity under applicable company law or a statutory fallback. An organisation’s fine does not automatically become a personal fine.

What fine applies for missing BSI registration?

Missing, incorrect, incomplete or late registration information can attract up to EUR 500,000 under section 65(2), point 6, and subsection 5, first sentence, point 5 BSIG. This is a maximum, not an automatic penalty.

What penalties apply for late incident reporting?

Breaches of section 32 BSIG are among the cases subject to the high entity-based or turnover-based limits in section 65. The actual assessment depends on the offence and individual circumstances.

Can NIS2 and GDPR fines be added together?

Not as a blanket rule. Section 65(11) BSIG excludes a further BSIG fine based on the same conduct already sanctioned by a GDPR fine. Separate breaches and reporting duties require separate assessment.

Can BSI prohibit business operations?

Section 61(9) BSIG provides, under restrictive conditions and as a last resort, for temporary measures by the competent supervisory authority affecting authorisations or unreliable management. An arbitrary NIS2 breach does not automatically lead to a business prohibition.

Does D&O insurance cover NIS2 breaches?

The insurance label alone does not answer this. Review the actual policy, exclusions and type of claim with the responsible insurance and legal specialists. This guide cannot establish coverage.

Is there a general grace period?

An internal project plan does not create a grace period. Check the duty, its statutory deadline and relevant special or transitional rules. The three-month registration period is not a general implementation deadline for all security measures.