Compliancemanzill.com
CIS Amazon Web Services Foundations Benchmark v1.2.0

CIS Amazon Web Services Foundations Benchmark v1.2.0/Identity and Access Management/22 of 49

1.22Ensure IAM policies that allow full "*:*" administrative privileges are not created

Control family: Identity and Access Management

Control description

IAM policies are the means by which privileges are granted to users, groups, or roles. It is recommended and considered a standard security advice to grant _least privilege_—that is, granting only the permissions required to perform a task. Determine what users need to do and then craft policies for them that let the users perform _only_ those tasks, instead of allowing full administrative privileges.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

A custom policy that allows every action on every resource is administrator access under another name, and it is easy to attach by mistake. Each policy should allow only what its users need. Where full administrator access is truly needed, the AWS-managed AdministratorAccess policy is used on a small, reviewed group instead of homemade copies.

Before you start

The same on every cloud, before the steps in the tabs.

  • Agree who may hold full administrator access, and that it comes only from the AWS-managed AdministratorAccess policy.
  • Review new or changed customer managed policies for wildcards before they are attached.

Evidence

  • The list of administrators and the policy review record

On AWS the tasks find customer managed policies that allow everything, using the AWS Config rule from the benchmark, then narrow them down.

Task 1Find policies that allow every action on every resource

  1. Sign in to the AWS Management Console at console.aws.amazon.com, open AWS Config in the Region where you record global resources such as IAM, and choose Rules > Add rule.
  2. On Specify rule type, search for iam-policy-no-statements-with-admin-access, select it and choose Next.
  3. On Configure rule, keep the name, then choose Next.
  4. On Review and create, check the settings and add the rule.
  5. Once it has finished Evaluating..., open the rule and list the noncompliant policies.

Task 2Replace each one with a narrower policy

  1. In IAM > Policies, open a flagged policy and look at its Entities attached tab to see who uses it.
  2. Use the Last accessed tab of those users and roles to see which services they really use.
  3. Choose Edit, replace the statement allowing all actions on all resources with statements for just those services and resources, and choose Next > Save changes.
  4. Under Policy versions, delete older versions that still allow everything.
  5. Check it: the iam-policy-no-statements-with-admin-access rule shows the policy as compliant, and the users can still do their work.

Evidence

  • The iam-policy-no-statements-with-admin-access rule, showing all customer managed policies compliant
  • Security Hub CSPM control IAM.1, showing passed

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.