Compare the agent's granted permissions with what it used and remove the rest
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 9 of 30: Compare the agent's granted permissions with what it used and remove the rest. Permissions granted during a pilot tend to stay long after the agent stops using them. Each unused permission is access an attacker could use for nothing the agent needs.
The whole checklist ยท The map
Why it matters
Permissions granted during a pilot tend to stay long after the agent stops using them. Each unused permission is access an attacker could use for nothing the agent needs.
How, in each cloud
- AWS
- Create an IAM Access Analyzer unused access analyzer to find unused access.
- Google Cloud
- Use IAM role recommendations to identify and remove excess permissions.
- Azure
- Run recurring Microsoft Entra access reviews of role assignments.
What the documentation says
- "IAM Access Analyzer unused access analyzers help identify unused access in your" (source)
- "Role recommendations help you identify and remove excess permissions from your" (source)
- "enable organizations to efficiently manage group memberships, access to enterprise applications, and role assignments." (source)
- Previous: Explicitly deny the agent IAM changes and destructive actions
- Next: Grant roles at the narrowest scope that works
Related pages
- Grant roles at the narrowest scope that works: the check, and how in AWS, Google Cloud and Azure
- Keep the encryption keys for agent data under your control and limit who can use them: the check, and how in AWS, Google Cloud and Azure
- Block public access on storage the agent can write to: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html, read 10 Nov 2026
- cloud.google.com/iam/docs/recommender-overview, read 10 Nov 2026
- learn.microsoft.com/en-us/entra/id-governance/access-reviews-overview, read 10 Nov 2026
Last reviewed 16 Nov 2026.