ctipilot.ch

Germany KRITIS-DachG (CER Directive transposition) in force March 2026 — public administration first time in CI scope; registration deadline 17 July 2026

campaign · policy:germany-kritis-dachg-2026

Coverage timeline
1
first 2026-05-10 → last 2026-05-10
Briefs
1
1 distinct
Sources cited
24
19 hosts
Sections touched
1
weekly_policy
Co-occurring entities
2
see Related entities below

Story timeline

  1. 2026-05-10CTI Weekly Summary — 2026-W19 (May 04 – May 10, 2026)
    weekly_policyFirst coverage. W2 horizon research. CER Directive 2022/2557 transposition; Bundesrat approval 6 March 2026; cross-sectoral physical resilience covering energy, transport, healthcare, water, finance, municipal waste, public administration. 24-hour BSI/BBK incident reporting; risk assessments every 4 years; fines up to €1M for concealment.

Where this entity is cited

  • weekly_policy1

Source distribution

  • heise.de4 (17%)
  • kaspersky.com2 (8%)
  • therecord.media2 (8%)
  • luther-lawfirm.com1 (4%)
  • mofo.com1 (4%)
  • anwalt.de1 (4%)
  • bleepingcomputer.com1 (4%)
  • cert.europa.eu1 (4%)
  • other11 (46%)

Related entities

All cited sources (24)

Items in briefs about Germany KRITIS-DachG (CER Directive transposition) in force March 2026 — public administration first time in CI scope; registration deadline 17 July 2026 (2)

Germany KRITIS-DachG in force — public administration first time in critical-infrastructure scope; registration deadline 17 July 2026

From CTI Weekly Summary — 2026-W19 (May 04 – May 10, 2026) · published 2026-05-11 · view item permalink →

Germany's KRITIS-DachG (Act to Strengthen Physical Resilience of Critical Installations), implementing EU CER Directive 2022/2557, entered into force in late March 2026 following Bundesrat approval on 6 March 2026 (Luther Lawfirm, 2026-04-10 · Morrison Foerster European Digital Compliance, 2026-05-01). The Act establishes the first cross-sectoral physical and organisational resilience framework covering energy, transport, healthcare, water, finance, and — for the first time — municipal waste disposal and aspects of public administration. Registration deadline 17 July 2026 (or within three months of later qualification). Post-registration obligations cascade over nine–ten months: risk assessments every four years covering natural / technical / sabotage / cross-border scenarios, resilience plans, and 24-hour incident reporting to a joint BSI/BBK reporting point. Fines for non-compliance: up to €100,000 for registration/cooperation failures; up to €1,000,000 for concealing non-registration status; up to €200,000 for missing resilience evidence or plan. Key ambiguity: the BMI implementing ordinance defining which specific services and installations qualify as "critical" is not yet published, leaving scope uncertain for borderline operators. What defenders need to do differently: German public-sector and critical-sector organisations need to self-assess KRITIS-DachG applicability before 17 July; ISG-style 24-hour reporting obligation now applies to physical as well as cyber incidents; Swiss entities with German subsidiaries operating in scope sectors are directly affected. Cross-references NIS2 and BSI Act obligations — the three frameworks overlap operationally and require coordinated incident-response runbook design.

Qilin ransomware hits Die Linke (Germany): 1.5 TB claimed, DPA notified (~April 2026, first coverage)

From CTI Daily Brief — 2026-05-08 · published 2026-05-11 · view item permalink →

The German federal party Die Linke confirmed in April 2026 that the Qilin ransomware group (also known as Agenda, a Rust-based RaaS platform known for double extortion) encrypted and exfiltrated its systems, with the gang claiming 1.5 TB of internal data. The party's data protection officer notified the responsible Landesdatenschutzbehörde (state DPA). Die Linke issued a victim statement acknowledging operational disruption; no ransom figure has been publicly disclosed. Qilin has targeted political parties and civil-society organisations across Western Europe since 2023. This breach is approximately four weeks old but has not been previously covered in this brief series.