NIST SP 800-53 Rev 5
CM - Configuration Management

NIST SP 800-53 Rev 5 NIST800-CM-5: CM-5 Access Restrictions for Change

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

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

What else in your programme already covers this

This control maps to 48 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.

PCI DSS 4.0 · 8 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 1.2.8 1.2.8 NSC configuration files secured and consistent
  • 10.6.3 10.6.3 Time sync configuration and time data protected
  • 5.3.5 5.3.5 Users cannot disable or alter anti-malware
  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.3 6.5.3 Separate pre-production from production
  • 6.5.4 6.5.4 Separate roles between production and pre-production
  • 7.2.5 7.2.5 Application and system accounts least privilege

ISO 27002:2022 · 4 controls

  • 8.19 Installation of software on operational systems
  • 8.32 Change management
  • 8.34 Protection of information systems during audit testing
  • 8.4 Access to source code

C5 (Germany) · 3 controls

  • C5-DEV-07 Logging of changes
  • C5-DEV-09 Approvals for provision in the production environment
  • C5-OPS-16 Logging and Monitoring - Configuration

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

NIST SP 800-218 · 3 controls

SOC 2 · 3 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SEC11-BP06 Deploy software programmatically
  • SEC11-BP07 Regularly assess security properties of the pipelines

CMMC 2.0 · 2 controls

NIST SP 800-128 · 2 controls

  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked

NIST SP 800-172 · 1 control

  • 3.1.1e Dual Authorization for Sensitive System Operations

NIST SP 800-207 · 1 control

  • CM-5 CM-5 Access Restrictions for Change
  • CM-5 CM-5 Access Restrictions for Change
  • CM-5 CM-5 Access Restrictions for Change

UK Cyber Essentials · 1 control

  • CE-AC.5 Separate Admin Accounts for Administrative Activities

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 CM - Configuration 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-CM-5 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 48 it maps to, and the evidence behind each claim, over MCP and REST.