
Financial Sector & Regulatory Compliance
Cybersecurity for Financial Services
The financial sector operates under the most demanding cybersecurity regulatory framework in Europe. DORA and MaRisk set extensive obligations. We know the requirements.
Why the Financial Sector Is Particularly Challenging
Financial institutions are challenging clients for two reasons: they are, first, highly attractive attack targets — direct financial gain, highly sensitive customer data, systemic economic importance — and second, they operate under the most demanding regulatory cybersecurity framework. Those working in financial services have no choice between compliance and security: both are legally mandated.
The threat actor landscape is correspondingly professional. Organised cybercrime, state-sponsored actors, and insider threats are all disproportionately active in the financial sector. Business Email Compromise (BEC), SWIFT attacks, ransomware against administrative systems, and targeted espionage against trading infrastructure are not theoretical scenarios but documented attack patterns with real damage in the billions.
Add to this the complexity of modern financial architectures: legacy core banking systems, modern microservice architectures, external cloud services, and a dense network of ICT third-party providers — data centres, payment processors, data providers, analytics platforms. Each of these providers is a potential attack path. Third-party management is not coincidentally a central pillar of DORA.
DORA: What Financial Entities Must Do Now
DORA (Digital Operational Resilience Act, Regulation (EU) 2022/2554) has applied since 17 January 2025 to banks, insurers, investment firms, payment service providers and investment funds in the EU. The regulation covers five areas: ICT risk management, incident reporting, resilience testing, ICT third-party risk and information sharing.
Significant institutions must also undergo Threat-Led Penetration Testing (TLPT) under TIBER-EU at least every three years, based on concrete threat intelligence. Scope, requirements and implementation are covered in detail on our DORA site.
BaFin Requirements: BAIT and MaRisk
BAIT no longer applies to CRR credit institutions since 17 January 2025; the remaining institutions under Section 1a(2a) KWG apply it until it is fully repealed at the end of 31 December 2026. Which path from BAIT to DORA applies to your institution is shown in our chapter-by-chapter mapping (in German).
MaRisk (Minimum Requirements for Risk Management) addresses risk management comprehensively and contains specific IT requirements in sections AT 7.2 and BT 3. BaFin supervisory reviews explicitly address compliance with these provisions. Deficiencies in IT security organisation, testing practices, or third-party management result in findings and can trigger supervisory action.
We support financial institutions from the DORA gap analysis through reworking existing documentation to preparing for supervisory discussions and external audits. Our consultants bring practical experience from years of work as external information security officers and CISOs within the insurance sector.
Our Services
- DORA gap analysis, roadmap, and implementation support
- ICT risk management framework per DORA Art. 6
- TLPT preparation and coordination (TIBER-EU)
- ICT third-party register and contract review
- Transition from BAIT to DORA and BaFin preparation
- Incident management and reporting per DORA
Applicable Regulations
- DORA
- BAIT (until 31 Dec 2026)
- MaRisk
- PSD2 / PSD3
- ISO/IEC 27001
Industry-Specific Consulting
Talk to our experts about your specific requirements and regulatory obligations.
Request ConsultingKontakt aufnehmen
Ready to address your industry-specific security requirements?
Sprechen Sie mit uns über Ihre Sicherheitsanforderungen – konkret, ohne Verpflichtung und auf Augenhöhe.