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

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

1.16Ensure IAM policies are attached only to groups or roles

Control family: Identity and Access Management

Control description

By default, IAM users, groups, and roles have no access to AWS resources. IAM policies are the means by which privileges are granted to users, groups, or roles. It is recommended that IAM policies be applied directly to groups and roles but not users.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Permissions given straight to individual IAM users are hard to see and easy to forget when people change jobs. Attaching policies to groups or roles, and putting users into those, keeps access in a few places that can be reviewed. Any policy attached directly to a user, managed or inline, is moved to a group or role.

Before you start

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

  • Define the groups (or Identity Center permission sets) that match each job, so every permission has a home other than a user.
  • Add "no policies attached to users" to the access request and review process.

Evidence

  • The list of job groups with their owners and policies

On AWS the tasks find users with policies of their own, move those permissions into groups, and add the AWS Config rule that flags any user with a direct policy.

Task 1Find users with policies attached directly

  1. Sign in to the AWS Management Console at console.aws.amazon.com and open IAM > Users.
  2. Open each user and choose the Permissions tab.
  3. Under Permissions policies, note every policy whose Attached via column says Directly (inline policies show as directly attached too).
  4. For each such user, decide which group or role their access should come from.

Task 2Move the permissions into a group

  1. In IAM, choose User groups > Create group.
  2. Enter a group name that describes the job, such as billing-readers.
  3. Under Attach permissions policies, select the policies the user had, and under Add users to the group, select the users who need them; choose Create user group.
  4. Open each user's Permissions tab, select the directly attached policies and choose Remove; delete any inline policy.
  5. Check it: the user's Permissions tab lists the policies only as attached through the group.

Task 3Keep it checked with the AWS Config rule iam-user-no-policies-check

  1. 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-user-no-policies-check, 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. Check it: once the rule has finished Evaluating..., every IAM user shows as compliant.

Evidence

  • The iam-user-no-policies-check rule, showing all users compliant, and Security Hub CSPM control IAM.2 showing passed
  • IAM > User groups, with the policies attached to each group

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.