BaFin is auditing, are you ready?

DORA Compliance for Financial Entities

From gap analysis to audit support.

  • 01Comprehensive DORA gap analysis across all 5 pillars with a prioritized action plan
  • 02ICT risk management and incident reporting in accordance with BaFin requirements and RTS/ITS Level 2 standards
  • 03Third-party information register and concentration risk analysis with maintenance and submission processes
  • 04Audit preparation for IDW EPS 528, §44 special audits, and internal review
  • 05TLPT support according to TIBER-EU for systemically important institutions
11+Years of experience
120+Employees
540+Projects
ISO 27001certified

DORA Compliance: The Grace Period Is Over, BaFin Is Auditing

The Digital Operational Resilience Act (Regulation (EU) 2022/2554) has been mandatory since 17 January 2025, and supervisors are serious. Since then, BaFin has registered over 600 serious ICT incidents, conducted initial §44 special audits with a DORA focus, and in Q3 2025 initiated the first DORA-related fine proceedings, due to inadequate ICT third-party risk documentation. In February 2026, BaFin held its own workshops on the submission of information registers. At the same time, a KPMG benchmark study shows: 44% of financial entities in the EU are not yet fully DORA-compliant.

DORA goes far beyond the existing requirements of BAIT, KAIT, VAIT, ZAIT, and MaRisk. The regulation is specified by 13 regulatory technical standards (RTS) and 2 implementing technical standards (ITS), the so-called Level 2 measures of the ESAs (EBA, ESMA, EIOPA). These RTS/ITS define in detail how the five DORA pillars are to be implemented operationally:

• ICT Risk Management (Art. 5–16): Comprehensive framework for the identification, assessment, and control of all ICT risks, including the new role of the ICT risk manager and specific requirements for protection, detection, and recovery measures. • Incident Management & Reporting (Art. 17–23): Obligation to classify, document, and report major ICT incidents to BaFin within defined deadlines (For major ICT-related incidents, Article 5 of Delegated Regulation (EU) 2025/301 requires an initial notification as early as possible, within four hours of classification as major and generally within 24 hours of awareness of the incident. If classification occurs after those 24 hours, the four-hour limit runs from classification. The intermediate report is due within 72 hours of the initial notification; an updated intermediate report follows without undue delay and at the latest when regular activities have been recovered. The final report is due within one month of the intermediate report or the latest updated intermediate report. Weekend and bank-holiday provisions must be checked against entity type and supervisory decisions.). • Digital Operational Resilience Testing (Art. 24–27): Regular testing of ICT systems, for systemically important institutions including Threat-Led Penetration Testing (TLPT) under the TIBER-EU framework, at least every 3 years. • Third-Party Risk Management (Art. 28–44): Complete information register of all ICT third-party service providers, assessment of concentration risks, and viable exit strategies. Determine the applicable submission deadline from the current request issued by the competent supervisor. • Information Sharing (Art. 45): Voluntary, but supervisory-recommended exchange of threat information between financial entities, BaFin has already published guidance on this.

With the Financial Market Digitalization Act (FinmadiG), the German legislator has extended the DORA scope at the national level and designated BaFin as the competent supervisory authority. FinmadiG also governs the administrative offense provisions: violations of DORA obligations can be sanctioned as administrative offenses with fines of up to EUR 5 million. For critical ICT third-party providers, DORA itself provides for periodic penalty payments of up to 1% of average daily worldwide turnover, on a daily basis until compliance is achieved.

The Institute of Public Auditors in Germany (IDW) is currently finalizing the audit standard EPS 528, which defines how statutory auditors must assess DORA compliance. For the 2025 audit year, leniency applies to deficiencies remediated by year-end, from 2026 onwards, this grace period no longer applies. Entities in scope include: credit institutions, insurance undertakings, reinsurers, investment firms, payment institutions, e-money institutions, crypto-asset service providers, central securities depositories, central counterparties, and their critical ICT third-party service providers.

