FedRAMP Moderate CM-5(5): Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))

What else in your programme already covers this

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

PCI DSS 4.0 · 6 controls

6.5.6 6.5.6 Remove test data and accounts before production
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.4 7.2.4 User accounts and privileges reviewed every six months
7.2.5 7.2.5 Application and system accounts least privilege

Azure Security Benchmark · 3 controls

ASBv3-DS-3 Secure DevOps infrastructure
ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy
ASBv3-PA-7 Follow just enough administration (least privilege) principle

ISO 27001:2022 · 3 controls

8.2 Privileged access rights
8.32 Change management
8.4 Access to source code

ISO 27002:2022 · 3 controls

8.2 Privileged access rights
8.32 Change management
8.4 Access to source code

AWS Well-Architected Security Pillar · 2 controls

SEC06-BP03 Reduce manual management and interactive access
SEC11-BP07 Regularly assess security properties of the pipelines

CIS Controls v8 · 2 controls

CIS-16.8 Separate Production and Non-Production Systems
CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts

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

CCM-CCC-04 Unauthorized Change Protection
CCM-IVS-05 Production and Non-Production Environments

ISO 27701:2019 · 2 controls

6.11.3 Test data
6.9.1 Operational procedures and responsibilities

SOC 2 · 2 controls

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) · 1 control

C5-DEV-10 Separation of environments

CMMC 2.0 · 1 control

CM.L2-3.4.5 Access Restrictions for Change

NIST SP 800-171 Rev 3 · 1 control

03.04.05 Access Restrictions for Change

NIST SP 800-172 · 1 control

3.1.1e Dual Authorization for Sensitive System Operations

NIST SP 800-218 · 1 control

SP800-218-PO.5.1 Secure Development Environment Implementation

NIST SP 800-53 Rev 5 · 1 control

NIST800-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.

You are reading one control. How much of FedRAMP Moderate have you already done?

FedRAMP Moderate CM-5(5) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

If you hold ISO 27002:202256.3% covered · 141 gaps If you hold PCI DSS 4.051.1% covered · 158 gaps If you hold ISO 27001:202249.8% covered · 162 gaps If you hold NIST SP 800-171 Rev 345.5% covered · 176 gaps If you hold C5 (Germany)37.2% covered · 203 gaps If you hold CMMC 2.035% covered · 210 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. 348 were rejected on the ISO 27002:2022 pair alone.

See the released pairs, $299 each Browse the graph free