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 ActReglamento (UE) 2024/1689El reglamento de la UE sobre inteligencia artificial. Clasifica los sistemas de IA por niveles de riesgo —prohibido, alto riesgo, riesgo limitado y riesgo mínimo— y atribuye obligaciones distintas al proveedor que construye un sistema y al responsable del despliegue que lo utiliza. Entró en vigor el 1 de agosto de 2024 y se aplica por etapas; el Digital Omnibus, Reglamento (UE) 2026/1744, en vigor desde el 27 de julio de 2026, retrasó las etapas de alto riesgo sin modificar las sanciones. El artículo 99 las mantiene en hasta 35 millones de euros o el 7 % del volumen de negocios anual mundial para las prácticas prohibidas, y hasta 15 millones de euros o el 3 % para la mayoría de las demás infracciones, incluidas las obligaciones de alto riesgo y de transparencia.Se aplica aProveedores y responsables del despliegue de sistemas de IA introducidos en el mercado de la UE o utilizados en ella.Próxima fecha2 de diciembre de 2026 — Marcado de los contenidos generados por IA conforme al artículo 50, apartado 2, para los sistemas ya introducidos en el mercado el 2 de agosto de 2026Leer el texto original (se abre en una pestaña nueva)Información de carácter general sobre el instrumento citado, no asesoramiento jurídico. as implemented domestically through the KI-MIGKI-Marktüberwachungs- und Innovationsförderungsgesetz — la ley alemana de aplicación del EU AI ActLa ley alemana que traslada el EU AI Act al derecho nacional, en vigor desde el 29 de julio de 2026. Designa a la Bundesnetzagentur como autoridad central de vigilancia del mercado de la IA fuera de los sectores regulados, y crea allí un centro de coordinación, KoKIVO. La BaFin conserva el mandato sectorial para los sistemas de IA utilizados en conexión directa con una actividad financiera regulada, y por eso un banco y una empresa de vivienda responden ante supervisores distintos por el mismo tipo de modelo.Se aplica aProveedores y responsables del despliegue de sistemas de IA supervisados en Alemania. Qué autoridad supervisa depende del sector.Leer el texto original (se abre en una pestaña nueva)Información de carácter general sobre el instrumento citado, no asesoramiento jurídico., BaFin’s long-standing supervisory expectations, DORADigital Operational Resilience Act — Reglamento (UE) 2022/2554El reglamento de la UE sobre resiliencia operativa digital en el sector financiero. Abarca la gestión del riesgo TIC, la clasificación y notificación de incidentes, las pruebas de resiliencia y la supervisión de los proveedores TIC externos, incorporando a esos proveedores a un perímetro de supervisión que antes se detenía en la entidad financiera. La guía de la BaFin de 18 de diciembre de 2025 se dirige a las entidades sujetas a los artículos 5 a 15 de DORA y sitúa los sistemas de IA dentro de ese marco TIC existente en lugar de en un régimen aparte, examinando el riesgo TIC a lo largo de todo el ciclo de vida de la IA —adquisición de datos, desarrollo y suministro del modelo, operación continuada y retirada— con especial atención al riesgo TIC de terceros.Se aplica aLas entidades financieras de la UE y los proveedores de servicios TIC designados como críticos para ellas.Leer el texto original (se abre en una pestaña nueva)Información de carácter general sobre el instrumento citado, no asesoramiento jurídico. 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 / BSIGDirectiva (UE) 2022/2555, transpuesta en Alemania por la ley de aplicación de NIS 2 que modifica la BSI-GesetzLa segunda directiva de la UE sobre seguridad de las redes y de la información, y la ley alemana que la traslada al derecho nacional. Fija medidas de gestión de riesgos de ciberseguridad, un calendario escalonado de notificación de incidentes y el registro ante el BSI. Conforme al § 38 Abs. 2 BSIG, la dirección de una empresa responde personalmente frente a la entidad por el incumplimiento de esas obligaciones, y eso es lo que la distingue del anterior derecho alemán de seguridad informática.Se aplica aEntidades «importantes» y «especialmente importantes» de 18 sectores, dimensionadas por plantilla y volumen de negocios.Leer el texto original (se abre en una pestaña nueva)Información de carácter general sobre el instrumento citado, no asesoramiento jurídico. | 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.