New urgency since July 2026: in a letter dated 7 July 2026 (SSM-2026-0301), ECB Banking Supervision requires all significant institutions to assess the impact of AI-enabled cyber threats without delay and to submit a concrete action plan to their Joint Supervisory Team (JST) by 31 October 2026. AI models now discover vulnerabilities and generate working exploits at unprecedented speed, the ECB therefore expects accelerated vulnerability and patch management, AI-enabled detection and defence capabilities, and robust ICT third-party risk management. The action plan must build on the existing cyber-risk strategy; DORA explicitly remains the binding framework. In parallel, the ESRB warns of systemic cyber risks stemming from frontier AI models, and the ECB has announced a separate letter on post-quantum cryptography.

ADVISORIs DORA team knows both sides of the table: our consultants have personally accompanied BaFin audits, conducted §44 KWG special audits, and implemented DORA gap analyses at institutions of all sizes. As an ISO 27001-certified consulting firm with approximately 150 specialists, we advise banks, insurance companies, payment institutions, and their critical ICT service providers, organizations where regulatory failures are not minor infractions but existential threats. Our experience from VS-NfD environments and classified information mandates demonstrates: we are at home where requirements are at their highest. At the same time, we make this experience accessible to the upper mid-market, critical ICT service providers and financial entities with 500 to 5,000 employees that need DORA compliance at banking level but want to implement it pragmatically and resource-efficiently. Our consultants are supported by AI-assisted analytical tools, from automated document analysis of ICT third-party contracts to real-time compliance monitoring of open DORA measures. This shortens project timelines without compromising quality.

Our expert consultants provide comprehensive dora compliance services tailored to your organization's specific needs. We combine deep regulatory expertise with practical implementation experience to deliver measurable results.

6 service modules

Service scope

01

DORA Readiness Assessment

Where do you actually stand? Our readiness assessment systematically evaluates your current ICT governance against all DORA requirements and the 13 RTS/2 ITS of the ESAs, from ICT risk management and incident reporting to the third-party register. You receive a detailed gap report with a prioritized action plan, effort estimate, and timeline. Companies with an existing ISMS (e.g., ISO 27001) have, in our experience, already covered 40–60% of the requirements. Deliverables: gap report, maturity scoring per DORA pillar, management presentation, prioritized roadmap.

  • Review of all 5 DORA pillars and RTS/ITS against your existing structures
  • Gap report with risk assessment, prioritization, and effort estimate
  • Management-ready results presentation for the executive board and supervisory board
  • Benchmarking against KPMG industry maturity levels and current BaFin expectations
02

ICT Risk Management Framework

DORA Art. 5–16 requires a comprehensive ICT risk management framework, significantly beyond what BAIT and MaRisk previously demanded. The associated RTS specify requirements for risk taxonomy, protective measures, detection mechanisms, and recovery strategies. We design and implement this framework tailored to your organization, including the new role of the ICT risk manager. Deliverables: ICT risk framework, risk taxonomy, role model, process documentation.

  • Development of a DORA-compliant ICT risk taxonomy and assessment methodology
  • Definition and staffing of the ICT risk manager function pursuant to DORA Art. 6(4)
  • Integration into existing ISMS (ISO 27001), BCM, and operational risk management
  • Derivation of protection, detection, and recovery measures in accordance with RTS requirements
03

Incident Management & BaFin Reporting

Since January 2025, BaFin has registered over 600 serious ICT incidents, and explicitly checks whether documented incident response processes exist and are regularly exercised. For major ICT-related incidents, Article 5 of Delegated Regulation (EU) 2025/301 requires an initial notification as early as possible, within four hours of classification as major and generally within 24 hours of awareness of the incident. If classification occurs after those 24 hours, the four-hour limit runs from classification. The intermediate report is due within 72 hours of the initial notification; an updated intermediate report follows without undue delay and at the latest when regular activities have been recovered. The final report is due within one month of the intermediate report or the latest updated intermediate report. Weekend and bank-holiday provisions must be checked against entity type and supervisory decisions. We implement a complete incident management system including tabletop exercises. Deliverables: incident response playbook, reporting chain documentation, BaFin reporting templates, exercise program.

  • Classification scheme for ICT incidents pursuant to DORA Art. 17–23 and the associated RTS
  • Reporting chains with documented deadline triggers under Article 5 of Delegated Regulation (EU) 2025/301: classification and awareness of the incident, initial notification and latest intermediate report
  • BaFin MVP reporting integration and process automation
  • Incident response exercise program (tabletop exercises, simulations, lessons learned)
