The EU’s Digital Operational Resilience Act (DORA), Regulation (EU) 2022/2554, entered into force in January 2025 and applies to a broad range of financial entities and their critical ICT third-party service providers. For compliance leaders, DORA’s relevance extends beyond IT risk management: AML transaction monitoring platforms, fraud detection systems, sanctions screening tools, and case management solutions are all ICT systems within scope.
For institutions operating AML and fraud detection platforms in the EU, integrating DORA compliance into financial crime technology governance requires immediate assessment of ICT classifications, contractual gaps, and resilience testing programmes.
DORA’s Core Requirements Relevant to Financial Crime Systems
DORA imposes requirements in five main areas. Each has direct implications for financial crime technology infrastructure:
ICT Risk Management
Identify and classify ICT assets, assess associated risks, and implement protection, detection, response, and recovery measures
Incident Classification & Reporting
Classify and notify major ICT-related incidents within defined regulatory timelines — including AML system outages
Resilience Testing
Basic testing for all in-scope entities; advanced Threat-Led Penetration Testing (TLPT) for significant institutions
ICT Third-Party Risk Management
Enhanced contractual requirements for Critical ICT Third-Party Providers — directly relevant to cloud-hosted AML and fraud platforms
Information Sharing
Participation in cyber threat intelligence sharing arrangements within the EU financial sector
Incident Reporting for Financial Crime System Outages
An outage of an AML transaction monitoring or sanctions screening platform could meet the threshold for a major incident classification if it affects a significant volume of transactions or creates a period of non-compliance. The DORA reporting timeline is strict:
Within 4 hours of classifying as major (no later than 24h of becoming aware)
Intermediate update to the competent authority within 72 hours
Full final report submitted within one month of the intermediate report
Financial crime system outages must be included in the incident classification framework — and notification procedures must be documented and tested before an incident occurs, not drafted in response to one.
ICT Third-Party Risk: What Contracts Must Include
DORA’s third-party risk requirements are particularly relevant for institutions using cloud-hosted or vendor-managed AML and fraud detection platforms. Contracts with Critical ICT Third-Party Providers must include specific provisions:
Information Security
Defined security standards, access controls, encryption requirements, and vulnerability management obligations for the vendor.
Data Access and Audit Rights
The institution’s right to audit the vendor’s systems and access data held on its behalf — on demand and with defined notice periods.
Service Continuity and Disaster Recovery
Defined recovery time objectives, business continuity plans, and geographic redundancy requirements to ensure AML system availability.
Exit Assistance and Data Portability
Clear obligations on the vendor to support migration to an alternative provider — including data export in usable formats within defined timelines.
Regulatory Access and Inspection Rights
Supervisory authorities’ right to access and inspect the vendor’s premises and systems where relevant to the institution’s regulated activities.
Incident Notification
Vendor obligations to notify the institution of ICT incidents within defined timeframes consistent with the institution’s own DORA reporting obligations.
Implications for Financial Crime Technology Procurement
DORA significantly raises the due diligence bar for procuring financial crime technology from third-party vendors. Procurement assessments must now evaluate:
| Assessment Area | Key Questions | Priority |
|---|---|---|
| Operational Resilience | Business continuity, disaster recovery, geographic redundancy | Critical |
| Security Certifications | ISO 27001, SOC 2, or equivalent — current and auditable | Critical |
| DORA Contractual Provisions | Ability to support all mandatory DORA contract requirements | Critical |
| CTPP Designation Status | Is the vendor designated or likely to be designated as a Critical Third-Party Provider? | Monitor |
| Testing Cooperation | Ability to support TLPT and vulnerability assessment programmes | Critical |
Institutions should revisit existing contracts with financial crime technology vendors to assess DORA compliance gaps and initiate renegotiation where necessary. DORA required existing contracts to be brought into compliance by the application date — a requirement that has driven significant contract review activity across the EU financial sector since 2024.
Frequently Asked Questions
Assessing your financial crime systems for DORA compliance?
Nexiant supports EU-regulated institutions in aligning their AML and fraud detection technology governance with DORA’s operational resilience requirements.
Get in touch with our teamThis article was accurate at the time of publication in May 2026 and is intended for general informational purposes only. It does not constitute legal or compliance advice. Organisations should seek qualified professional counsel in relation to their specific obligations under EU law.




