NIST SP 800-171 Rev 3
03.04 CM (Configuration Management)

NIST SP 800-171 Rev 3 03.04.05: Access Restrictions for Change

Define, document, approve, and enforce physical and logical access restrictions associated with system changes.

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

What else in your programme already covers this

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

FedRAMP High · 3 controls

  • CM-5 Access Restrictions for Change
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))
  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))

FedRAMP Moderate · 3 controls

  • CM-5 Access Restrictions for Change
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))
  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))

ISO 27001:2022 · 3 controls

  • 8.19 Installation of software on operational systems
  • 8.32 Change management
  • 8.4 Access to source code
  • SEC11-BP06 Deploy software programmatically
  • SEC11-BP07 Regularly assess security properties of the pipelines

C5 (Germany) · 2 controls

  • C5-DEV-07 Logging of changes
  • C5-DEV-09 Approvals for provision in the production environment

ISO 27002:2022 · 2 controls

  • 8.19 Installation of software on operational systems
  • 8.32 Change management
  • 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-CSF-PR.PS-01 Configuration management practices are established and applied

PCI DSS 4.0 · 2 controls

  • 1.2.8 1.2.8 NSC configuration files secured and consistent
  • 6.5.3 6.5.3 Separate pre-production from production

CMMC 2.0 · 1 control

NIST SP 800-172 · 1 control

  • 3.1.1e Dual Authorization for Sensitive System Operations

SOC 2 · 1 control

  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

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 03.04 CM (Configuration Management)

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

NIST SP 800-171 Rev 3 03.04.05 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 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 PCI DSS 4.0 pair alone.

Query this from an agent

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