Unexpected formatting of IAM policy

What this check finds

IAM policies can be written to do things that are unexpected. This catch-all issue identifies anything unexpected in a policy.

Passing looks like: IAM policies well-formed.

How to fix it

Review the flagged policy in the IAM console and simplify it to standard Allow/Deny statements with explicit Action, Resource, and Condition fields.

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

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

All IAM checks