IAM policy applies to all resources ("*")
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
An IAM statement with Resource "*" applies to every resource in the account, so even a scoped action can touch far more than intended.
Why it matters
An IAM statement with Resource "*" applies its actions to every resource in the account. Even a seemingly narrow set of actions then reaches far beyond what was intended, for example letting a role read or delete objects in every bucket rather than one. Scoping resources is a core part of least privilege.
How to fix it
Replace "*" with the specific ARNs the workload needs, using variables or references to the resources defined in the same configuration. Some actions genuinely require "*" because they do not operate on a specific resource; for those, keep the wildcard but pair it with tight conditions where possible. Document any action that truly needs account-wide scope.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo