IAM group grants admin access but its name does not say so
- Severity
- Low
- Service
- IAM
- Check ID
- IAM_NAME_DOES_NOT_INDICATE_ADMIN
What this check finds
This IAM Group grants admin privileges, but the name does not indicate it is for admins.
Passing looks like: Admin roles clearly named.
How to fix it
Rename the IAM Group to clearly reflect its admin nature (e.g. 'admin', 'administrators', 'ops-admin'). This prevents accidental membership by non-admin users.
AWS console
IAM → User groups → select group → rename.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More IAM checks
- HighDeprecated or flawed AWS managed policy in use
- HighIAM role allows assumption from anywhere
- HighIAM role with admin privileges can be assumed by unexpected principals
- HighIAM role with s3 listing and get privileges can be assumed by unexpected principals
- HighIAM user access key has not been rotated in over 180 days
- HighIncorrect policy used to attempt to enforce MFA
- HighInline policy allows privilege escalation to admin
- HighPrincipal has an attached policy granting administrative access