IAM deny policies: what it can block and where it stops
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
IAM deny policies is a Google Cloud mechanism. Deny policies are made up of deny rules that prevent certain principals from using certain permissions, regardless of the roles they are granted. It applies to principals named in the deny rules, on the resource the policy is attached to and its descendants.
All mechanisms ยท Google Cloud guardrails
Deny policies are made up of deny rules that prevent certain principals from using certain permissions, regardless of the roles they are granted. IAM checks relevant deny policies before allow policies, and a deny policy is attached to a project, folder or organization.
Deny policies are made of deny rules that prevent certain principals from using certain permissions, regardless of the roles they hold. IAM checks relevant deny policies before allow policies, and a deny policy is attached to a project, folder or organization.
Limits: each resource can have up to 500 deny policies, the policies on a resource can contain 500 deny rules in total, and wildcards are supported only in supported permission groups. Policy Troubleshooter examines the allow, deny and principal access boundary policies that affect a principal and says whether it can use a permission on a resource. 2 library entries use IAM deny policies.
Documented limits
- Each resource can have up to 500 deny policies. (source)
- The deny policies on a resource can contain a total of 500 deny rules. (source)
- Wildcards are supported only in supported permission groups. (source)
Testing before enforcement
Google documents Policy Troubleshooter, which examines the allow, deny and Principal Access Boundary policies that affect a principal and says whether the principal can use a permission on a resource. (source)
The 2 library entries written in it
- Deny service account key create and delete to a group on one projectGoogle Cloud, IAM deny policies, identity and privilege
- Deny deleting projects tagged prodGoogle Cloud, IAM deny policies, organization integrity
Where Act is behind
Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.
Related pages
Sources
- IAM deny policies, read 10 Nov 2026
- Testing, read 10 Nov 2026
Last reviewed 16 Nov 2026.