Join our Newsletter — 33% off our NHI Course
Home› Guides› Assured Workloads and Sovereign Controls Guide: Control Packages,…
Guide Cloud Security

Assured Workloads and Sovereign Controls Guide: Control Packages, Access Approval and Violation Monitoring

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 8 November 2026 13 min read
On this page

Google Cloud Assured Workloads turns a folder into a regulated boundary, but the boundary only holds while the organisation policies it sets stay in place, the keys sit where the package expects, and someone actually reviews violations and Google access requests. Assured Workloads applies a control package (a regional data boundary such as the EU Data Boundary, a regulatory boundary such as FedRAMP High, IL5 or ITAR, or Sovereign Controls by Partners) to a folder, and the package's guardrails then govern every project inside it. Access Transparency and Access Approval add visibility and approval over Google personnel access, and Key Access Justifications extend that to key use. This guide covers how identity and access work around an Assured Workloads folder, who should administer it, the service accounts and keys involved, violation and access monitoring, and a hardening baseline. It is for cloud security architects and compliance engineers in regulated organisations. The legal side of residency is in the Data Sovereignty and Residency Guide; this page stays on the Google Cloud controls, from Google's documentation and published API definitions as checked in October 2026.

This is an independent guide from NHI Mgmt Group, based on Google Cloud's public documentation as of November 2026. It is not sponsored or reviewed by Google Cloud. Product features change, so confirm settings against Google Cloud's current documentation.

Key takeaways

  • The compliance regime is fixed at creation. The workload's compliance regime is required and immutable, so choose the package (for example EU_REGIONS_AND_SUPPORT, FEDRAMP_HIGH, IL5, ITAR) before you build. Changing it means a new folder and a migration.
  • Guardrails are organisation policies, and organisation policy administrators can weaken them. Assured Workloads enforces its controls through organisation policy constraints such as gcp.restrictServiceUsage. Anyone with policy administration rights on the folder or above can override them, so violation monitoring is essential.
  • Acknowledging a violation is permanent. The API states that acknowledgement records a business justification for ignoring a violation and cannot be reverted. Treat it as a risk acceptance with sign-off.
  • Access Approval trades support speed for control. Google warns that enabling it may mean product SLAs do not apply to disruption caused by its use, and that requests with no activity for 14 days are treated as dismissed. Enrol services deliberately.
  • Keys are part of the boundary. The ITAR package requires customer-managed encryption keys in a separate key project; other packages support CMEK, Cloud External Key Manager and key import. Key administrators are as privileged as folder administrators.

How identity and access work in Assured Workloads

An Assured Workloads workload is an API resource at organizations/{organization_id}/locations/{location_id}/workloads/{workload_id} that creates and manages a folder (and, for some packages, an encryption keys project). Ordinary Google Cloud IAM governs who can create and change it; the workload then applies organisation policy constraints and service restrictions to everything in the folder. Google personnel access is a separate plane, covered by Assured Support personnel requirements, Access Transparency logs and Access Approval requests.

Control package typeExamples (API values)What it mainly constrains
Regional data boundariesUS_REGIONAL_ACCESS, EU_REGIONS_AND_SUPPORT, CA_REGIONS_AND_SUPPORT, JP_REGIONS_AND_SUPPORT, REGIONAL_CONTROLSWhere resources may be created and where support personnel may be located
Regulatory data boundariesFEDRAMP_MODERATE, FEDRAMP_HIGH, IL2, IL4, IL5, CJIS, ITAR, IRS_1075, CA_PROTECTED_B, HIPAA, HITRUST, HEALTHCARE_AND_LIFE_SCIENCES_CONTROLSAllowed services, locations, key management and personnel requirements for a named regime
Sovereign Controls by PartnersASSURED_WORKLOADS_FOR_PARTNERS with a partner value such as SOVEREIGN_CONTROLS_BY_T_SYSTEMS, LOCAL_CONTROLS_BY_S3NS or SOVEREIGN_CONTROLS_BY_PSNA local partner manages encryption keys, access justification and audits

Google renamed many packages in June 2025 (for example, EU Regions became EU Data Boundary) without changing their function, so console names and API values can differ; the API values above are from the Terraform provider documentation for the workload resource. Package availability changes; check the current list before planning. For how these options compare with other providers, see the EU Sovereign Cloud Options Compared Guide.

Inside the folder, the most important constraint is the service restriction. The RestrictAllowedResources API sets one of two restriction types: ALLOW_COMPLIANT_RESOURCES, which limits the folder to products supported for the regime, or ALLOW_ALL_GCP_RESOURCES, which in Google's words effectively removes the gcp.restrictServiceUsage policy on the folder. Calling it requires assuredworkloads.workload.update plus orgpolicy.policy.set on the folder. Location limits are applied with the resource locations constraint (gcp.resourceLocations); see the Google Cloud Organization Policy Guide.

Admin roles and privileged access

RoleGrantsWho should hold it
roles/assuredworkloads.adminCreate and delete Assured Workloads folders, read-write accessTwo or three named cloud platform administrators, at organisation level
roles/assuredworkloads.editorRead-write access to workloadsPlatform engineers who update labels, settings and violation handling
roles/assuredworkloads.readerGet and list workloads, read-onlyCompliance, audit and SOC
roles/resourcemanager.organizationViewerView all resources in the organisationRequired alongside the Assured Workloads roles for console use
Organisation policy administratorSet and override organisation policiesVery few people; any override inside the folder creates a violation
Cloud KMS administrators on the keys projectManage the CMEK keys the package relies onSeparate from folder administrators, per separation of duties
Access Approval approversApprove, dismiss or invalidate Google access requestsA named on-call group with a documented decision rule
  • Granting the roles is itself privileged: assigning them needs resourcemanager.organizations.setIamPolicy, included in roles/resourcemanager.organizationAdmin. Keep organisation administrators out of daily work; see the Google Cloud IAM and Service Accounts Guide.
  • Billing is part of creation: creating a folder also needs a Cloud Billing access role and an active billing account, and partner packages from SIA, PSN or CNTXT need a partner services billing account with billing.resourceAssociations.create.
  • Separate key and workload control: for ITAR and other CMEK packages, the person who can change folder policy should not also be able to disable or destroy the keys.
  • Restrict inheritance surprises: roles granted at the organisation or a parent folder flow into the Assured Workloads folder. Review grants above the folder, not only on it.

Integrations, API tokens and service accounts

  • Infrastructure as code: workloads are commonly created with Terraform (google_assured_workloads_workload). The pipeline identity needs Assured Workloads admin at the organisation, which makes it one of the most privileged service accounts you own. Run it from a dedicated project, use workload identity federation instead of service account keys, and require approval on plan changes. Several inputs are immutable, including the compliance regime. See the Google Cloud Enterprise Foundations Blueprint Guide.
  • Access Approval service account: Access Approval uses a Google-managed service account (retrievable through the service account method in the API) to access Cloud KMS keys when you choose to sign approvals with your own key via active_key_version. If that account has not been granted permission on the key, the settings show invalid_key_version.
  • Partner service accounts: for Sovereign Controls by Partners, partner_permissions controls whether the partner may view violation alerts (assured_workloads_monitoring), inspectability logs (data_logs_viewer) and Access Approval logs (service_access_approver). Grant only what the partner contract requires.
  • Keys project: resource settings let you create the ENCRYPTION_KEYS_PROJECT and KEYRING with chosen IDs. Workloads in the folder use service agents to reach those keys; review those grants as part of key governance. See the Cloud KMS and Cloud HSM Guide and the BYOK, HYOK and External Key Management Guide.
  • Key Access Justifications: the workload exposes a KAJ enrollment type (FULL_KAJ, EKM_ONLY, KEY_ACCESS_TRANSPARENCY_OFF) and state. Key Access Justifications let you approve or deny key access in Cloud KMS or supported external key managers based on the stated reason.

Logging and detection

Three signal sources matter: Assured Workloads violations, Google personnel access records, and your own Cloud Audit Logs for changes to the folder, policies and keys.

SignalSourceWhat to do with it
Organisation policy and resource violationsAssured Workloads violation monitoring; ListViolations (use workloads/- to read across all workloads)Ticket every unresolved violation; email notifications are on by default (violation_notifications_enabled)
Violation acknowledgedAcknowledgeViolation in audit logs; state moves to exceptionRequire a risk acceptance record; acknowledgement cannot be reverted
Google personnel accessAccess Transparency logsMatch each entry to a support case or published incident
Google access requestsAccess Approval requests (email to up to 50 addresses per level; optional Pub/Sub)Approve only with a case reference; check the requester's home office and physical location
Policy, IAM and key changesCloud Audit Logs Admin Activity for orgpolicy, IAM and Cloud KMSAlert on policy overrides in the folder, key disable or destroy, and new grants above the folder

Access Approval requests carry a justification type that should drive your decision: CUSTOMER_INITIATED_SUPPORT (with a case number), GOOGLE_INITIATED_SERVICE, GOOGLE_INITIATED_REVIEW (security, fraud, abuse or compliance), THIRD_PARTY_DATA_REQUEST (legal process) and GOOGLE_RESPONSE_TO_PRODUCTION_ALERT. Each request also states the principal's home office and physical location as a country or region code. Dismissing a request does not deny access if another request has been approved; invalidating removes a single approval. Route all of these to your SIEM with the patterns in the Google Cloud Audit Logs and Log Sinks Guide.

Metrics that show the boundary holds:

  • Open violations by workload and age, with a target of zero older than 30 days.
  • Acknowledged violations per quarter, each with a signed risk acceptance.
  • Access Approval decisions within the requested expiry, and the share approved with a matching case reference.
  • Folders on the latest control package version, from workload update checks.
  • Privileged grants at organisation and parent folder level that flow into the boundary, reviewed quarterly.

Hardening baseline

  1. Map obligations to a package. Decide which regime applies (residency only, FedRAMP, IL, CJIS, ITAR, IRS 1075, healthcare or partner sovereignty) and confirm the services you need are supported for it before creating anything. See the FedRAMP Guide and the CJIS Security Policy Guide where they apply.
  2. Create the workload as code. Use a dedicated pipeline identity, set provisioned_resources_parent to a known folder, set resource IDs for the keys project and key ring, and set Terraform's deletion_policy to PREVENT so a mistaken destroy cannot delete the boundary.
  3. Keep the service restriction on. Use ALLOW_COMPLIANT_RESOURCES. Never switch to ALLOW_ALL_GCP_RESOURCES for convenience; if a team needs an unsupported product, place it outside the boundary.
  4. Set up keys before data. Create CMEK keys in the keys project with rotation, separate key administrators from workload administrators, and decide on External Key Manager or key import where the regime or your policy needs keys outside Google.
  5. Enable Access Transparency and Access Approval. Enrol services at the organisation where per-service enrolment is possible (folders and projects are all or nothing), set notification emails and a Pub/Sub topic, and optionally sign approvals with your own key. Exclude projects that need rapid support response.
  6. Wire violation handling. Route violation emails to a ticket queue, poll ListViolations into the SIEM, and restrict AcknowledgeViolation to the compliance owner.
  7. Pilot, then migrate. Build a non-production project in the folder, test deployments against the restrictions, then move production. Rolling back means moving projects out of the folder, which removes the guardrails, so treat it as a compliance event, not a routine change.
  8. Review package updates. Check workload updates periodically and apply upgrades so the folder matches the current control package version.
DecisionChoose this whenTrade-off
Regional data boundary onlyYour obligation is residency and support location, not a named regimeFewer restrictions; does not on its own satisfy FedRAMP or IL requirements
Regulatory packageA contract or regulator names FedRAMP, IL, CJIS, ITAR or IRS 1075Smaller set of supported services; stricter key and personnel rules
Sovereign Controls by PartnersPolicy or law expects a local operator to hold keys and run access justificationExtra billing and contracts; partner gets defined visibility
Google-managed keysPackage allows it and risk is lowLeast operational effort; least customer control
CMEK or External Key ManagerPackage requires it (ITAR) or you need to revoke access independentlyKey outages become service outages; more administration

Framework mapping

CapabilityNIST SP 800-53 Rev. 5NIST CSF 2.0ISO/IEC 27001:2022 Annex A
Control packages and organisation policiesCM-2, CM-6, CM-7PR.PS-01, GV.OC-03A.8.9 Configuration management, A.5.31 Legal, statutory, regulatory and contractual requirements
Provider personnel access controlsSA-9, AC-3GV.SC-05A.5.19 Information security in supplier relationships
Keys and CMEKSC-12, SC-28PR.DS-01A.8.24 Use of cryptography
Violation monitoring and access logsCA-7, AU-6DE.CM-09A.8.15 Logging, A.8.16 Monitoring activities

Common misconfigurations

  • Wrong package, discovered late: the compliance regime is immutable, so a folder built on a residency package cannot be upgraded to IL5 in place. Confirm obligations with legal and the contracting authority first.
  • Service restriction switched to allow-all: ALLOW_ALL_GCP_RESOURCES removes the main service guardrail. Alert on any RestrictAllowedResources call.
  • Violations acknowledged to clear the dashboard: acknowledgement is permanent and signals accepted risk to auditors. Fix the cause, or record a formal exception.
  • Approvers who approve everything: Access Approval without a decision rule becomes a rubber stamp. Require a support case reference for CUSTOMER_INITIATED_SUPPORT and escalate legal-process requests.
  • Privileged grants above the folder: organisation-level owners, policy administrators and broad service accounts reach into the boundary. Review inherited IAM, and remove service account keys from pipeline identities; see the Google Cloud Service Account Keys Security Guide.
  • Treating the folder as the whole answer: Assured Workloads controls where resources live and who at Google can reach them; it does not secure your applications, identities or data flows out of the folder.

Practitioner checklist

  • Document which regime applies and confirm required services are supported before creating a workload.
  • Create workloads through a reviewed pipeline with workload identity federation and deletion_policy = PREVENT.
  • Limit roles/assuredworkloads.admin and organisation policy administration to a few named people, and review inherited grants quarterly.
  • Keep ALLOW_COMPLIANT_RESOURCES and alert on any change to the service restriction.
  • Separate key administrators from workload administrators and set CMEK rotation in the keys project.
  • Enable Access Transparency and Access Approval with a written approval rule and a Pub/Sub feed to the SIEM.
  • Route violations to tickets, restrict acknowledgement to the compliance owner and record each as a risk acceptance.
  • Check for control package updates and apply them on a schedule.

Standards and references

Related NHI Mgmt Group resources: Data Sovereignty and Residency Guide · Google Cloud Security Guide · Google Cloud Organization Policy Guide · EU Sovereign Cloud Options Compared Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 8 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.