DORA
DORA Chapter II: ICT Risk Management

DORA DORA-Art.16: Simplified ICT risk management framework

What does DORA-Art.16 require?

Articles 5 to 15 are disapplied for: investment firms that are small and non-interconnected; payment institutions and electronic money institutions exempted under their directives; institutions exempted under Directive 2013/36/EU where the Member State has not used the Article 2(4) option; and small occupational retirement institutions (IORPs). These entities instead keep a sound, documented ICT risk management framework, monitor ICT systems continuously, use resilient and updated systems that protect data, detect anomalies and handle incidents quickly, identify key ICT third-party dependencies, keep business continuity plans with at least backup and restoration measures, test those plans and controls regularly, and apply lessons and training according to their risk profile. The framework is reviewed periodically and after major incidents, with a review report available on request (Art. 16(2)). The detailed requirements are in Title III (Articles 28 to 41) of Commission Delegated Regulation (EU) 2024/1774. These entities are also excluded from TLPT (Art. 26(1)) and from the ICT third-party risk strategy duty (Art. 28(2)).

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

What else in your programme already covers this

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

CIS Controls v8 · 3 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-13.1 Centralize Security Event Alerting
  • CIS-17.4 Establish and Maintain an Incident Response Process

FedRAMP High · 3 controls

  • CP-2 Contingency Plan
  • IR-4 Incident Handling
  • SI-4 System Monitoring

FedRAMP Moderate · 3 controls

  • CP-2 Contingency Plan
  • IR-4 Incident Handling
  • SI-4 System Monitoring

ISO 27001:2022 · 3 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.30 ICT readiness for business continuity
  • 8.16 Monitoring activities

ISO 27002:2022 · 3 controls

  • 5.24 Information security incident management planning and preparation
  • 5.30 ICT readiness for business continuity
  • 8.16 Monitoring activities
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations

NIST SP 800-53 Rev 5 · 3 controls

SOC 2 · 3 controls

  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

NIS2 Directive · 1 control

  • Art.21.1 Take proportionate all-hazards measures calibrated to the entity's own risk exposure

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.16 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 28 it maps to, and the evidence behind each claim, over MCP and REST.