Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Amazon Web Services Foundations v7.0.0 · 2.1.5

A delegated administrator account, not the management account, should manage AWS Organizations policies

  • Level 2

This check looks at whether policy management in AWS Organizations, such as service control policies, has been delegated to a dedicated member account. The safe setting is a delegation policy that names that account, so day-to-day policy work does not happen in the management account.

Why it matters

The management account of an AWS organization is special: service control policies do not restrict it, and it can affect every other account. The more people who sign in to it for routine policy edits, the larger the chance of a mistake or a stolen session there.

AWS lets you delegate management of organization policies, for example service control policies, tag policies and backup policies, to a member account through a resource-based delegation policy. Policy authors then work in that account, and the management account can be reserved for the few tasks that only it can do.

Source: Delegate policy management to member accounts (AWS Organizations User Guide).

How to check it yourself

Console: sign in to the management account, open AWS Organizations → Settings and look at the Delegation for AWS Organizations section. It shows the delegation policy, if one exists.

AWS CLI (read-only), run from the management account:

aws organizations describe-resource-policy
aws organizations list-delegated-administrators

The first returns the delegation policy or an error saying none exists. A missing policy means policy management has not been delegated. The second lists member accounts that are delegated administrators for integrated services; it is useful context but is a different thing from the policy delegation itself.

Reference: describe-resource-policy (AWS CLI reference).

How to fix it

Console: in the management account go to AWS Organizations → Settings → Delegation → Create delegation policy. Pick a dedicated, well-protected member account (not a workload account), choose which policy actions it may perform and save.

Script: the command below creates the delegation, so review the JSON with your security team and try it in a test organization first. ConfigCobra never makes this change.

aws organizations put-resource-policy --content file://delegation-policy.json

The JSON follows the example in the AWS guide: a statement whose principal is the delegated account's root ARN (for example arn:aws:iam::111122223333:root) and whose actions are the Organizations policy actions you want to hand over. Grant only the policy types you need.

What changes when you fix it

The delegated account's administrators gain the power to create, edit and attach organization policies. Because a service control policy can block actions across many accounts, treat that account as highly sensitive: strong sign-in controls, few people, and logging.

Management account users can stop doing routine policy edits there. They keep their access, so nothing breaks if they still make a change.

Member accounts and workloads are unaffected by the delegation itself. Effects appear only when the delegated team later changes a policy, so agree on a review process for policy changes at the same time.

Included in

BenchmarkCIS IDProfile
CIS Amazon Web Services Foundations v7.0.02.1.5Level 2

Check this on your AWS

ConfigCobra runs this check with every other control of the CIS Amazon Web Services Benchmarks, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial