NIST SP 800-218
Protect the Software

NIST SP 800-218 SP800-218-PS.1.1: Protect All Forms of Code from Unauthorized Modification

Apply controls to source code, infrastructure as code, and build scripts so that only authorized contributors can change them and all changes are reviewed and logged. Protect main branches and require pull request reviews.

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

What else in your programme already covers this

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

C5 (Germany) · 6 controls

OpenSSF Open Source Project Security Baseline (OSPS Baseline) · 5 controls

  • OSPS-AC-02.01 OSPS-AC-02.01 Restrict Collaborator Permissions
  • OSPS-AC-03.01 OSPS-AC-03.01 Protect the Primary Branch from Accidental Modification
  • OSPS-AC-03.02 OSPS-AC-03.02 Protect the Primary Branch from Accidental Modification
  • OSPS-GV-04.01 OSPS-GV-04.01 Require Formal Review of Permission Grants
  • OSPS-QA-01.02 OSPS-QA-01.02 Publish Source Code and Change History

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 4 controls

FedRAMP High · 4 controls

  • CM-3 Configuration Change Control
  • CM-5 Access Restrictions for Change
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))
  • SA-10 Developer Configuration Management

FedRAMP Moderate · 4 controls

  • CM-3 Configuration Change Control
  • CM-5 Access Restrictions for Change
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))
  • SA-10 Developer Configuration Management

AWS Well-Architected Security Pillar · 3 controls

CMMC 2.0 · 3 controls

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

SOC 2 · 3 controls

  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

Azure Security Benchmark · 2 controls

  • ASBv3-DS-3 Secure DevOps infrastructure
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle

ISO 27001:2022 · 2 controls

  • 8.32 Change management
  • 8.4 Access to source code

ISO 27002:2022 · 2 controls

  • 8.32 Change management
  • 8.4 Access to source code

ISO/IEC 42001:2023 · 2 controls

  • 7.5.3 Control of documented information
  • 8.3 AI risk treatment

PCI DSS 4.0 · 2 controls

  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.4 6.5.4 Separate roles between production and pre-production

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.1.1e Dual Authorization for Sensitive System Operations

OpenSSF Scorecard · 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 Protect the Software

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

NIST SP 800-218 SP800-218-PS.1.1 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.

If you hold NIST SP 800-53 Rev 571.4% covered · 12 gapsIf you hold C5 (Germany)61.9% covered · 16 gapsIf you hold NIST SP 800-161 Rev 161.9% covered · 16 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.152.4% covered · 20 gapsIf you hold ISO 27002:202252.4% covered · 20 gapsIf you hold Azure Security Benchmark50% covered · 21 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll NIST SP 800-218 controls