C5 (Germany)
C5: Organisation of Information Security

C5 (Germany) C5-OIS-04: Segregation of Duties

Separate conflicting duties on the basis of the documented risk assessment, at minimum across rights administration and access approval, change development, testing and release, and system operation, and where separation is not feasible monitor those activities to detect misuse or unintended change.

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

What else in your programme already covers this

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

SOC 2 · 4 controls

  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
  • SOC2-CC3.3 CC3.3 Considering fraud risk (COSO principle 8)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

NIST SP 800-218 · 3 controls

  • SEC03-BP05 Define permission guardrails for your organization
  • SEC11-BP06 Deploy software programmatically

ISO 27001:2022 · 2 controls

  • 5.2 Information security roles and responsibilities
  • 5.3 Segregation of duties

ISO 27002:2022 · 2 controls

  • 5.2 Information security roles and responsibilities
  • 5.3 Segregation of duties
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • 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 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.1.1e Dual Authorization for Sensitive System Operations
  • 3.9.2e Insider Threat Program
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • CPS220-P35 Required Content of Risk Management Policies and Procedures

APRA CPS 234 · 1 control

  • CPS234-14 Definition of Information Security Roles and Responsibilities
  • ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy

CMMC 2.0 · 1 control

DORA · 1 control

FedRAMP High · 1 control

  • AC-5 Separation of Duties

FedRAMP Moderate · 1 control

  • AC-5 Separation of Duties

ISO 27018:2019 · 1 control

  • 6.1.2 Segregation of duties

PCI DSS 4.0 · 1 control

  • 6.5.4 6.5.4 Separate roles between production and pre-production

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 C5: Organisation of Information Security

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-OIS-04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) 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 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

Query this from an agent

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