Start hereConfirm entity scope and accountability
~112 days leftOpen step
Guide library
Regulation Europe

DORA

Digital Operational Resilience Act · Regulation (EU) 2022/2554

Organize ICT risk, incident reporting, resilience testing and third-party oversight for EU financial entities.

Who it applies to

Financial entities listed in Article 2, subject to exclusions and proportionality. Separate provisions govern oversight of designated critical ICT third-party providers.

What you’ll produce

Evidence of digital operational resilience governance, testing and ICT provider management.

Use applicable technical standards and competent authority instructions for incident templates, timing, registers and threat-led penetration testing.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which regulated entities and critical functions are in scope?
Have Legal confirm entity types and competent authorities. Business owners decide which functions are critical or important and map the technology and third parties that can interrupt them.
Who can recover the business within its tolerances?
Name accountable service owners and approve recovery targets using business impact. Fund restore testing, vendor due diligence, contract remediation and exit exercises.
Who can file an incident report after hours?
Agree a classification delegate, backups and filing access. Confirm the applicable supervisory route and test it with the incident team.

How to spend the first week

  1. Pick a critical client or business service and map the people, systems, contracts, suppliers and recovery dependencies required to deliver it.
  2. Reconcile the ICT register to Procurement and Finance records. Identify contracts, provider identifiers and functions with missing data.
  3. Walk an outage scenario with Operations, Security and Compliance. Ask the reporting owner to demonstrate how they classify it and find the correct template and regulator.

What to review each week

Track critical functions without tested recovery, invalid register rows, open contract or exit gaps, and incident-report deadlines as separate items.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

DORA kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Confirm entity scope and accountability · Management body + legal [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Pick a critical client or business service and map the people, systems, contracts, suppliers and recovery dependencies required to deliver it.
2. Reconcile the ICT register to Procurement and Finance records. Identify contracts, provider identifiers and functions with missing data.
3. Walk an outage scenario with Operations, Security and Compliance. Ask the reporting owner to demonstrate how they classify it and find the correct template and regulator.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which entity and important functions rely on the ICT supplier?
  • What would an exit or severe disruption look like, and can you test it?

Worked scenario

A financial firm models loss of a managed database service. Its third-party risk team confirms which functions depend on it, tests data export and includes subcontractors in the relevant register fields.

What to read next

  • EU Data Act

    Review cloud switching obligations that may also affect the arrangement.

  • APRA CPS 230

    Compare operational resilience work for an Australian regulated entity if relevant.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
Plan evidence for DORA and other programs
The whole journeyabout 112 days across 4 steps
  1. 01Confirm entity scope and accountabilityManagement body + legal · ~14 days
  2. 02Operate ICT risk and incident controlsCISO + resilience lead · ~35 days
  3. 03Build the ICT third-party registerVendor risk + contracts · ~35 days
  4. 04Test operational resilienceResilience lead + independent testers · ~28 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Confirm entity scope and accountabilityManagement body + legalAt initiationSet a start dateScope memo; Accountability map; Critical-function inventoryOpen
Operate ICT risk and incident controlsCISO + resilience leadOngoing and on incidentsSet a start dateICT risk framework; Incident procedure; Recovery evidenceOpen
Build the ICT third-party registerVendor risk + contractsBefore contracting and ongoingSet a start dateRegister of information; Contract gap analysis; Exit plansOpen
Test operational resilienceResilience lead + independent testersOn applicable test scheduleSet a start dateTesting program; Test reports; Remediation evidenceOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Confirm entity scope and accountability

    Who Management body + legal When At initiation

    Identify regulated entities, critical functions and proportionality. Assign responsibility for ICT risk, incident and third-party governance.

    How to do this step

    Before you start

    Regulatory permissions, group chart, service inventory, business impact records and competent authority instructions.

    1. Map each legal entity to the applicable DORA provisions and supervision. Document group procedures and any applicable entity-level differences.
    2. For each critical or important function, list enabling applications, providers, people, locations and data. Agree the consequence and tolerance for interruption with the business owner.
    3. Bring scope, decision authority and budget to the management body. Record approvals, delegate ownership by entity and appoint backups.

    What a reviewer should see

    The scope matrix links a regulated entity and critical function to its accountable executive, service map and competent authority.

    When to escalate

    Escalate an uncertain entity classification or a critical function whose provider and recovery dependencies nobody owns.

    What to produce

    Scope memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Accountability mapMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

    Critical-function inventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

  2. 02

    Operate ICT risk and incident controls

    Who CISO + resilience lead When Ongoing and on incidents

    Map assets, dependencies and recovery objectives. Classify ICT incidents, test escalation and prepare current reporting templates and clocks.

    How to do this step

    Before you start

    ICT inventory, service dependencies, approved tolerances, applicable classification criteria and regulatory portal contacts.

    1. Map protection, detection, recovery and continuity controls to each critical function. Capture who performs each control and where results live.
    2. Rehearse classifying a major incident and submitting the required notifications and reports. Capture time of awareness and classification separately and use current deadlines and the authority’s procedure.
    3. Run a realistic restore. Measure elapsed time, verify restored data against expectations and assign gaps with target dates.

    What a reviewer should see

    An exercise ticket includes the original alert, timestamps, classification reasoning, regulator destination and the actual restore results.

    When to escalate

    Raise an unstaffed filing route, an incident approaching a deadline or a recovery result outside the approved tolerance.

    What to produce

    ICT risk frameworkMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

    Incident procedureMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

    Recovery evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  3. 03

    Build the ICT third-party register

    Who Vendor risk + contracts When Before contracting and ongoing

    Maintain register entries at the applicable organizational levels, review contract clauses, concentration and subcontracting, and plan tested exits.

    How to do this step

    Before you start

    Contracts, service inventories, provider identifiers, subcontracting records and the reporting templates for the regulated entity.

    1. Match Procurement and Finance records to ICT arrangements. Link contracting and using entities, service identifiers, providers and the functions supported.
    2. Validate required joins and identifiers against the official templates. Arrange input from providers and resolve mismatches before reporting.
    3. Compare critical contracts against applicable clauses and document exit and migration steps. Have Procurement schedule remediation and identify fallback providers or arrangements.

    What a reviewer should see

    One linked set of register rows connects a critical function to its ICT service, signed contract, provider and relevant subcontracting records.

    When to escalate

    Escalate missing information, contract terms that block oversight or an exit plan with unresolved data access or migration barriers.

    What to produce

    Register of informationSpreadsheet

    Gather first

    • Signed contracts and supplier inventory
    • Critical functions, service relationships and subprocessors
    • Reporting instructions and data dictionary when applicable

    How to prepare it

    1. Identify the contracting entity, supplier identifier, service, dates and location. Map dependencies to critical functions and distinguish direct providers from subcontractors.
    2. Gather evidence on security, continuity, location, access and exit. In a required reporting register, use the current authority workbook and allowed identifiers.
    3. Reconcile records against contracts and procurement data, and validate reference keys. Send missing or inconsistent elements to the supplier and record the final approval.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Arrangement ID
    ICT-018, managed database hosting
    Contract and provider
    Enter signed agreement reference and verified legal entity identifier.
    Service and function
    Managed database supporting invoicing. Record entity and function reference.
    Location and subcontractors
    Check documented data locations and supplier chain.
    Evidence and status
    Contract verified, subcontractor fields under review.

    Check before handing it over

    Each provider and contract record links to an actual function and all required identifiers are present.

    Use the verified register in supplier reviews and put required submissions in the authority’s prescribed format.

    Contract gap analysisMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.

    Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.

    Exit plansMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

  4. 04

    Test operational resilience

    Who Resilience lead + independent testers When On applicable test schedule

    Run risk-based testing and track remediation. Confirm whether authorities require threat-led penetration testing and on what scope.

    How to do this step

    Before you start

    Critical function map, risk analysis, incident history, recovery objectives and applicable testing obligations.

    1. Choose scenarios that exercise critical functions and providers. Determine whether threat-led penetration testing applies with the competent authority or the responsible team.
    2. Set success criteria and safeguards before each test. Record results against time, data integrity and service availability targets.
    3. Give failures a root cause, owner, due date and retest. Have management review weaknesses that materially affect service continuity.

    What a reviewer should see

    The test report shows what was exercised, measured results, limitations, fixes and evidence from a retest.

    When to escalate

    Raise recurring failed tolerance tests or an upcoming required exercise without resources or provider participation.

    What to produce

    Testing programMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

    Test reportsMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    Remediation evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes