NIST SP 800-161 Rev 1
C-SCRM Family: Access Control

NIST SP 800-161 Rev 1 161R1-AC-5: Separation of Duties

Separates the duties that would let one party both select or supply a component and approve its acceptance.

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

What else in your programme already covers this

This control maps to 20 controls across 17 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

C5 (Germany) · 2 controls

  • C5-DEV-09 Approvals for provision in the production environment
  • C5-OIS-04 Segregation of Duties

ISO 27001:2022 · 2 controls

  • 5.3 Segregation of duties
  • 8.4 Access to source code

ISO 27002:2022 · 2 controls

  • 5.3 Segregation of duties
  • 8.4 Access to source code
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles

APRA CPS 234 · 1 control

  • CPS234-P30 Independence and Skill of Testing Personnel
  • ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy

CMMC 2.0 · 1 control

FedRAMP High · 1 control

  • AC-5 Separation of Duties

FedRAMP Moderate · 1 control

  • AC-5 Separation of Duties

NIST SP 800-172 · 1 control

  • 3.1.1e Dual Authorization for Sensitive System Operations

NIST SP 800-218 · 1 control

PCI DSS 4.0 · 1 control

  • 6.5.4 6.5.4 Separate roles between production and pre-production

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 C-SCRM Family: Access Control

You are reading one control. How much of NIST SP 800-161 Rev 1 have you already done?

NIST SP 800-161 Rev 1 161R1-AC-5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-161 Rev 1 your existing evidence covers. Hold C5 (Germany) and 94 of 191 NIST SP 800-161 Rev 1 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. 0 were rejected on the C5 (Germany) pair alone.

Query this from an agent

The graph holds this control, the 20 it maps to, and the evidence behind each claim, over MCP and REST.