{"slug": "how-to-simplify-cloud-access-with-unified-access-policies-now-in-preview", "title": "How to simplify cloud access with Unified Access Policies, now in preview", "summary": "Google Cloud released Unified Access Policies (UAP) in preview at no additional cost, a next-generation access control engine in Cloud IAM that consolidates allow and deny rules into one schema and decouples policy definition from resource enforcement. UAP lets administrators bind a single policy across up to 25 Cloud Resource Manager targets in preview, attach up to five 64 KB policies with up to 100 rules each per resource, and scale to 2,500 unique principals and 500 groups per resource — roughly 5x the effective policy size of the legacy 64 KB single-policy limit. Google Cloud said the change targets the operational bottleneck of managing least privilege across thousands of autonomous agents, microservices and workload identities without duplicating Terraform configurations.", "body_md": "As organizations scale their cloud footprint to thousands of autonomous agents and microservices, you can accidentally create an operational bottleneck with strict Identity and Access Management (IAM). Meanwhile, administrators still need to enforce least privilege across thousands of resources without slowing down engineering velocity.\n\nEnter [Unified Access Policies](https://docs.cloud.google.com/iam/docs/unified-access-policies) (UAPs), Google Cloud's next-generation access control engine in [Cloud IAM](https://cloud.google.com/products/iam), now in preview at no additional cost. UAP consolidates allow and deny rules into one unified schema, and decouples policy definition from resource enforcement. \n\nThis approach allows you to author a policy once and bind it across your organization. UAP governs human, workload, and first-class agent identities with your existing IAM policies. With UAP, you can radically simplify your access policies and manage them more easily at scale.\n\nTraditional access policy models can push teams into a tough trade-off between Zero Trust access and pipeline speed due to three compounding forces:\n\n**Fragmented schemas and permission sprawl**: In granting thousands of granular permissions across cloud resources, administrators are forced to choose between either over-granting permissions from coarse roles with broad access, or wrangling two different syntaxes (APIs and mental models across allow and deny) just to define one workload's custom access posture.\n\n**Policies treated as snowflakes**: Because legacy policies attach directly to individual resources, applying a standard developer or security baseline across 25 projects means duplicating and maintaining 50 separate allow and deny policy configurations in Terraform. This approach can create severe configuration fatigue and operational burden, with greater risk of misconfiguration.\n\n**Scale ceilings and explosion of agent identities**: Modern cloud environments span human teams, federated workloads, service accounts, and autonomous agents that should never share generic service account credentials. As non-human and agent identities multiply, large enterprises routinely hit the hard 64 KB single-policy size limit on allow policies — requiring policy refactoring to onboard new teams or agents.\n\nHelping platform and security teams address these access limitations demands a new approach: an agent-ready engine on a unified control plane, designed to simplify, centralize, and scale access control.\n\nUAP removes cognitive burden for platform and IAM administrators, security architects, and agent administrators while shrinking your Infrastructure as Code footprint. UAP re-architects how policies are authored, bound, and enforced across your resource hierarchy because it’s built around a simpler authorization model.\n\n1. **Unified allow and deny syntax**: Consolidate positive access grants and firm security guardrails into a single, auditable policy instead of reconciling separate allow and deny files.\n\n2. **Multi-binding support**: A standalone policy binding acts as the connective tissue between your policy definition and target Cloud Resource Manager (CRM) nodes (organization, folder, and project). You can now bind a single UAP policy across up to 25 CRM targets in preview, eliminating duplicate Terraform blocks.\n\n3. **Expanded scale limits (5x effective policy size)**: UAP breaks through the legacy single-policy size ceiling by letting you attach up to five UAP policies (64 KB and up to 100 rules each) to any single CRM resource — scaling to 2,500 unique principals and 500 groups per resource.\n\n4. **Clear separation of concerns**: Central security architects can author vetted baseline and guardrail policies at the organization node and delegate self-service binding to folder and project administrators, without letting local teams alter central rule logic.\n\n5. **Expressive permission wildcards and immutable guardrails**: Replace brittle permission lists with prefix, suffix, and substring wildcards alongside predefined roles and action exclusions (excluded permissions).\n\n6. **Built-in readiness for agents**: UAP treats agents as first-class principals (principal://agents.global...) rather than generic service accounts. Agent administrators can scope least-privilege allow and deny rules directly to individual agents or entire agent pools, combine UAP with short-lived, downscoped tokens, and build on an extensible foundation for human-in-the-loop and delegated agent authorization.\n\n7. **Day 1 parity across all four surfaces**: At runtime, Cloud IAM evaluates your existing allow policies, deny policies and UAP policies concurrently across your resource hierarchy. Whether your teams prefer interactive workflows or declarative automation, UAP launches with full create, read, update, and delete parity across the Google Cloud console, gCloud CLI, Terraform, and the Cloud IAM v3 REST API.\n\nYou can deploy your first policy to bring these powerful capabilities into your environment in just a few minutes.\n\nWhile you can automate UAP through Terraform, gCloud CLI or REST API, you can also author and bind policies interactively in the Google Cloud console.\n\n**Step 1: Open the Unified Access Policies tab** In the Google Cloud console, select your target organization, folder, or project in the resource picker and navigate to IAM & Admin > IAM. \n\nAlongside the existing Principals tab, select the new Unified Access Policies tab to view all policies in your scope — including their binding status, governed principals and rule types — and click + Create policy.\n\n**Step 2: Define policy details and access rules** In the Policy Details pane, enter a policy name and description, then build your access posture under Add rules:\n\n**Select principals and exceptions**: Choose a principal set or individual identity (such as dev group or agent identity) via + Add principal, and optionally exempt breakglass administrator groups via + Add exception principal.\n\n**Choose the rule effect and permissions**: Select Allow (using predefined roles, individual permissions or permission wildcards) or Deny (using explicit permissions or wildcards, such as compute.googleapis.com/firewalls.*)\n\n**Combine rules in one policy**: Click Add another rule to pair positive grants and deny guardrails in the same policy, while inspecting the live JSON configuration preview on the right.\n\n**Step 3: Bind the policy and manage lifecycle** Proceed to the Enforcement step, select the target organization, folder, or project scopes where you want the policy to take effect, and click Bind policy. \n\nOnce created, you can click any policy on the Unified Access Policies landing page to open its Policy details view — where you can audit active rules and resource bindings, click View JSON to export the policy for IaC pipelines, or edit bindings as your environment evolves.\n\nWith your first policy securely enforced and managed, your security and platform teams can spend less time wrangling permission sprawl and more time driving business velocity.\n\nWith Unified Access Policies, we are excited to help you build a more secure, agile and future-ready cloud architecture that scales alongside your human and AI workloads.\n\nTo streamline your organization’s access management, explore the Unified Access Policies [documentation](https://docs.cloud.google.com/iam/docs/unified-access-policies), and try it in a test project — create and bind your first reusable UAP policy using gcloud CLI, REST API, or Terraform.", "url": "https://wpnews.pro/news/how-to-simplify-cloud-access-with-unified-access-policies-now-in-preview", "canonical_source": "https://cloud.google.com/blog/products/identity-security/how-to-simplify-cloud-access-with-unified-access-policies/", "published_at": "2026-11-20 17:00:00+00:00", "updated_at": "2026-11-20 18:13:07.795989+00:00", "lang": "en", "topics": ["ai-agents", "ai-policy"], "entities": ["Google Cloud", "Unified Access Policies", "Cloud IAM", "Cloud Resource Manager", "Terraform"], "also_reported_by": [], "takeaway": "UAP replaces separate allow and deny policy files with one schema bound to up to 25 CRM targets, and lifts the legacy 64 KB ceiling to five 64 KB policies of up to 100 rules each per resource, scaling to 2,500 principals and 500 groups.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/how-to-simplify-cloud-access-with-unified-access-policies-now-in-preview", "markdown": "https://wpnews.pro/news/how-to-simplify-cloud-access-with-unified-access-policies-now-in-preview.md", "text": "https://wpnews.pro/news/how-to-simplify-cloud-access-with-unified-access-policies-now-in-preview.txt", "jsonld": "https://wpnews.pro/news/how-to-simplify-cloud-access-with-unified-access-policies-now-in-preview.jsonld"}}