CMMC 2.0 CM.L2-3.4.5: Access Restrictions for Change

What else in your programme already covers this

This control maps to 38 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 · 4 controls

1.2.2 Changes to NSC reviewed and approved
6.5.1 Changes to all system components in the production environment are made according to established procedures that include: • Reason for, and description of, the change. • Documentation of security impact. • Documented change approval
6.5.4 Roles and functions are separated between production and pre-production environments to provide accountability such that only reviewed and approved changes are deployed
7.2.4 All user accounts and related access privileges, including third-party/vendor accounts, are reviewed as follows: • At least once every six months. • To ensure user accounts and access remain appropriate based on job function.

SOC 2 · 4 controls

SOC2-CC5.1 COSO principle 10: Selects and develops control activities to mitigate risks
SOC2-CC6.2 Prior to granting access, registration and authorization processes are established
SOC2-CC6.3 Role-based access and least privilege are enforced
SOC2-CC8.1 Change management processes are in place

FedRAMP High · 3 controls

CM-5 Access Restrictions for Change
CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records. (a) Enforce access restrictions using [Assignment: organization-defined automated mechanisms]; and (b) Automatically generate audit records of the enforcement actions
CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation. (a) Limit privileges to change system components and system-related information within a production or operational environment; and (b) Review and reevaluate privileges [Assignment:

FedRAMP Moderate · 3 controls

CM-5 Access Restrictions for Change
CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records. (a) Enforce access restrictions using [Assignment: organization-defined automated mechanisms]; and (b) Automatically generate audit records of the enforcement actions
CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation. (a) Limit privileges to change system components and system-related information within a production or operational environment; and (b) Review and reevaluate privileges [Assignment:

AWS Well-Architected Security Pillar · 2 controls

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

Azure Security Benchmark · 2 controls

ASBv3-AM-4 Limit access to asset management
ASBv3-DS-3 Secure DevOps infrastructure

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 27001:2022 · 2 controls

8.32 Change management
8.4 Access to source code

NIST SP 800-53 Rev 5 · 2 controls

NIST800-CM-1 Policy and procedures for configuration management
NIST800-CM-5 Access restrictions for change

NIST SP 800-53 Revision 5.1 HIGH · 2 controls

CM-5 Access Restrictions for Change
CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records. (a) Enforce access restrictions using [Assignment: organization-defined automated mechanisms]; and (b) Automatically generate audit records of the enforcement actions

ACSC Essential Eight · 1 control

E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)

C5 (Germany) · 1 control

C5-DEV-09 Approvals for provision in the production environment

HIPAA Security Rule · 1 control

164.310(a)(2)(iii) Access Control and Validation Procedures (Addressable)

NIST Cybersecurity Framework 2.0 · 1 control

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

NIST SP 800-161 Rev 1 · 1 control

161R1-CM-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-PS.1.1 Protect All Forms of Code from Unauthorized Modification

NIST SP 800-53 Rev 5 LOW · 1 control

CM-5 Access Restrictions for Change

NIST SP 800-53 Rev 5 MODERATE · 1 control

CM-5 Access Restrictions for Change

NIST SP 800-66 Rev 2 · 1 control

164.310(a)(2)(iii) Access Control and Validation Procedures (Addressable)

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 CMMC 2.0 have you already done?

CMMC 2.0 CM.L2-3.4.5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

If you hold FedRAMP Moderate98.2% covered · 2 gaps If you hold NIST SP 800-171 Rev 394.5% covered · 6 gaps If you hold NIST SP 800-53 Rev 585.5% covered · 16 gaps If you hold ISO 27001:202279.1% covered · 23 gaps If you hold ISO 27002:202267.3% covered · 36 gaps If you hold CIS Controls v864.5% covered · 39 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. 1 were rejected on the FedRAMP Moderate pair alone.

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