IAM role allows assumption from anywhere
- Severity
- High
- Service
- IAM
- Check ID
- IAM_ROLE_ALLOWS_ASSUMPTION_FROM_ANYWHERE
What this check finds
The IAM role's trust policy allows any other account to assume it.
Passing looks like: IAM roles not assumable from anywhere.
How to fix it
Update the trust policy to restrict the Principal to specific trusted AWS account IDs, services, or ARNs. Add a Condition with sts:ExternalId for cross-account roles.
AWS console
IAM → Roles → select role → Trust relationships → Edit trust policy.
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 |
|---|---|
| PCI-DSS v4.0.1 |
|
| HIPAA Security Rule |
|
| 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 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
- MediumExpired SSL/TLS certificate stored in IAM