FedRAMP High AC-5: Separation of Duties

What else in your programme already covers this

This control maps to 32 controls across 21 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 · 8 controls

10.1.2 10.1.2 Roles for logging and monitoring assigned and understood
3.7.6 3.7.6 Split knowledge and dual control for manual key operations
7.2.2 7.2.2 User access assigned by job function and least privilege
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
7.2.6 7.2.6 Query access to stored cardholder data restricted
8.6.1 8.6.1 Interactive use of system accounts controlled

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP01 Separate workloads using accounts
SEC11-BP06 Deploy software programmatically

Azure Security Benchmark · 2 controls

ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy
PA-1 Separate and limit highly privileged/administrative users

CIS Controls v8 · 2 controls

CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
CIS-6.8 Define and Maintain Role-Based Access Control

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

CCM-IAM-04 Separation of Duties
CCM-IAM-09 Segregation of Privileged Access Roles

ACSC Essential Eight · 1 control

E8-BACKUP-ML2 Regular Backups (ML2)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles

C5 (Germany) · 1 control

C5-OIS-04 Segregation of Duties

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-3 Information Security Category

CMMC 2.0 · 1 control

AC.L2-3.1.4 Separation of Duties

NIST Cybersecurity Framework 2.0 · 1 control

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 SP 800-161 Rev 1 · 1 control

161R1-AC-5 Separation of Duties

NIST SP 800-171 Rev 3 · 1 control

03.01.04 Separation of Duties

NIST SP 800-172 · 1 control

3.1.1e Dual Authorization for Sensitive System Operations

NIST SP 800-53 Rev 5 · 1 control

NIST800-AC-5 AC-5 Separation of Duties

NIST SP 800-53 Rev 5 HIGH · 1 control

AC-5 AC-5 Separation of Duties

NIST SP 800-53 Rev 5 MODERATE · 1 control

AC-5 AC-5 Separation of Duties

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

CE-AC.5 Separate Admin Accounts for Administrative Activities

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

FedRAMP High AC-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.

If you hold C5 (Germany)29% covered · 291 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. 6 were rejected on the C5 (Germany) pair alone.

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