NIST SP 800-161 Rev 1
C-SCRM Family: Configuration Management

NIST SP 800-161 Rev 1 161R1-CM-5: Access Restrictions for Change

Restricts who, including which supplier personnel, may change components, and records when that right is exercised.

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

What else in your programme already covers this

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

  • SEC06-BP03 Reduce manual management and interactive access
  • SEC11-BP06 Deploy software programmatically

C5 (Germany) · 2 controls

CMMC 2.0 · 1 control

FedRAMP High · 1 control

  • CM-5 Access Restrictions for Change

FedRAMP Moderate · 1 control

  • CM-5 Access Restrictions for Change

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.32 Change management

ISO 27002:2022 · 1 control

  • 8.32 Change management

NIST SP 800-218 · 1 control

PCI DSS 4.0 · 1 control

  • 6.5.1 6.5.1 Change control procedure for production

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 C-SCRM Family: Configuration Management

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

NIST SP 800-161 Rev 1 161R1-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-161 Rev 1 your existing evidence covers. Hold C5 (Germany) and 94 of 191 NIST SP 800-161 Rev 1 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 C5 (Germany) pair alone.

Query this from an agent

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