# BSI C5:2020 OIS-04 — Segregation of Duties - Source: https://support.icompaas.com/compliance/bsi-c5-2020/ois-04-segregation-of-duties - Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Information Security Governance (OIS) - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **BSI C5:2020**·Criterion `OIS-04`·high·Component: **Information Security Governance** ## What this control requires > Separates conflicting tasks based on OIS-06 risk assessment to prevent unauthorized changes or misuse of cloud customer data. Covers rights administration, development/testing, and system operations. Implements monitoring measures when separation is infeasible to detect and address unauthorized activities promptly. > > — BSI C5:2020, Criterion OIS-04 ### In plain English Separates conflicting tasks based on OIS-06 risk assessment to prevent unauthorized changes or misuse of cloud customer data. In practice, this means you can prove you information measures-level controls on a defined cadence. ## Why it matters BSI C5 is the default cloud-security baseline German public-sector buyers and many DAX-listed enterprises expect; gaps here directly block procurement in the DACH region and frequently appear as must-have items in EU public-tender documents. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A C5 attesting auditor (under ISAE 3000 / IDW PS 860) tests both the design and — for a Type 2 — the operating effectiveness over the attestation period. For each criterion they look for both the Basic and any in-scope Additional objectives. Within **Information Security Governance**, the assessor will trace your implementation back to the catalogue reference (Criterion OIS-04) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Cloud Posture **CSPM.** Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold. ### Operational checklist - **Information.** Document the trigger, the owner and the cadence. - **Segregation.** Document the trigger, the owner and the cadence. - **Risk.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Scope:** measures, cloud customer data, administration, development, changes, management. ## Evidence to collect - **Identity Scan.** IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Segregation of Duties. ## Common pitfalls - Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.3.1** — Event Logging](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-3-1-event-logging) - [**SOC 2 (2017 TSC) CC6.2** — Access Provisioning](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-2-access-provisioning) - [**ISO/IEC 27001:2022 A.8.2** — Privileged access rights](https://support.icompaas.com/compliance/iso-27001-2022/a-8-2-privileged-access-rights) - [**CIS Controls v8 14.9** — Conduct Role-Specific Security Awareness and Skills Training](https://support.icompaas.com/compliance/cis-controls-v8/14-9-conduct-role-specific-security-awareness-and-skills-training) - [**NIST SP 800-53 Rev. 5 AC-6(6)** — Privileged Access By Non-Organizational Users](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-6-6-privileged-access-by-non-organizational-users) ## Related controls in BSI C5:2020 - [**Criterion IDM-06** — Privileged access rights](https://support.icompaas.com/compliance/bsi-c5-2020/idm-06-privileged-access-rights) - [**Criterion DEV-07** — Logging of changes](https://support.icompaas.com/compliance/bsi-c5-2020/dev-07-logging-of-changes) - [**Criterion IDM-04** — Withdraw or adjust access rights as the task area changes](https://support.icompaas.com/compliance/bsi-c5-2020/idm-04-withdraw-or-adjust-access-rights-as-the-task-area-changes) - [**Criterion PSS-09** — Authorisation Mechanisms](https://support.icompaas.com/compliance/bsi-c5-2020/pss-09-authorisation-mechanisms) - [**Criterion AM-05** — Commitment to Permissible Use, Safe Handling and Return of Assets](https://support.icompaas.com/compliance/bsi-c5-2020/am-05-commitment-to-permissible-use-safe-handling-and-return-of-assets) - [**Criterion HR-01** — Verification of qualification and trustworthiness](https://support.icompaas.com/compliance/bsi-c5-2020/hr-01-verification-of-qualification-and-trustworthiness) ## References - [Bundesamt für Sicherheit in der Informationstechnik (BSI) — BSI C5:2020](https://www.bsi.bund.de/EN/Topics/CloudComputing/Compliance_Criteria_Catalogue/Compliance_Criteria_Catalogue_node.html) - Catalogue identifier: `Criterion OIS-04` Topics: identity accesslogging monitoringprivileged accessidentity managementaccess reviewcloud posture ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.