EvidenceSheet

Art.11 Response and recovery

Financial entities adopt an ICT business continuity policy within their overall continuity policy and implement it through documented arrangements that keep critical or important functions running, contain and resolve incidents, estimate preliminary impacts, and drive crisis communication and reporting under Articles 14 and 19; they run a business impact analysis, keep ICT response and recovery plans, test, at least once a year and after substantive changes, the continuity and response plans for the systems behind every function, test crisis communication plans, and keep records of activity during disruptions. Entities other than microenterprises additionally have the response and recovery plans reviewed by independent internal audit (Art. 11(3)), include cyber-attack and switchover scenarios in testing (Art. 11(6)), run a crisis management function (Art. 11(7)), and estimate aggregated annual costs and losses of major incidents when the authority asks (Art. 11(10)). Central securities depositories also send continuity test results to the authority (Art. 11(9)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

Source: DORA (Regulation (EU) 2022/2554), Art.11. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open DORA (Regulation (EU) 2022/2554) in the compliance library.

Applies to the financial entities listed in Article 2. Many duties are lighter or absent for microenterprises and for the entities in Article 16(1); each statement says where. Article 19 carries the reporting clocks of Delegated Regulation (EU) 2025/301, Article 5.

5
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Internal audit review of the response and recovery plans, crisis management function terms of reference and cyber-attack and switchover test scenarios (entities other than microenterprises) · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • ICT business continuity policy and the business impact analysis it rests on · Policy repository / GRC workspace
  • ICT response and recovery plans with yearly test reports and tests after substantive changes · Policy repository / GRC workspace
  • Crisis communication plan test record and records kept during actual disruptions · Policy repository / GRC workspace
  • Aggregated annual cost and loss estimate for major incidents, where the authority has requested it · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

Art.10 Detection · Art.12 Backup policies and procedures, restoration and recovery