04

Third-Party Risk Management & Information Register

According to industry surveys, ICT third-party management is the greatest DORA challenge, 75% of critical outsourcing service providers originate from third countries. DORA requires a complete information register of all contractual arrangements with ICT third-party service providers. Determine the applicable submission deadline from the current request issued by the competent supervisor. In Q3 2025, the first fine was imposed for inadequate third-party documentation. Deliverables: BaFin-compliant information register, concentration risk report, exit strategies, monitoring process.

  • Build-out of the BaFin-compliant information register with maintenance and submission processes
  • Concentration risk analysis and substitutability assessment of critical providers
  • Exit strategies and contingency plans for critical ICT service providers
  • Ongoing monitoring and risk assessment of the third-party portfolio
05

TLPT & Resilience Testing

DORA Art. 24–27 requires regular testing of digital operational resilience, for systemically important institutions including Threat-Led Penetration Testing (TLPT) under the TIBER-EU framework, at least every 3 years. We plan and support your testing programs: from vulnerability assessments and scenario-based tests to full TLPT with qualified red team providers. Deliverables: test strategy, TLPT scope definition, provider selection, test support, measure tracking.

  • Test planning and strategy pursuant to DORA Art. 24–27 and the associated RTS
  • TLPT support according to the TIBER-EU/TIBER-DE framework
  • Coordination with qualified threat intelligence and red team providers
  • Derivation, prioritization, and tracking of measures from test results
06

DORA Audit Preparation & Audit Support

BaFin has announced DORA as an audit focus, and the IDW standard EPS 528 defines for the first time how statutory auditors must assess DORA compliance. In addition, §44 KWG special audits with a DORA focus are already underway. We prepare you specifically: documentation, evidence management, dry runs, and support during the audit. From 2026, the leniency for first-year deficiencies no longer applies. Deliverables: audit readiness report, documentation matrix, dry-run protocol, audit support.

  • Preparation for IDW EPS 528 audits and §44 KWG special audits
  • Documentation matrix: mapping of all DORA requirements to your evidence
  • Dry runs with realistic audit scenarios and interview preparation
  • Support during the audit as a technical sparring partner

5 phases

Our Methodology: 5 Phases to Sustainable DORA Compliance

We follow a structured yet pragmatic approach. No overengineering, no paper compliance, but resilience that works in day-to-day operations, withstands any BaFin audit, and meets the RTS/ITS requirements of the ESAs.

  1. Phase 1, Assessment

    2–4 weeks

    Systematic as-is analysis of your ICT governance against all DORA requirements and RTS/ITS. Benchmark against KPMG industry maturity levels, identification of regulatory gaps and quick wins.

    gap report, maturity scoring, prioritized roadmap.

  2. Phase 2, Design

    4–8 weeks

    Development of the required frameworks, processes, and role models. Establishment of the ICT risk manager function, definition of reporting chains according to DORA deadlines (with a documented trigger for each reporting stage), build-out of the information register.

    framework documentation, process map, role model.

  3. Phase 3, Implementation

    8–16 weeks

    Stepwise implementation with minimal impact on ongoing operations. Integration into existing ISMS, BCM, and outsourcing structures. Migration of existing BAIT/MaRisk evidence into the DORA framework.

    implemented processes, populated information register, training records.

  4. Phase 4, Operationalization

    ongoing

    Embedding into day-to-day operations with KPI tracking, automated monitoring, and regular resilience exercises. Because DORA is not a project, it is a permanent state.

    KPI dashboard, exercise protocols, quarterly reporting.

  5. Phase 5, Audit preparation

    4–6 weeks

    Targeted preparation for IDW EPS 528 audits, §44 special audits, and internal reviews. Documentation, evidence management, dry runs, and interview coaching.

    audit readiness report, documentation matrix, dry-run protocol.

Sarah Richter

Your contact

Sarah Richter

Head of Information Security, Cyber Security

10+ years of experience, CISA, CISM, Lead Auditor, DORA, NIS2, BCM, Cyber and Information Security

