IAM policy has linting issues
- Severity
- Low
- Service
- IAM
- Check ID
- IAM_LINTER
What this check finds
The IAM policy linter Parliament found a problem in this policy: an action that does not exist, a resource ARN that does not match its action, a malformed statement, or a pattern that grants more than it appears to. A policy with these errors may not do what its author intended.
Passing looks like: No IAM linting issues.
How to fix it
Review the IAM policy for syntax or logic errors flagged by the linter. Common issues include non-existent actions, incorrect ARN formats, and redundant statements.
AWS console
IAM → Policies → select policy → Edit 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 |
|---|---|
| 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