The Digital Operational Resilience Act took effect January 17, 2025. For banks, investment firms, payment institutions and their critical ICT providers, DORA is a binding operational requirement with supervisory consequences. We have worked inside financial institutions for decades. We know what ICT risk documentation looks like under examination, and we know the difference between a register that satisfies a regulator and one that does not.
DORA covers five interconnected areas. A gap in any one of them is visible during supervisory examination. We work across all five, grounded in the Level 1 regulation and the Level 2 RTS and ITS that specify how compliance is demonstrated.
Governance structure, risk appetite, policies, controls and evidence that the framework operates. Not a document that describes the right process but a system of records showing it runs.
Classification criteria, escalation thresholds, the major incident reporting chain to competent authorities, and the internal records that support each notification.
Threat-led penetration testing for significant institutions, vulnerability assessments for others, and the methodology, results and remediation records regulators require.
Contractual requirements for ICT providers, the Register of Information in the format ESAs examine, concentration risk analysis and ongoing oversight procedures.
Participation in threat intelligence sharing, documentation of sharing agreements and their scope, and integration with the incident response function.
We map your current posture against the five pillars, the RTS on ICT risk management, and the ITS on the Register of Information. The output is a prioritized gap register with specific corrective actions and the evidence each closure requires, not a summary of things you already knew.
The Register of Information is the document supervisors examine most closely. We build or review it against the ESA templates: contractual arrangements, ICT service categories, substitutability assessments, concentration analysis and the supporting data quality controls.
We design the oversight program: due diligence criteria, contractual minimum requirements, ongoing monitoring procedures and escalation paths for critical or important ICT providers. The program is built to hold up when a supervisory authority asks how concentration risk is managed.
We build the classification framework using the RTS criteria, draft the reporting templates for major incident notifications, and document the internal escalation chain so the reporting obligation can be met within regulatory timeframes.
We define the testing scope against DORA's requirements, review existing test programs for coverage gaps, and produce the methodology and results documentation the regulation requires.
We conduct an independent internal audit of the DORA compliance program, evaluate evidence quality across all five pillars and produce findings with specific closure criteria. The audit is conducted by credentialed lead auditors, not junior consultants.
Our background is quantitative finance, data operations and risk management inside financial institutions. We understand ICT architecture as it actually exists in a bank, not as it appears in a consultant's slide deck.
We know what supervisory examination looks like from the inside. The Register of Information, incident logs, and third-party oversight records we produce are designed to withstand scrutiny, not pass a self-assessment checklist.
DORA sits at the intersection of ICT, operational risk and third-party governance. We work at the control level, tracing each requirement to a process, a record, and an owner, not at the summary level where most compliance work stops.
DORA applies directly to financial entities regulated under EU law: credit institutions, payment institutions, e-money institutions, investment firms, insurance and reinsurance undertakings, crypto-asset service providers and others. It also applies to critical ICT third-party providers designated by the ESAs.
If you are a US-headquartered financial institution with EU operations, an ICT provider whose financial-entity clients are subject to DORA, or a financial group determining which entities fall within scope, the first task is a clear applicability analysis. We start there.
Entity type, the regulation you are subject to, your current state against the five pillars, and any supervisory timeline or examination date that shapes the work. That is enough to give you a clear picture of what an engagement looks like.
Please do not send confidential source data, credentials or regulated personal information through this form.