NIST SP 800-218
NIST SP 800-218: Information Security Policies

NIST SP 800-218 SP800-218-PO.2.3: Obtain Management Commitment to Secure Development

Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all personnel with software-development-related roles.

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

What else in your programme already covers this

This control maps to 23 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 SP 800-161 Rev 1 · 3 controls

  • ASBv3-GS-10 Define and implement DevOps security strategy
  • GS-1 Align organization roles, responsibilities and accountabilities

BSIMM · 2 controls

  • SM1.1 Publish process and evolve as necessary
  • SM1.3 Educate executives on software security

C5 (Germany) · 2 controls

  • C5-OIS-02 Information Security Policy
  • C5-SP-02 Review and Approval of Policies and Instructions
  • CCM-AIS-01 Application and Interface Security Policy and Procedures
  • CCM-GRC-01 Governance Program Policy and Procedures

ISO 27002:2022 · 2 controls

  • 5.1 Policies for information security
  • 5.4 Management responsibilities

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC1.2 CC1.2 Board independence and oversight of internal control (COSO principle 2)
  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)

FedRAMP High · 1 control

  • SA-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • SA-1 Policy and Procedures

ISO 27001:2022 · 1 control

  • 5.4 Management responsibilities

ISO/IEC 42001:2023 · 1 control

  • 5.1 Leadership and commitment
  • 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

PCI DSS 4.0 · 1 control

  • 12.1.1 12.1.1 Overall information security policy established and disseminated

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 NIST SP 800-218: Information Security Policies

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

NIST SP 800-218 SP800-218-PO.2.3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-218 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 30 of 42 NIST SP 800-218 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 NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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