DORA
DORA Chapter II: ICT Risk Management

DORA DORA-Art.5: Governance and organisation

What does DORA-Art.5 require?

The management body defines, approves and oversees the ICT risk management framework and carries final accountability for ICT risk: it sets ICT roles and governance, approves the digital operational resilience strategy and ICT risk tolerance, approves and reviews the continuity and response plans, the ICT internal audit plans and the ICT third-party policy, allocates budget for resilience, awareness and skills, and receives reporting on third-party arrangements and major incidents. Its members keep their own ICT risk knowledge current through regular training. Entities other than microenterprises must also set up a role to monitor ICT third-party arrangements, or name a senior manager accountable for that exposure (Art. 5(3)). Applied in proportion to size, risk profile and complexity under Article 4(1). 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 51 controls across 17 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • CPS230-13 Board Accountability for Operational Risk Management
  • CPS230-14 Board Setting of Senior Manager Roles and Responsibilities
  • CPS230-8 Board Oversight, Approval of the BCP, Tolerance Levels and Service Provider Policy
  • CPS230-P23 Senior Management Information to the Board on Resilience Decisions
  • CPS230-P41 BCP Execution Capability and Tolerance Breach Reporting
  • 19 Para 19 Board ultimate accountability for operational risk oversight
  • 21 Para 21 Board oversight duties: risk profile, BCP and tolerances, service provider policy
  • NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
  • NIST-CSF-GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated
  • NIST-CSF-GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • NIST-CSF-GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies

SOC 2 · 5 controls

  • SOC2-CC1.1 CC1.1 Commitment to integrity and ethical values (COSO principle 1)
  • SOC2-CC1.2 CC1.2 Board independence and oversight of internal control (COSO principle 2)
  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
  • SOC2-CC1.5 CC1.5 Accountability for internal control responsibilities (COSO principle 5)
  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)

C5 (Germany) · 4 controls

  • C5-BCM-01 Top management responsibility
  • C5-COM-04 Information on information security performance and management assessment of the ISMS
  • C5-OIS-02 Information Security Policy
  • C5-OIS-04 Segregation of Duties

NIST SP 800-161 Rev 1 · 4 controls

  • CFTC-SS-2 Enterprise Risk Management and Governance Category
  • CFTC-SS-23 Resources Sufficient to Fulfil Obligations
  • CFTC-SS-36 Internal Reporting and Review by Senior Management and the Board

ISO 27001:2022 · 3 controls

  • 5.1 Policies for information security
  • 5.2 Information security roles and responsibilities
  • 5.4 Management responsibilities

ISO 27002:2022 · 3 controls

  • 5.1 Policies for information security
  • 5.2 Information security roles and responsibilities
  • 5.4 Management responsibilities

NIST SP 800-53 Rev 5 · 3 controls

FedRAMP High · 2 controls

  • CA-6 Authorization
  • SA-2 Allocation of Resources

FedRAMP Moderate · 2 controls

  • CA-6 Authorization
  • SA-2 Allocation of Resources

NIS2 Directive · 2 controls

  • Art.20.1 Management body approves the cybersecurity risk-management measures and oversees their implementation
  • Art.20.2 Train the management body, and offer equivalent training to staff on a regular basis
  • PSD2-Art.95 Management of operational and security risks (PSD2 Article 95)

GDPR · 1 control

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