German AI Regulation: Navigating BaFin, DORA, NIS2 and the KI-MIG
German firms deploying AI do not face one regulator or one rulebook. They face the EU AI ActVerordening (EU) 2024/1689De verordening van de EU over artificiële intelligentie. Zij deelt AI-systemen in naar risiconiveau — verboden, hoog risico, beperkt risico en minimaal risico — en verbindt verschillende verplichtingen aan de aanbieder die een systeem bouwt en aan de gebruiksverantwoordelijke die het gebruikt. Zij is op 1 augustus 2024 in werking getreden en geldt in fasen; de Digital Omnibus, verordening (EU) 2026/1744, in werking sinds 27 juli 2026, heeft de hoogrisicofasen verschoven zonder de sancties te wijzigen. Artikel 99 laat die staan op ten hoogste 35 miljoen euro of 7 % van de wereldwijde jaaromzet voor verboden praktijken, en ten hoogste 15 miljoen euro of 3 % voor de meeste andere inbreuken, waaronder de hoogrisico- en transparantieverplichtingen.Geldt voorAanbieders en gebruiksverantwoordelijken van AI-systemen die in de EU in de handel worden gebracht of worden gebruikt.Volgende datum2 december 2026 — Markering van door AI gegenereerde inhoud op grond van artikel 50, lid 2, voor systemen die op 2 augustus 2026 al in de handel warenLees de brontekst (opent in een nieuw tabblad)Algemene informatie over het genoemde instrument, geen juridisch advies. as implemented domestically through the KI-MIGKI-Marktüberwachungs- und Innovationsförderungsgesetz — de Duitse uitvoeringswet bij de EU AI ActDe Duitse wet die de EU AI Act in nationaal recht omzet, van kracht sinds 29 juli 2026. Zij wijst de Bundesnetzagentur aan als centrale markttoezichthouder voor AI buiten de gereguleerde sectoren, en richt daar een coördinatiecentrum, KoKIVO, op. BaFin behoudt het sectorspecifieke mandaat voor AI-systemen die in rechtstreeks verband met een gereguleerde financiële activiteit worden gebruikt; daarom vallen een bank en een woningbedrijf voor hetzelfde soort model onder verschillende toezichthouders.Geldt voorAanbieders en gebruiksverantwoordelijken van AI-systemen onder Duits toezicht. Welke autoriteit toezicht houdt, hangt af van de sector.Lees de brontekst (opent in een nieuw tabblad)Algemene informatie over het genoemde instrument, geen juridisch advies., BaFin’s long-standing supervisory expectations, DORADigital Operational Resilience Act — verordening (EU) 2022/2554De EU-verordening over digitale operationele weerbaarheid in de financiële sector. Zij bestrijkt ICT-risicobeheer, incidentclassificatie en -melding, weerbaarheidstesten en toezicht op externe ICT-dienstverleners — waarmee die dienstverleners binnen een toezichtsperimeter komen die eerder bij de financiële entiteit ophield. De leidraad van BaFin van 18 december 2025 richt zich tot entiteiten die onder de artikelen 5 tot en met 15 van DORA vallen en plaatst AI-systemen binnen dat bestaande ICT-kader in plaats van in een apart regime, waarbij het ICT-risico over de gehele AI-levenscyclus wordt onderzocht — dataverwerving, modelontwikkeling en -levering, doorlopend gebruik en buitengebruikstelling — met bijzondere aandacht voor ICT-risico bij derden.Geldt voorFinanciële entiteiten in de EU, en de ICT-dienstverleners die als kritiek voor hen zijn aangewezen.Lees de brontekst (opent in een nieuw tabblad)Algemene informatie over het genoemde instrument, geen juridisch advies. for operational resilience, and NIS2 as transposed into the BSIG for cybersecurity incidents. These regimes overlap in scope, differ in deadline, and — critically — differ in who you report to and how fast.
Published: March 2026 · updated August 2026 · Author: Dominic Fui Dodzi-Nusenu · Reading time: ~8 minutes
Disclosure: This article was drafted using generative AI assistance and subsequently edited, verified, and expanded by human legal and tech policy specialists. The organizational case study presented below is a composite hypothetical scenario designed to illustrate compliance risks.
In brief
Four regimes govern AI in German financial and critical-infrastructure firms. The KI-MIG implements the EU AI Act domestically and designates the Bundesnetzagentur as market surveillance authority. BaFin continues to supervise institutions through MaRisk and BAIT, which already require model governance and outsourcing controls that predate the AI Act. DORA governs ICT risk and third-party dependency for financial entities. NIS2, transposed through the BSIG, imposes a 24-hour early warning, a 72-hour incident notification and a one-month final report. The reporting clocks are the sharpest edge: they differ per regime, they start on awareness rather than on confirmation, and a single AI-related outage can trigger more than one at once. Build one control set and map it to all four rather than running four projects.
The four regimes, and what each one actually wants
| Regime | Scope | Core demand | Authority |
|---|---|---|---|
| KI-MIG / EU AI Act | Any AI system by use case | Risk classification, Annex IV documentation, oversight, monitoring | BNetzA as market surveillance |
| MaRisk / BAIT | Supervised institutions | Model governance, validation, outsourcing control, IT organisation | BaFin |
| DORA | Financial entities and their ICT providers | ICT risk management, third-party register, resilience testing | BaFin / ESAs |
| NIS2 / BSIGRichtlijn (EU) 2022/2555, in Duitsland omgezet door de NIS2-uitvoeringswet tot wijziging van het BSI-GesetzDe tweede richtlijn van de EU over netwerk- en informatiebeveiliging, en de Duitse wet die haar in nationaal recht omzet. Zij stelt maatregelen voor het beheer van cyberbeveiligingsrisico's vast, een gefaseerd tijdschema voor incidentmelding, en registratie bij het BSI. Op grond van § 38 Abs. 2 BSIG is de leiding van een onderneming persoonlijk aansprakelijk jegens de entiteit voor schending van die verplichtingen, en dat is wat haar onderscheidt van het eerdere Duitse IT-beveiligingsrecht.Geldt voor“Belangrijke” en “bijzonder belangrijke” entiteiten in 18 sectoren, ingedeeld naar personeelsomvang en omzet.Lees de brontekst (opent in een nieuw tabblad)Algemene informatie over het genoemde instrument, geen juridisch advies. | Essential and important entities | Cyber risk measures and staged incident reporting | BSI |
The useful observation is that these ask for the same underlying artefacts in different vocabularies. An inventory of AI systems, an owner per system, a documented risk assessment, evidence of monitoring, and an incident procedure will carry a very large share of all four. Firms that run four separate programmes produce four inconsistent answers about the same system, which is worse than one imperfect answer.
The KI-MIG: what German implementation adds
The AI Act is a regulation, so it applies directly — the KI-MIG does not restate it. What national implementation supplies is the machinery: which authority conducts market surveillance, how penalties are administered, and how the AI Act’s supervision meshes with existing sectoral supervisors. For financial institutions the practical consequence is that BaFin supervision does not displace AI Act market surveillance. You should expect to evidence the same model to two audiences with different questions.
Where the reporting clocks collide
This is the part that catches firms out, because the regimes measure time differently and the trigger is usually awareness, not confirmation.
| Trigger | Regime | Clock |
|---|---|---|
| Significant cyber incident | NIS2 / BSIG | 24h early warning → 72h notification → 1 month final report |
| Major ICT-related incident | DORA | Initial, intermediate and final reports on defined deadlines |
| Serious incident involving a high-risk AI system | EU AI Act Article 73 | Reporting to market surveillance, with a shortened window for widespread infringement or serious disruption |
A single event — say, a compromised model-serving endpoint producing discriminatory credit decisions — can plausibly trigger all three. If your incident runbook names only one regulator, it is not a runbook. The remedy is unglamorous: one incident register, one clock started on first awareness, and a mapping that fans out to each recipient.
Case scenario: a fintech that thought DORA covered it
A Frankfurt payments firm completed a substantial DORA programme in 2025 — ICT risk framework, third-party register, resilience testing. Asked in a 2026 procurement round for its EU AI Act position, it had none, and discovered three things: its fraud-scoring model was arguably Annex III, its DORA third-party register listed the model vendor as an ICT provider but recorded nothing about model behaviour, and its AI literacy obligation under Article 4 had been live for over a year with no training delivered.
Nothing in its DORA work was wasted — the third-party register was two-thirds of an AI vendor inventory. But DORA asks whether a supplier can keep running; the AI Act asks whether its output is lawful, documented and monitored. Different question, same supplier.
Practical sequencing for German firms
- Build one AI inventory and make it serve the AI Act classification, the DORA third-party register and BaFin outsourcing records simultaneously.
- Close the already-enforceable AI Act duties first — Article 5 prohibitions, Article 4 AI literacy, Article 50 transparency. These are live now, unlike the high-risk tier which moved to December 2027.
- Consolidate incident reporting into a single intake with a mapping to BSI, BaFin and market surveillance, and start the clock on awareness.
- Reuse MaRisk and BAIT model governance rather than rebuilding. Validation, approval and change control already exist in supervised institutions; the AI Act mostly asks for them to be evidenced differently.
- Assign one accountable owner across all four. Splitting AI Act ownership from ICT risk ownership is how the same system ends up described two ways.
Four regimes, one estate — can you evidence the same system to all of them?
Map your AI systems against the AI Act, DORA and NIS2 in one place.
Related reading
- EU AI Act for Financial Institutions: The 2027 Deadline
- EU AI Act Compliance Checklist for High-Risk AI Systems
- How German Banks Are Adopting AI: Market Landscape 2026
Frequently asked questions
Does the KI-MIG create obligations beyond the EU AI Act?
The AI Act applies directly as a regulation, so the KI-MIG’s role is largely institutional — designating market surveillance (the Bundesnetzagentur), administering penalties, and coordinating with sectoral supervisors. Your substantive duties come from the AI Act itself.
If BaFin already supervises our models, is the AI Act duplicated work?
There is real overlap in substance but not in evidence. MaRisk and BAIT model governance gives you validation, approval and change control; the AI Act asks for Annex IV documentation, classification reasoning, and post-market monitoring records. Treat the BaFin work as an input rather than a substitute.
Which incident clock starts first?
In practice the NIS2 24-hour early warning is the tightest, and it starts on becoming aware of a significant incident — not on completing triage. Firms should assume the shortest applicable clock and de-escalate later if a regime turns out not to apply.
Does DORA’s third-party register satisfy AI vendor documentation?
Partly. It identifies the supplier and the dependency, which is most of an AI vendor inventory. It does not record intended purpose, training data provenance, risk classification or monitoring, which the AI Act requires.
We are not a financial entity. Does any of this apply?
The AI Act does, because it regulates by use case rather than sector — employment screening and essential-services eligibility are Annex III wherever they occur. NIS2 may also apply if you are an essential or important entity. DORA and BaFin expectations will not.