IAM Policies Attached Directly to Users
IAM users have policies attached directly rather than receiving permissions through groups or roles, which makes permissions harder to review and keep consistent.
| Severity | Informational |
| CVSS 3.1 | 0 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N Open in the calculator |
| CVSS 4.0 | 0 CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-269: Improper Privilege Management |
| OWASP Top 10 | A06:2025 Insecure Design |
| Category | Security Misconfiguration |
Description
Permissions are granted to individual IAM users by attaching managed policies to them or embedding inline policies in them, rather than through IAM groups or through roles assumed by federated identities. Each user's permissions then have to be reviewed one by one, and people with the same job often end up with different access as one-off changes accumulate.
The finding concerns how permissions are managed rather than what they allow: a policy attached directly to a user is no more permissive than the same policy attached to a group, so there is no direct impact. Its practical effect is that permissions spread across individual users are harder to audit, so excessive or outdated permissions are more likely to go unnoticed during access reviews and when people change role or leave: users are more likely to keep access they no longer need, and the access reviews that would catch an over-privileged account are slower and less reliable. This increases the effect of any later compromise of an affected user's credentials.
The issue is identified with aws iam list-attached-user-policies and aws iam list-user-policies for each user, or from aws iam get-account-authorization-details. It is a check in the CIS AWS Foundations Benchmark, Security Hub and Prowler, which report every user with a directly attached or inline policy.
Remediation
Manage permissions through groups and roles:
- Create IAM groups for each job function, attach the required managed policies to the groups and add users to the right groups, then detach the policies from the users and delete their inline policies.
- Prefer customer managed policies to inline policies, so that each policy is defined once, versioned and reused.
- For the longer term, move people to
IAM Identity Centeror another identity provider with permission sets or roles, which removes the need for individual IAM users. - Include IAM in periodic access reviews, using
IAM Access Analyzerunused access findings to remove permissions that are not used.
Confirm the fix by checking that aws iam list-attached-user-policies and aws iam list-user-policies return no policies for any user.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.