NIST SP 800-53 Rev 5
PM - Program Management

NIST SP 800-53 Rev 5 NIST800-PM-2: 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.

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

What else in your programme already covers this

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

ISO/IEC 42001:2023 · 5 controls

  • 5.1 Leadership and commitment
  • 5.3 Roles, responsibilities and authorities
  • 7.1 Resources
  • A.3 Internal organization
  • A.3.2 AI roles and responsibilities

ISO 22301:2019 · 4 controls

  • 4.1 Understanding the organization and its context
  • 5.1 Leadership and commitment
  • 5.3 Roles, responsibilities and authorities
  • 7.1 Resources

ISO 27701:2019 · 4 controls

  • 5.3.1 Leadership and commitment
  • 5.3.3 Organizational roles, responsibilities and authorities
  • 6.2.1 Management direction for information security
  • 6.3.1 Internal organization
  • 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 · 3 controls

  • 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.4 CC1.4 Attracting, developing and retaining competent people (COSO principle 4)
  • CPS220-09 Designation of a Chief Risk Officer
  • CPS220-P40 Chief Risk Officer Reporting Lines and Board Access

APRA CPS 234 · 2 controls

  • CPS234-13 Board Responsibility for Information Security
  • CPS234-14 Definition of Information Security Roles and Responsibilities

ISO 27002:2022 · 2 controls

  • 5.2 Information security roles and responsibilities
  • 5.4 Management responsibilities
  • ANSSI-HYG-39 Designate an Information System Security Officer and Make the Role Known
  • CPS230-14 Board Setting of Senior Manager Roles and Responsibilities
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • GS-1 Align organization roles, responsibilities and accountabilities

C5 (Germany) · 1 control

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

DORA · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.2 Information security roles and responsibilities

NIS2 Directive · 1 control

  • Art.20.1 Management body approves the cybersecurity risk-management measures and oversees their implementation
  • 161R1-PM-2 Information Security Program Leadership Role

NIST SP 800-181 · 1 control

PCI DSS 4.0 · 1 control

  • 12.1.4 12.1.4 Executive ownership of information security formally assigned

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 NIST800-PM-2 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 1014 NIST SP 800-53 Rev 5 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. 342 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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