QuestionQ72

VerifiedSecuring and governing agentic workflows

You are deploying a data analysis agent with a dedicated agent identity. The agent needs access to a specific Cloud Storage bucket containing financial data in the same project as the agent. You must ensure that the agent identity cannot access any other storage buckets, even if overly permissive project-wide IAM roles are accidentally granted.

What should you do?

Explanation

A principal access boundary policy is a guardrail that limits the set of resources a principal set (including agent identities) is eligible to use, and it is enforced regardless of any allow role bindings. Even if an overly permissive project-wide role is accidentally granted, the agent identity remains blocked from anything outside its boundary, which is exactly the stated requirement. IAM Conditions on the agent's own bindings (A) cannot stop a different, broader allow grant from taking effect. A VPC Service Controls ingress policy (B) controls network and API perimeter access, not per-identity per-bucket authorization. An organization-wide deny on all service accounts (D) would also block the agent's legitimate access to the financial bucket.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!