# Excess permission

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

An excess permission is a permission an identity holds that its work does not require. It may be unused, or used rarely, or granted through a broad role that bundles more than the task needs. Removing it lowers what a stolen credential can do without changing what the owner does.

## An example, sourced

Google Cloud's documentation says each role recommendation suggests that you remove or replace a role that gives your principals excess permissions, and that at scale these recommendations help you enforce the principle of least privilege by ensuring principals have only the permissions they actually need. Google states that the IAM recommender identifies excess permissions using policy insights, which are ML-based findings about a principal's permission usage.

## Why it matters here

Excess permissions are the raw material of every clean-up program. The questions this index asks are who removes them, how the change is tested first, and whether the removal holds after the next deployment. The count is a starting point for the work and not a measure of the risk, which depends on what the permission reaches.

## Related pages

- [Unused permission: meaning and an example](/glossary/unused-permission/)
- [Privilege escalation: meaning and an example](/glossary/privilege-escalation/)
- [Dormant identity: meaning and an example](/glossary/dormant-identity/)
- [All of them](/glossary/)

## Sources

- https://cloud.google.com/policy-intelligence/docs/role-recommendations-overview (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://ciemtools.com/glossary/excess-permission/
