FedRAMP High
AC - Access Control

FedRAMP High AC-5: Separation of Duties

Identify and document duties requiring separation; define access authorizations to support.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 30 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 · 8 controls

  • 10.1.2 Requirement 10 roles and responsibilities documented and assigned
  • 3.7.6 Manual cleartext key operations use split knowledge
  • 7.2.2 Access is assigned to users, including privileged users, based on: • Job classification and function. • Least privileges necessary to perform job responsibilities
  • 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.
  • 7.2.5 All application and system accounts and related access privileges are assigned and managed as follows: • Based on the least privileges necessary for the operability of the system or application. • Access is limited
  • 7.2.6 All user access to query repositories of stored cardholder data is restricted as follows: • Via applications or other programmatic methods, with access and allowed actions based on user roles and least privileges. •
  • 8.6.1 If accounts used by systems or applications can be used for interactive login, they are managed as follows: • Interactive use is prevented unless needed for an exceptional circumstance. • Interactive use is limited
  • 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
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 5.3 Segregation of duties

ISO 27002:2022 · 1 control

  • 5.3 Segregation of duties
  • 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-172 · 1 control

  • 3.1.1e Dual Authorization for Sensitive System Operations

SOC 2 · 1 control

  • SOC2-CC6.3 Role-based access and least privilege are enforced

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.

Other controls in AC - Access Control

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.

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 30 it maps to, and the evidence behind each claim, over MCP and REST.