# Principal access boundary (PAB) policies: what it can block and where it stops

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

Principal access boundary (PAB) policies is a Google Cloud mechanism. A principal access boundary policy defines the resources a set of principals is eligible to access. It applies to principal sets bound to the policy through a policy binding; blocks only permissions in the policy enforcement version.

A principal access boundary policy defines the resources a set of principals is eligible to access. If a principal is ineligible to access a resource, access is limited regardless of the roles granted; the policy can only block access, not grant it.

A principal access boundary policy defines the resources a set of principals is eligible to access. If a principal is ineligible for a resource, access is limited regardless of the roles granted. The policy can only block access, never grant it, and applies to principal sets bound through a policy binding.

Limits: a policy can have up to 500 rules, an organization up to 1,000 policies, and permissions outside the policy enforcement version are not blocked. Cached publicly visible resources can still be viewed. Google lists Policy Simulator for these policies in its documentation, and Policy Troubleshooter examines them. 1 library entry uses a principal access boundary.

## Documented limits

- A policy can have up to 500 rules. ([source](https://cloud.google.com/iam/docs/principal-access-boundary-policies))
- An organization can have up to 1000 policies. ([source](https://cloud.google.com/iam/docs/principal-access-boundary-policies))
- Permissions outside the enforcement version are not blocked. ([source](https://cloud.google.com/iam/docs/principal-access-boundary-policies))
- Cached publicly visible resources can still be viewed. ([source](https://cloud.google.com/iam/docs/principal-access-boundary-policies))

## Testing before enforcement

Google lists Policy Simulator for Principal Access Boundary policies in its documentation navigation, and Policy Troubleshooter examines PAB policies. ([source](https://cloud.google.com/policy-intelligence/docs/test-organization-policies))

## The 1 library entry written in it

- [Principal access boundary limiting the resources principals can access](/guardrails/gcp-pab-eligible-resources/): Google Cloud, Principal access boundary (PAB) policies, data exfiltration

**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

- [Service control policies (SCPs): how it works, its limits and how to test it](/mechanisms/scp/)
- [Resource control policies (RCPs): how it works, its limits and how to test it](/mechanisms/rcp/)
- [IAM permissions boundaries: how it works, its limits and how to test it](/mechanisms/permissions-boundary/)

## Sources

- Principal access boundary (PAB) policies: https://cloud.google.com/iam/docs/principal-access-boundary-policies (read 10 Nov 2026)
- Testing: https://cloud.google.com/policy-intelligence/docs/test-organization-policies (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/mechanisms/principal-access-boundary/