Why ADVISORI for DORA Compliance

  • 01ISO 27001-certified, our own information security meets the highest standards that we implement for our clients
  • 02Deep experience with BAIT, MaRisk, KAIT, VAIT, and ZAIT, DORA builds on these frameworks, and we know each of them from years of practice at banks and insurance companies
  • 03Dedicated DORA team with its own readiness check, two-day training program (dora.advisori.de), and experience from over 30 DORA projects
  • 04AI platform Synthara AI Studio for automated compliance documentation, information register maintenance, and continuous monitoring
  • 05Practical experience at banks, insurance companies, capital management companies, payment institutions, and investment firms of all sizes, from fintech to large bank
  • 06In-depth knowledge of RTS/ITS Level 2 standards and close exchange with auditors conducting reviews under IDW EPS 528 and §44 KWG

Expert Consultation Available

Contact our specialists today for a personalized assessment of your requirements.

9 QUESTIONS, BRIEFLY ANSWERED

Frequently asked questions about DORA Compliance

What does a typical DORA compliance advisory engagement cover?

A typical engagement starts with a gap analysis against the five DORA pillars, followed by prioritizing the largest gaps, usually in third-party management, and support implementing concrete measures such as contract renegotiation or building the information register. Scope varies significantly depending on the maturity of existing risk management.

How does DORA compliance advisory differ from pure audit preparation?

Audit preparation focuses on successfully passing a specific, usually upcoming review. Compliance advisory is broader, covering the full path from initial assessment to ongoing operational integration, regardless of whether a review is imminent. In practice the two overlap often, but pure audit prep shortly before a review rarely covers full, sustainable implementation.

How is advisory need assessed for a specific company?

The starting point is a quick status check: is a documented ICT risk management framework already in place, how many and how critical are the ICT third-party relationships, and have resilience tests already been conducted. These three factors largely determine whether targeted support or a comprehensive engagement makes more sense.

What internal groundwork makes a DORA compliance advisory engagement easier?

Helpful groundwork includes a pre-compiled overview of all ICT third-party contracts, even if not yet DORA-compliant, and a collection of existing IT security and risk management documentation. That significantly shortens the initial phase of the engagement, which otherwise consumes a large share of time on inventory-taking rather than actual gap closure.

How long does a typical DORA compliance advisory engagement take?

For companies with established foundations, such as an existing ISO 27001 ISMS, a few months to full gap closure is often realistic. Without prior groundwork or with complex group structures involving many third-party relationships, the timeline extends considerably, mainly due to contract renegotiations that are hard to accelerate through internal project management alone.

How do you recognize an experienced DORA advisor?

Relevant indicators are demonstrable experience with comparable financial entities, a concrete grasp of the five DORA pillars rather than generic cybersecurity advisory, and the ability to address both regulatory and technical questions. An advisor who treats DORA only as a subtopic of general IT security consulting often lacks the necessary depth on the supervisory details.

How much does DORA consulting cost?

The effort depends mainly on the maturity of the existing ICT risk management, the number of ICT third-party providers in the register of information and the number of companies in scope. An institution that has already implemented BAIT or VAIT properly starts with far fewer gaps. The effort can be quantified reliably after a gap analysis against the DORA requirements. The starting point is a no-obligation initial call of 30 minutes.

Does DORA also apply to smaller and mid-sized institutions?

Yes. DORA applies to the financial entities in scope regardless of their size, but it is applied in line with the principle of proportionality (Art. 4): the extent and depth of the measures follow size, risk profile and the nature, scale and complexity of the business. For certain small entities Art. 16 provides a simplified ICT risk management framework. For mid-sized banks, insurers and payment institutions this means the obligations apply in full, while the implementation may be tailored appropriately. This distinction is part of the gap analysis.

How do corporate groups and banking groups implement DORA?

In groups, a common ICT risk management framework with uniform policies, anchored in every supervised company, has proven itself. The register of information is kept at the level of the individual company and on a consolidated basis. Important: intra-group ICT providers also count as ICT third-party service providers and belong in the register with their contracts. Incident reporting, digital resilience testing and the responsibility of the management body must be demonstrably in place for each company, even when steering is central.