# Separation of Duties

Separation of Duties divides sensitive responsibilities among independent people, roles, or teams so that no single actor controls an entire high-risk process.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/separation-of-duties

> The idea is to prevent one identity from initiating, approving, executing, and concealing a sensitive action without independent oversight. In cloud environments, separate administrative roles, account boundaries, approval workflows, and protected audit records reduce the risk of fraud, mistakes, and compromised credentials.

Practice exams covering Separation of Duties: [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Separation of Duties

Effective separation combines independent responsibility, enforceable access boundaries, scoped delegation, protected evidence, and regular testing for bypass paths.

1. **Independent ownership of incompatible duties**: Assign conflicting responsibilities, such as requesting and approving a production change, to independent actors. Define the conflicts explicitly rather than assuming that different role names establish separation.
2. **Enforced permission boundaries**: Use identity permissions, role trust policies, account boundaries, and organization guardrails to prevent actors from combining incompatible privileges. Include indirect paths such as modifying policies or assuming deployment roles in access reviews.
3. **Delegated security administration**: Delegate supported centralized security operations to a dedicated member account instead of routinely operating from the organization management account. Configure and verify delegation separately for each security service.
4. **Independent audit custody**: Store audit records under administrators who are independent of the teams whose actions are recorded. Restrict log deletion, retention changes, and changes to encryption keys that could make evidence unavailable.
5. **Controlled approvals and emergency access**: Require independent authorization for high-risk actions where appropriate. Make emergency access time-limited and monitored, with subsequent review by someone other than the person who used it.
6. **Continuous validation**: Review effective permissions and test whether one actor can request, approve, execute, and conceal a sensitive action. Revalidate after changes to group membership, trust relationships, automation, or account ownership.

## Cloud services for Separation of Duties

AWS Organizations establishes account boundaries and service-specific delegated administration, while IAM determines which people and automation can exercise each responsibility. GuardDuty and Security Hub let a dedicated security team centrally operate supported security functions without routinely accessing the management account. CloudTrail provides activity records that can be delivered to an independently administered log archive. KMS controls access to encryption keys, including keys protecting audit data. Together, these services support separation only when permissions, trust relationships, policy-changing authority, and evidence custody are designed to prevent a single actor from bypassing the intended boundaries.

- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: AWS Organizations provides multi-account governance and supports delegated administrator registration for integrated services. Service control policies constrain permissions in member accounts without granting access, while the management account remains outside SCP restrictions.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: GuardDuty supports a delegated administrator that centrally manages threat detection for organization member accounts. This separates detection administration from workload ownership, with regional configuration and membership settings requiring deliberate management.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Security Hub supports delegated administration for centralized security posture and findings management across organization accounts. Security teams can manage supported organization-wide configuration without giving application teams responsibility for their own independent oversight.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records account activity and supports organization trails for centralized audit coverage. Delivering logs to a separately controlled archive helps prevent workload administrators from controlling both operational changes and their audit evidence.

## Separation of Duties exam questions

Real practice exam questions on Separation of Duties, with the correct answer and its explanation.

### Question 1 (AIB-C01 (beta))

**Question:**

A financial services company has an AI council with business, engineering, legal, security, and compliance representatives. Business units operate AI systems, and the council establishes control requirements. The council also selects which of its decisions are audited and can remove findings from assurance reports before those reports reach the board. After an internal review, the board requests independent assurance that AI governance controls are effective without transferring day-to-day control operations to auditors. Which change BEST meets this requirement?

**Correct answer:** Assign assurance to the internal audit function with authority over audit scope and direct reporting to the board audit committee; retain control standards with the AI council and remediation ownership with business units.

**Explanation:** Independent authority over audit scope and reporting prevents the council from filtering scrutiny of its own decisions. The council retains cross-functional governance responsibilities, business units remain responsible for operating and correcting controls, and auditors provide independent assurance.

### Question 2 (SAA-C03)

**Question:**

A company uses a symmetric customer managed AWS KMS key to encrypt application records. Operations engineers must be able to enable and disable the key, view its configuration, and manage automatic key rotation. Only the application's IAM role may encrypt and decrypt records. Operations engineers must not be able to decrypt records or give themselves permission to do so, even temporarily.

A separate governance team controls IAM policies and role trust policies. Operations engineers cannot modify those policies or assume the application role. No other permissions or KMS grants provide access to the key.

Which key policy configuration meets these requirements?

**Correct answer:** Allow the operations role only kms:DescribeKey, kms:EnableKey, kms:DisableKey, kms:GetKeyRotationStatus, kms:EnableKeyRotation, and kms:DisableKeyRotation. Allow the application role only kms:Encrypt, kms:Decrypt, and kms:GenerateDataKey. Reserve key policy changes and grant management for the governance team.

**Explanation:** This separates key lifecycle operations from cryptographic use and permission administration. Operations engineers can perform their required tasks but cannot decrypt data, modify the key policy, or create grants to obtain decryption access. The governance team's control of IAM and role trust policies also prevents escalation through those paths.

### Question 3 (SAP-C03)

**Question:**

A company uses AWS Organizations with all features enabled and SCPs enabled. A central governance team maintains a set of approved SCPs. These policies are used only in a Sandbox OU, which has no nested OUs. The governance team retains exclusive control over policy contents and the list of approved policies.

Platform engineers work from a dedicated member account. They must be able to attach and detach the approved SCPs on the Sandbox OU without requesting each change from the governance team. They must not be able to update policy documents, manage attachments on other targets, or change the organization structure. Company policy prohibits the engineers from signing in to or assuming roles in the management account.

Which solution meets these requirements with the LEAST custom automation?

**Correct answer:** In the management account, configure an AWS Organizations resource-based delegation policy that permits the platform engineers' role to perform organizations:AttachPolicy and organizations:DetachPolicy only for the approved SCP ARNs and the Sandbox OU ARN. Give the role corresponding identity-based permissions in the member account.

**Explanation:** AWS Organizations supports resource-based delegation policies that delegate supported policy-management operations to principals in member accounts. Combining narrowly scoped delegation with corresponding identity-based permissions allows the engineers to manage only the specified policy attachments. It does not require management-account role assumption or grant policy-document or organization-structure administration.

### Question 4 (AIP-C01)

**Question:**

A company runs foundation model applications in production member accounts managed through AWS Organizations. Application engineers propose changes to the business tools that each application can invoke. An independent AI risk team must approve every production tool-permission change before it takes effect.

An audit finds that engineers use different IAM roles to submit and approve changes, but can assume both roles. Engineers can also modify the deployment workflow and pass its execution role to other automation. Approval events are logged, but engineers administer the log destination.

The company needs an organization-wide control that prevents an engineer with compromised credentials from authorizing their own change, bypassing the approved deployment path, or removing the associated evidence. A separate central security team administers organizational controls and does not develop these applications.

Which design meets these requirements?

**Correct answer:** Use centrally controlled, non-overlapping engineer and risk-reviewer identities. Bind each approval to the exact proposed change and allow only a protected workflow execution role to apply it. Use SCPs and centrally administered IAM permissions and trust policies to block engineers from direct updates, assuming or passing privileged roles, and modifying the workflow or its controls. Store evidence under independent custody.

**Explanation:** This design separates proposing, approving, executing, and retaining evidence through effective access controls. Binding approval to the exact change prevents substitution after review. Protected workflow and role configuration prevent bypass, while independent log custody prevents engineers from removing evidence. SCPs establish permission boundaries; IAM policies and trust policies provide the necessary authorized access.

### Question 5 (SCS-C03)

**Question:**

A company uses AWS Organizations with all features enabled. Its production accounts belong to a Production OU and run Application Load Balancers in two AWS Regions. AWS Config records the required resource types in all relevant accounts and Regions. New production accounts and load balancers are created frequently.

The security team must centrally enforce a baseline of AWS WAF managed rules on all existing and future production load balancers. The governance team must retain exclusive access to the Organizations management account, and the security team must perform routine policy administration from a dedicated security member account. The solution must automatically correct missing baseline protections with the least operational overhead.

Which solution meets these requirements?

**Correct answer:** Have the governance team designate the security account as an AWS Firewall Manager administrator. From that account, create an AWS WAF policy in each required Region, scope the policies to the Production OU and Application Load Balancers, and enable automatic remediation.

**Explanation:** Firewall Manager supports centralized AWS WAF policy administration from a designated member account. OU-based scope includes applicable resources in existing accounts and accounts subsequently added to the OU. Regional policies with automatic remediation apply the required protections to existing and newly created in-scope load balancers without routine management-account access.

### Question 6 (DOP-C02)

**Question:**

A company uses AWS Organizations with all features enabled. Production workloads run in the management account and several member accounts. Application administrators have AdministratorAccess in the accounts that host their workloads.

The security team must centrally prohibit ec2:TerminateInstances for all IAM users, IAM roles, and root users in every account that hosts production workloads. Service-linked roles are explicitly excluded from this requirement. Application administrators must not be able to remove the restriction, and routine application administration must not require management-account access. The company permits workload migration and wants to avoid maintaining account-specific permission restrictions.

Which solution meets these requirements?

**Correct answer:** Migrate production workloads from the management account into member accounts in a Production OU. Place the existing production member accounts in that OU. Attach an SCP denying ec2:TerminateInstances to the OU, reserve organization policy administration for the governance team, and limit application administrators to their workload accounts.

**Explanation:** The explicit SCP deny restricts IAM users, IAM roles other than service-linked roles, and root users in the Production OU's member accounts. AdministratorAccess cannot override the deny. Moving production workloads out of the management account avoids its SCP exemption, and OU inheritance provides centralized enforcement without account-specific restrictions.

## Practice Separation of Duties in a full exam

Questions on Separation of Duties in each practice exam, with every answer option and an explanation for each:

- [AIB-C01 (beta)](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 6 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 6 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 6 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 4 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 3 questions

## What is Separation of Duties

Separation of Duties is a security and governance principle that distributes incompatible responsibilities across independent actors. The objective is not merely to create different job titles or accounts, but to prevent one actor from controlling every stage of a sensitive operation. For example, a developer may propose a production change, a separate reviewer may approve it, and an automated deployment role may execute it. The developer should not also be able to bypass approval or erase evidence of the deployment.

Cloud implementations combine organizational ownership with technical enforcement. Identity policies define which actions each role can perform, trust policies control who can assume those roles, and account boundaries separate workloads from security administration and audit storage. Engineers must evaluate effective access across all these layers. Two nominally separate roles do not provide meaningful separation if the same person can freely assume both, change their permissions, or impersonate the approval identity.

A common multi-account design separates organization governance, centralized security operations, workload administration, and log custody. The organization management account handles restricted governance tasks, while a dedicated security member account operates supported security services across workload accounts. A separate log archive account protects audit records from workload administrators. These account boundaries support separation, but their effectiveness depends on access policies and ownership arrangements.

In AWS, delegated administration allows a designated member account to perform supported organization-wide service administration without routinely using the AWS Organizations management account. For example, security personnel can administer Amazon GuardDuty or AWS Security Hub capabilities through a security account while application teams manage workloads in their own accounts. Delegation is service-specific: registering an account for one service does not make it the administrator of every security service. Configuration scope, regional behavior, member enrollment, and automatic enablement must be checked for each service.

Service control policies can reinforce this arrangement by limiting actions available in member accounts, such as attempts to disable required protections. They do not grant permissions, and they do not restrict principals in the organization's management account. Consequently, minimizing management-account access remains essential. Likewise, a delegated administrator has only the authority provided through the relevant service integration and applicable permissions, not unrestricted organization ownership.

Separation of Duties complements least privilege but is not identical to it. Least privilege limits each actor's permissions; separation addresses dangerous combinations of permissions and responsibilities. An identity with narrowly scoped approval and execution permissions may still violate separation if it can approve its own action. Some workflows therefore require independent approval or prevent the requester from serving as the approver.

The main trade-offs are additional coordination, account and role administration, and potentially slower emergency response. Automate routine policy deployment and access reviews, and define monitored, time-limited emergency access with independent post-event review. Test that administrators cannot bypass boundaries through role assumption, policy changes, deployment pipelines, or log deletion. Separation reduces single-actor risk, but does not eliminate collusion; protected audit evidence and independent review remain necessary.

## Learn Separation of Duties in lessons

8 short lessons on Separation of Duties in 6 certification courses.

- AIB-C01 (beta): Separation of Duties: independent governance roles (Premium), https://app.blowstack.com/lessons/separation-of-duties-independent-governance-roles-aib-c01
- SAA-C03: Least privilege and separation of duties (Premium), https://app.blowstack.com/lessons/least-privilege-and-separation-of-duties-saa-c03
- SAP-C03: Key Custody vs Separation of Duties (Premium), https://app.blowstack.com/lessons/key-custody-vs-separation-of-duties-sap-c03
- AIP-C01: Separation of Duties: independent approval in AI governance (Premium), https://app.blowstack.com/lessons/separation-of-duties-independent-approval-in-ai-governance-aip-c01
- SCS-C03: Separation of Duties: delegated security administration boundaries (Premium), https://app.blowstack.com/lessons/separation-of-duties-delegated-security-administration-boundaries-scs-c03
- DOP-C02: Separation of Duties: independent authority in deployment pipelines (Premium), https://app.blowstack.com/lessons/separation-of-duties-independent-authority-in-deployment-pipelines-dop-c02
