DORA
DORA Chapter II: ICT Risk Management

DORA DORA-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.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 59 controls across 16 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • CFTC-SS-11 Testing and Review of Business Continuity and Disaster Recovery Capabilities
  • CFTC-SS-22 Business Continuity and Disaster Recovery Planning Category
  • CFTC-SS-27 Coordination of the Recovery Plan with Members and Market Participants
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources
  • CFTC-SS-9 Next Business Day Recovery Time Objective

FedRAMP High · 5 controls

  • CP-1 Policy and Procedures
  • CP-10 System Recovery and Reconstitution
  • CP-2 Contingency Plan
  • CP-4 Contingency Plan Testing
  • CP-7 Alternate Processing Site

FedRAMP Moderate · 5 controls

  • CP-1 Policy and Procedures
  • CP-10 System Recovery and Reconstitution
  • CP-2 Contingency Plan
  • CP-4 Contingency Plan Testing
  • CP-7 Alternate Processing Site
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
  • NIST-CSF-RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared
  • NIST-CSF-RS.MI-01 Incidents are contained

CIS Controls v8 · 4 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-11.5 Test Data Recovery
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-17.7 Conduct Routine Incident Response Exercises

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption
  • CPS230-20 Prevention, Adaptation and Return to Normal Operations
  • CPS230-26 Critical Operations Register, Continuity Plan and Activation
  • CPS230-P40 Required Content of the Business Continuity Plan

C5 (Germany) · 3 controls

  • C5-BCM-03 Planning business continuity
  • C5-BCM-04 Verification, updating and testing of the business continuity
  • C5-OPS-08 Data Backup and Recovery - Regular Testing

ISO 27001:2022 · 3 controls

  • 5.26 Response to information security incidents
  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity

ISO 27002:2022 · 3 controls

  • 5.26 Response to information security incidents
  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity

NIST SP 800-161 Rev 1 · 3 controls

  • EBA-GL-3.7.1 Business impact analysis
  • EBA-GL-3.7.3 Response and recovery plans

NIS2 Directive · 1 control

  • Art.21.2.c Business continuity, backup management, disaster recovery and crisis management

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in DORA Chapter II: ICT Risk Management

You are reading one control. How much of DORA have you already done?

DORA DORA-Art.11 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of DORA your existing evidence covers. Hold NIS2 Directive and 17 of 26 DORA controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIS2 Directive pair alone.

Query this from an agent

The graph holds this control, the 59 it maps to, and the evidence behind each claim, over MCP and REST.