NIST SP 800-53 Rev 5
PM - Program Management

NIST SP 800-53 Rev 5 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

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

What else in your programme already covers this

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

NIST Cybersecurity Framework 2.0 · 8 controls

  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
  • NIST-CSF-GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes
  • NIST-CSF-GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated
  • NIST-CSF-GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties
  • 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

APRA CPS 220 Risk Management · 4 controls

  • CPS220-09 Designation of a Chief Risk Officer
  • CPS220-10 Designated Risk Management Function
  • CPS220-P39 Independence of the Chief Risk Officer
  • CPS220-P40 Chief Risk Officer Reporting Lines and Board Access

APRA CPS 230 Operational Risk Management · 2 controls

  • CPS230-13 Board Accountability for Operational Risk Management
  • CPS230-14 Board Setting of Senior Manager Roles and Responsibilities

ISO 22301:2019 · 2 controls

  • 5.1 Leadership and commitment
  • 5.3 Roles, responsibilities and authorities

ISO 27001:2022 · 2 controls

  • 5.2 Information security roles and responsibilities
  • 5.4 Management responsibilities

ISO 27002:2022 · 2 controls

  • 5.2 Information security roles and responsibilities
  • 5.4 Management responsibilities

NIST SP 800-181 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC1.2 COSO principle 2: Board exercises oversight responsibility
  • SOC2-CC1.3 COSO principle 3: Management establishes structures, reporting lines, and authorities

C5 (Germany) · 1 control

  • C5-OIS-01 Information Security Management System (ISMS)

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

DORA · 1 control

ISO 27701:2019 · 1 control

  • 5.3.3 Organizational roles, responsibilities and authorities

ISO/IEC 42001:2023 · 1 control

  • 5.1 Leadership and commitment

NIST SP 800-161 Rev 1 · 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 PM - Program Management

You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 PM-29 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 300 NIST SP 800-53 Rev 5 controls already carry evidence.

If you hold ISO 27001:202254.3% covered · 137 gapsIf you hold ISO 27002:202236.7% covered · 190 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.134.3% covered · 197 gapsIf you hold CIS Controls v834% covered · 198 gapsIf you hold NIST SP 800-171 Rev 334% covered · 198 gapsIf you hold C5 (Germany)32.3% covered · 203 gaps

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. 342 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll NIST SP 800-53 Rev 5 controls