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.14

IAM policies must not grant full administrative access

  • Level 1

This check looks at customer-managed IAM policies that are attached to identities and whether any of them allow every action on every resource. The safe setting is that no such full-administrator policy is attached.

Why it matters

A policy that allows all actions on all resources gives its holder the ability to read data, change networking, create new users and switch off logging anywhere in the account. If that identity is phished or its key leaks, the attacker inherits the same reach. It also makes mistakes costly, because a single wrong command from an administrator can affect every service.

The AWS IAM best practices recommend granting least privilege: start with the permissions that are needed and add more only when required. Policies with a wildcard for both actions and resources are the opposite of that guidance. They also tend to survive long after the project that needed them, because widening access is quick and narrowing it is slow.

Keeping a small, well-known set of administrator roles, rather than many wide policies, makes reviews and incident response much more manageable.

How to check it yourself

Console path: open IAM, then Policies, filter the type to Customer managed, and open each policy that is in use. On the Permissions tab view the JSON and look for a statement with "Effect": "Allow", "Action": "*" and "Resource": "*".

Read-only commands (AWS CLI, run in a test account first):

aws iam list-policies --scope Local --only-attached --query "Policies[].[PolicyName,Arn,DefaultVersionId]" --output text
aws iam get-policy-version --policy-arn <policy-arn> --version-id <default-version-id> --query PolicyVersion.Document

Run the second command for each policy returned. Any attached policy that contains the wildcard action on the wildcard resource fails the check.

How to fix it

Console steps: create a replacement policy that lists only the actions and resources the identity really needs (the policy simulator and the last accessed information on each identity help with this), attach it, then detach the wide policy from the user, group or role and, once nothing uses it, delete it.

Script option (run it yourself with suitable permissions; ConfigCobra itself never changes your AWS account):

aws iam attach-role-policy --role-name <role-name> --policy-arn <narrow-policy-arn>
aws iam detach-role-policy --role-name <role-name> --policy-arn <wide-policy-arn>

Use attach-user-policy and detach-user-policy, or the group equivalents, where the policy is attached to a user or group. Rerun the read-only listing afterwards to confirm that no wide policy is attached.

What changes when you fix it

The people, services and automation that use the affected identity are affected. Anything they did only because of the unlimited permissions, such as creating new resource types, will start to return access denied errors until the narrower policy covers it. Administrators who rely on the wide policy for everyday work need a properly scoped administrator role instead.

To avoid surprises, attach the narrow policy first and leave the wide one in place while you watch for denied requests in your logs, then detach it during a planned window. Keep a break-glass administrator role, protected with strong sign-in controls, so that you are never locked out of your own account.

Included in

BenchmarkCIS IDProfile
CIS Amazon Web Services Foundations v7.0.02.14Level 1

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