DORA
DORA Chapter II: ICT Risk Management

DORA DORA-Art.5: Governance and organisation

The management body of the financial entity shall define, approve, oversee and be responsible for the implementation of the ICT risk management framework, bear ultimate responsibility for managing ICT risk, set roles and responsibilities, approve the digital operational resilience strategy, and allocate appropriate budget and training.

What else in your programme already covers this

This control maps to 55 controls across 20 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
  • 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 COSO principle 1: Demonstrates commitment to integrity and ethical values
  • SOC2-CC1.2 COSO principle 2: Board exercises oversight responsibility
  • SOC2-CC1.3 COSO principle 3: Management establishes structures, reporting lines, and authorities
  • SOC2-CC1.5 COSO principle 5: Holds individuals accountable for internal control responsibilities
  • SOC2-CC4.2 COSO principle 17: Evaluates and communicates deficiencies in a timely manner

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

  • NIST800-PM-2 Information Security Program Leadership Role. Appoint a senior agency information security officer with the mission and resources to coordinate, develop, implement, and maintain an organization-wide information security program
  • NIST800-PM-29 Risk Management Program Leadership Roles. Appoint a Senior Accountable Official for Risk Management to align organizational information security and privacy management processes with strategic, operational, and budgetary planning processes; and Establish a Risk Executive
  • NIST800-PM-3 Information Security and Privacy Resources. Include the resources needed to implement the information security and privacy programs in capital planning and investment requests and document all exceptions to this requirement; Prepare documentation required for

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
  • CA-6 Authorization
  • SA-2 Allocation of Resources
  • CA-6 Authorization
  • SA-2 Allocation of Resources
  • CA-6 Authorization
  • SA-2 Allocation of Resources
  • 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 55 it maps to, and the evidence behind each claim, over MCP and REST.