European Union

DORA

26 controls. 32 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

26 controls 32 frameworks share controls with it European Union verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

DORA Evidence & Implementation Kit

26 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
DORA-Art.10Detection15
DORA-Art.11Response and recovery16
DORA-Art.12Backup policies and procedures, restoration and recovery16
DORA-Art.13Learning and evolving16
DORA-Art.14Communication17
DORA-Art.16Simplified ICT risk management framework10
DORA-Art.17ICT-related incident management process19
DORA-Art.18Classification of ICT-related incidents and cyber threats13
DORA-Art.19Reporting of major ICT-related incidents17
DORA-Art.23Operational or security payment-related incidents10
DORA-Art.24General requirements for the performance of digital operational resilience testing17
DORA-Art.25Testing of ICT tools and systems15
DORA-Art.26Advanced testing of ICT tools, systems and processes based on TLPT9
DORA-Art.27Requirements for testers for the carrying out of TLPT8
DORA-Art.28ICT third-party risk: general principles23
DORA-Art.29Preliminary assessment of ICT concentration risk at entity level13
DORA-Art.30Key contractual provisions21
DORA-Art.31Designation of critical ICT third-party service providers11
DORA-Art.45Information-sharing arrangements on cyber threat information and intelligence12
DORA-Art.5Governance and organisation17
DORA-Art.50Administrative penalties and remedial measures13
DORA-Art.56Data protection13
DORA-Art.6ICT risk management framework19
DORA-Art.7ICT systems, protocols and tools13
DORA-Art.8Identification20
DORA-Art.9Protection and prevention18

Tell me when DORA files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Crisis communication plan for major ICT incidents
  • Crisis communication plan and stakeholder contact lists
  • Records of recovery communications to internal/external parties
  • Public-relations and reputation-management procedures
  • Crisis communication plan and stakeholder/contact lists
  • Records of notifications during incidents
  • Backup policy stating data scope and minimum backup frequency by criticality
  • Restoration test reports from periodic backup and recovery tests
  • Architecture records showing restore environments separated physically and logically from source systems
  • Recovery time and recovery point objective register per function

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for DORA, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition