CMMC 2.0 SC.L2-3.13.3: Role Separation

What else in your programme already covers this

This control maps to 29 controls across 19 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

2.2.3 2.2.3 Primary functions with different security levels managed
7.3.2 7.3.2 Access control system enforces role-based permissions
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
8.6.1 8.6.1 Interactive use of system accounts controlled

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 3 controls

ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
ANSSI-HYG-27 Prohibit Internet Access from Administration Workstations and Servers
ANSSI-HYG-28 Use a Dedicated and Partitioned Network for Administration

Azure Security Benchmark · 2 controls

ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy
ASBv3-PA-6 Use privileged access workstations

ISO 27002:2022 · 2 controls

5.3 Segregation of duties
8.27 Secure system architecture and engineering principles

ISO 27701:2019 · 2 controls

6.3.1 Internal organization
6.9.1 Operational procedures and responsibilities

ACSC Essential Eight · 1 control

E8-ADMIN-ML1 Restrict Administrative Privileges (ML1)

AWS Well-Architected Security Pillar · 1 control

SEC01-BP01 Separate workloads using accounts

C5 (Germany) · 1 control

C5-COS-05 Networks for administration

CIS Controls v8 · 1 control

CIS-12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-IAM-09 Segregation of Privileged Access Roles

FedRAMP High · 1 control

SC-2 Separation of System and User Functionality

FedRAMP Moderate · 1 control

SC-2 Separation of System and User Functionality

ISO/IEC 42001:2023 · 1 control

5.3 Roles, responsibilities and authorities

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-171 Rev 3 · 1 control

03.01.06 Least Privilege - Privileged Accounts

NIST SP 800-172 · 1 control

3.13.2e Introduce Unpredictability into System Operations

NIST SP 800-53 Rev 5 · 1 control

NIST800-SC-2 SC-2 Separation of System and User Functionality

SOC 2 · 1 control

SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

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 SC.L2-3.13.3 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