Regulation (EU) 2022/2554 on digital operational resilience for the financial sector

What the authority record establishes

DORA establishes a harmonized framework for ICT risk management, incident reporting, resilience testing, third-party risk, and oversight across in-scope financial entities including insurance.

Binding within scope

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

Core and claims operating models must treat resilience, incidents, testing, outsourced ICT, contracts, concentration, recovery, and evidence as operating requirements rather than infrastructure footnotes.

Affected operating stages

• ICT Governance
• Incident Management
• Testing
• Third-Party Risk
• Contracting
• Oversight
• Recovery

Capabilities to examine

Policy Administration And Policy Lifecycle Control

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for policy administration and policy lifecycle control.

Premium Billing Invoicing And Receivables

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for premium billing invoicing and receivables.

Payments Disbursements And Reconciliation

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for payments disbursements and reconciliation.

Claim Case Task And Authority Workflow

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for claim case task and authority workflow.

Insurance Data Model Quality And Governance

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for insurance data model quality and governance.

API Event And Ecosystem Integration

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for API event and ecosystem integration.

Identity Security Privacy And Operational Controls

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for identity security privacy and operational controls.

Audit Trail Reason Code And Decision Reconstruction

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for audit trail reason code and decision reconstruction.

Affected buyer audiences

• EU insurers
• technology
• risk
• outsourcing
• legal
• operations

Implementation questions

• Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
• What is binding, what is guidance, and what is a technical or consensus standard?
• Which publication, adoption, effective, application, transition, and enforcement dates differ?
• Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
• How will a source revision affect open work and historical decisions?

Interpretation boundary

The publication does not determine entity scope, contractual sufficiency, materiality, incident classification, testing adequacy, or compliance.