FedRAMP High
CM - Configuration Management

FedRAMP High CM-5: Access Restrictions for Change

Define, document, approve, enforce physical and logical access restrictions for 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 49 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.

CIS Controls v8 · 6 controls

  • CIS-4.6 Securely Manage Enterprise Assets and Software
  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.1 Establish an Access Granting Process
  • CIS-6.2 Establish an Access Revoking Process
  • CIS-6.7 Centralize Access Control
  • CIS-6.8 Define and Maintain Role-Based Access Control

ISO 27001:2022 · 6 controls

  • 5.3 Segregation of duties
  • 8.19 Installation of software on operational systems
  • 8.2 Privileged access rights
  • 8.3 Information access restriction
  • 8.32 Change management
  • 8.4 Access to source code

PCI DSS 4.0 · 5 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
  • 7.2.3 7.2.3 Privileges approved by authorized personnel
  • 8.4.1 8.4.1 MFA for non-console administrative CDE access
  • 6.5.1 6.5.1 Change control procedure for production
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
  • 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.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied

SOC 2 · 4 controls

  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • 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

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

ISO 27002:2022 · 3 controls

  • 8.19 Installation of software on operational systems
  • 8.32 Change management
  • 8.4 Access to source code
  • SEC06-BP03 Reduce manual management and interactive access
  • SEC11-BP06 Deploy software programmatically

ISO 27701:2019 · 2 controls

  • 6.6.4 System and application access control
  • 6.9.5 Control of operational software
  • E8-MACRO-ML3 Configure Microsoft Office Macro Settings (ML3)

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

NIST SP 800-218 · 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

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 FedRAMP High have you already done?

FedRAMP High CM-5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High 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. 6 were rejected on the C5 (Germany) pair alone.

Query this from an agent

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