This page provides a list of all available Google-managed organization policy constraints.
Automatically enforced constraints
If an organization policy isn't enforced, it inherits from its lowest ancestor where an organization policy is enforced. If no organization policy is enforced anywhere in the ancestor hierarchy, the Google-managed default behavior of the constraint is enforced.
If the Google-managed default behavior of an organization policy constraint restricts an operation, then that operation is restricted even if you never explicitly defined an organization policy. To allow those operations, you must create organization policies that override the parent policy.
The following organization policy constraints have a Google-managed default behavior that restricts operations:
Available constraints
You can create organization policies using the following constraints.
Managed constraints
| Service | Constraint | Description |
|---|---|---|
| Compute Engine | Allowed VLAN Attachment encryption settings |
This list constraint defines the allowed encryption settings for new VLAN Attachments. constraints/compute.managed.allowedVlanAttachmentEncryption
|
| Compute Engine | Block Compute Engine Preview Features |
This constraint ensures that preview features are blocked unless this constraint is explicitly allowed. Once set to allow, you can control which preview features can individually be enabled or disabled for your project. Only enabled preview features can be accessed in the project. Subsequently disabling the policy does not change the status of individual preview features already set & they can be individually disabled. This constraint only applies to Compute Alpha API features. constraints/compute.managed.blockPreviewFeatures
|
| Compute Engine | Disable VM Nested Virtualization |
[Public Preview] This boolean constraint disables hardware-accelerated nestedvirtualization for all Compute Engine VMs belonging to the organization, project, or folder where this constraint is set to constraints/compute.managed.disableNestedVirtualization
|
| Compute Engine | Restrict enabling VM serial port access metadata |
Preview: This constraint prevents the serial-port-enable metadata key from being set to true for Compute Engine VMs within the organization, project, or folder where this constraint is enforced. By default, serial port access can be enabled on a per-VM, per-zone, or per-project basis using this metadata key. To allow serial port access for specific VMs, you can exempt them from this policy using tags and conditional rules. constraints/compute.managed.disableSerialPortAccess
|
| Compute Engine | Disable VM serial port logging to Stackdriver |
[Public Preview] This constraint, when enforced, disables serial port logging to Stackdriver from Compute Engine VMs. constraints/compute.managed.disableSerialPortLogging
|
| Compute Engine | Restricts usage of Global Internal DNS (gDNS) for projects that have a ZonalOnly DNS setting. |
[Public Preview] This constraint, when enforced, restricts gDNS usage. This restriction disables gDNS VM creation and updating VMs to use gDNS. Reverting a zDNS project to gDNS won't be blocked, but lead to policy violation enforcement during subsequent Instance API invocations. constraints/compute.managed.disallowGlobalDns
|
| Compute Engine | Require OS Config |
[Public Preview] This constraint, when enforced, requires enablement of VM Manager (OS Config) on all new projects. On new and existing projects, this constraint prevents metadata updates that disable VM Manager at the project, project-zonal, or instance level. You can allow specific VM instances to disable VM Manager. First apply tags to mark the instances, and then use conditional rules based on tag values to properly scope those instances out of enforcement. constraints/compute.managed.requireOsConfig
|
| Compute Engine | Require OS Login |
[Public Preview] This constraint, when enforced, requires enablement of OS Login on all newly created Projects. On new and existing projects, this constraint prevents metadata updates that disable OS Login at the project, project-zonal, or instance level. You can allow specific VM instances to disable OS Login. First apply tags to mark the instances, and then use conditional rules based on tag values to properly scope those instances out of enforcement. constraints/compute.managed.requireOsLogin
|
| Compute Engine | Restricts the use of protocol forwarding |
This constraint lets you restrict the types of protocol forwarding deployments (internal or external) that can be created in your organization. To configure the constraint, you specify an allowlist of the type of protocol forwarding deployment to be allowed. The allowlist can only include the following values:
constraints/compute.managed.restrictProtocolForwardingCreationForTypes
|
| Compute Engine | Restrict VM IP forwarding |
[Public Preview] This constraint defines whether Compute Engine VM instances can enable IP forwarding. By default, if no policy is specified, any VM can enable IP forwarding in any virtual network. If enforced, this constraint will deny the creation or update of VM instances with IP forwarding enabled. You can allow specific VM instances to enable IP forwarding. First apply tags to mark the instances, and then use conditional rules based on tag values to properly scope those instances out of enforcement. constraints/compute.managed.vmCanIpForward
|
| Compute Engine | Restrict External IPs For VM instances |
[Public Preview] This constraint defines whether Compute Engine VM instances are allowed to use IPv4 external IP addresses. By default, all VM instances are allowed to use external IP addresses. If enforced, this constraint will deny the creation or update of VM instances with IPv4 external IP addresses. This constraint will not restrict the usage of IPv6 external IP addresses. You can allow specific VM instances to use external IPv4 IP addresses. First apply tags to mark the instances, and then use conditional rules based on tag values to properly scope those instances out of enforcement. constraints/compute.managed.vmExternalIpAccess
|
| Google Kubernetes Engine | Require that the DenyServiceExternalIPs admission controller is enabled |
Require that the DenyServiceExternalIPs admission controller remains enabled in GKE clusters. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/hardening-your-cluster#deny_external_IPs constraints/container.managed.denyServiceExternalIPs
|
| Google Kubernetes Engine | Require that Attribute-Based Access Control is disabled |
Reject requests to enable Attribute-Based Access Control (ABAC) on GKE clusters. ABAC is a legacy authentication method that's disabled by default in all new clusters. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/hardening-your-cluster#leave_abac_disabled constraints/container.managed.disableABAC
|
| Google Kubernetes Engine | Require disabling the insecure kubelet read-only port in GKE clusters |
Require that the insecure kubelet read-only port (10255) remains disabled. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/disable-kubelet-readonly-port constraints/container.managed.disableInsecureKubeletReadOnlyPort
|
| Google Kubernetes Engine | Require that client certificate authentication is disabled |
Don't manually enable the legacy method of client certificate authentication.. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/api-server-authentication#disabling_authentication_with_a_client_certificate constraints/container.managed.disableLegacyClientCertificateIssuance
|
| Google Kubernetes Engine | Requires disabling RBAC bindings to system identities in GKE clusters. |
Disable non-default ClusterRoleBindings and RoleBindings that reference the system:anonymous, system:authenticated, or system:unauthenticated system identities when creating or updating GKE clusters. For details, see https://cloud.google.com/kubernetes-engine/docs/best-practices/rbac#prevent-default-group-usage constraints/container.managed.disableRBACSystemBindings
|
| Google Kubernetes Engine | Disallow using the default Compute Engine service account as the node pool service account. |
Don't use the default Compute Engine service account as the cluster or node pool service account. Use a minimally-privileged IAM service account instead. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/hardening-your-cluster#use_least_privilege_sa constraints/container.managed.disallowDefaultComputeServiceAccount
|
| Google Kubernetes Engine | Require enabling Binary Authorization for GKE clusters. |
Enable Binary Authorization when creating or updating GKE clusters. For details, see https://cloud.google.com/binary-authorization/docs/setting-up. constraints/container.managed.enableBinaryAuthorization
|
| Google Kubernetes Engine | Require that Cloud Logging is enabled in GKE clusters |
Require that all GKE clusters use at least the default Cloud Logging configuration. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/hardening-your-cluster#stackdriver_logging constraints/container.managed.enableCloudLogging
|
| Google Kubernetes Engine | Require using only the DNS-based endpoint to access GKE clusters. |
Enable the DNS-based endpoint for GKE control plane access and disable IP-based endpoints when creating or updating clusters. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/latest/network-isolation#dns-based-endpoint. constraints/container.managed.enableControlPlaneDNSOnlyAccess
|
| Google Kubernetes Engine | Require enabling Google Groups for RBAC in GKE clusters. |
Enable Google Groups for RBAC when creating or updating GKE clusters. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/google-groups-rbac. constraints/container.managed.enableGoogleGroupsRBAC
|
| Google Kubernetes Engine | Require enabling network policy enforcement in GKE clusters. |
Enable the use of Kubernetes NetworkPolicies by enabling network policy enforcement or GKE Dataplane V2. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy or https://cloud.google.com/kubernetes-engine/docs/how-to/dataplane-v2. constraints/container.managed.enableNetworkPolicy
|
| Google Kubernetes Engine | Require enabling private nodes in GKE clusters. |
Enable private nodes when creating or updating GKE clusters and node pools. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/latest/network-isolation#configure-cluster-networking. constraints/container.managed.enablePrivateNodes
|
| Google Kubernetes Engine | Require enabling self-managed secrets Encryption in GKE clusters. |
Enable Secret encryption with self-managed keys when creating or updating GKE clusters. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. constraints/container.managed.enableSecretsEncryption
|
| Google Kubernetes Engine | Require enabling Security Bulletin Notifications in GKE clusters. |
Enable Security Bulletin Notifications when creating or updating GKE clusters. For details, see https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-notifications#securitybulletin constraints/container.managed.enableSecurityBulletinNotifications
|
| Google Kubernetes Engine | Require enabling Shielded Nodes in GKE clusters |
Require that Shielded Nodes remain enabled. Shielded GKE Nodes provide strong, verifiable node identity and integrity to increase the security of GKE nodes. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/shielded-gke-nodes constraints/container.managed.enableShieldedNodes
|
| Google Kubernetes Engine | Require enabling Workload Identity Federation for GKE. |
Enable Workload Identity Federation for GKE when creating or updating clusters. For details, see https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity. constraints/container.managed.enableWorkloadIdentityFederation
|
| Dataflow | Block project SSH keys |
Disable project-wide SSH keys from accessing Dataflow Worker VMs. constraints/dataflow.managed.blockProjectSshKeys
|
| Dataflow | Disable public IPs |
Disable the use of public IPs on Dataflow Worker VMs. constraints/dataflow.managed.disableUsePublicIps
|
| Essential Contacts | Restrict contact domains |
This constraint defines the set of allowed domains that email addresses added to Essential Contacts can have. constraints/essentialcontacts.managed.allowedContactDomains
|
| Multiple Google Cloud services | Restrict enablement of service mcp endpoints. |
When enforced, ensures that only the allow listed services can have their mcp endpoints enabled. By default this constraint is enforced and the list of allowed services is empty, preventing any mcp endpoint enablement. constraints/gcp.managed.mcpAllowedServices
|
| Identity and Access Management | Restrict allowed policy members in IAM allow policies |
This constraint defines the organization principal sets that can be granted IAM roles in your organization. constraints/iam.managed.allowedPolicyMembers
|
| Identity and Access Management | Block service account API key bindings |
When enforced, disables creation of API Keys bound to service accounts. For more information, see Enable key binding to service accounts. constraints/iam.managed.disableServiceAccountApiKeyCreation
|
| Identity and Access Management | Disable service account creation |
This boolean constraint disables the creation of service accounts where this constraint is set to `True`. constraints/iam.managed.disableServiceAccountCreation
|
| Identity and Access Management | Disable service account key creation |
This constraint, when enforced, blocks service account key creation. constraints/iam.managed.disableServiceAccountKeyCreation
|
| Identity and Access Management | Disable service account key upload |
This boolean constraint disables the feature that allows uploading public keys to service accounts where this constraint is set to `True`. constraints/iam.managed.disableServiceAccountKeyUpload
|
| Identity and Access Management | Prevent privileged basic roles for default service accounts |
When this constraint is enforced, it prevents anyone from granting the Editor role ( constraints/iam.managed.preventPrivilegedBasicRolesForDefaultServiceAccounts
|
| Identity and Access Management | Allowed AWS accounts that can be configured for workload identity federation in Cloud IAM |
List of AWS account IDs that can be configured for workload identity federation in Cloud IAM. constraints/iam.managed.workloadIdentityPoolAwsAccounts
|
| Identity and Access Management | Allowed external Identity Providers for workloads in Cloud IAM |
Identity Providers that can be configured for workload authentication within Cloud IAM, specified by URI/URLs. This constraint is managed by Google. constraints/iam.managed.workloadIdentityPoolProviders
|
| Google Cloud Managed Service for Apache Kafka | Disable Kafka Connect Cluster Create And Update |
When this boolean constraint is enforced, creating andupdating Kafka Connect clusters will be disabled. constraints/managedkafka.managed.disableKafkaConnectClusterCreateAndUpdate
|
| Pub/Sub | Disables Subscription Single Message Transforms (SMTs) |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. When this boolean constraint is enforced, Pub/Sub Subscriptions cannot set Single Message Transforms (SMTs). constraints/pubsub.managed.disableSubscriptionMessageTransforms
|
| Pub/Sub | Disables Topic Single Message Transforms (SMTs) |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. When this boolean constraint is enforced, Pub/Sub Topics cannot set Single Message Transforms (SMTs). constraints/pubsub.managed.disableTopicMessageTransforms
|
| Cloud Run | Require IAM invoker check for Cloud Run services |
When enforced, this constraint requires the IAM invoker check to be enabled on Cloud Run services. constraints/run.managed.requireInvokerIam
|
| Spanner | Denied Editions for Cloud Spanner Instance |
The edition you're attempting to use is not allowed by your organization's policy. Please review the policy and select a permitted edition. constraints/spanner.managed.restrictCloudSpannerEditions
|
Legacy managed constraints
| Service | Constraint | Rule type | Description |
|---|---|---|---|
| Vertex AI Workbench | Define access mode for Vertex AI Workbench notebooks and instances | List |
This list constraint defines the modes of access allowed to Vertex AI Workbench notebooks and instances where enforced. The allow or deny list can specify multiple users with the Supported prefix:
|
| Vertex AI Workbench | Disable file downloads on new Vertex AI Workbench instances | Boolean |
This boolean constraint, when enforced, prevents the creation of Vertex AI Workbench instances with the file download option enabled. By default, the file download option can be enabled on any Vertex AI Workbench instance.
|
| Vertex AI Workbench | Disable root access on new Vertex AI Workbench user-managed notebooks and instances | Boolean |
This boolean constraint, when enforced, prevents newly created Vertex AI Workbench user-managed notebooks and instances from enabling root access. By default, Vertex AI Workbench user-managed notebooks and instances can have root access enabled.
|
| Vertex AI Workbench | Disable terminal on new Vertex AI Workbench instances | Boolean |
This boolean constraint, when enforced, prevents the creation of Vertex AI Workbench instances with the terminal enabled. By default, the terminal can be enabled on Vertex AI Workbench instances.
|
| Vertex AI Workbench | Restrict environment options on new Vertex AI Workbench user-managed notebooks | List |
This list constraint defines the VM and container image options a user can select when creating new Vertex AI Workbench user-managed notebooks. The options to be allowed or denied must be listed explicitly. Supported prefix:
|
| Vertex AI Workbench | Require automatic scheduled upgrades on new Vertex AI Workbench user-managed notebooks and instances | Boolean |
This boolean constraint, when enforced, requires that newly created Vertex AI Workbench user-managed notebooks and instances have an automatic upgrade schedule set. The automatic upgrade schedule can be defined by using the
|
| Vertex AI Workbench | Restrict public IP access on new Vertex AI Workbench notebooks and instances | Boolean |
This boolean constraint, when enforced, restricts public IP access to newly created Vertex AI Workbench notebooks and instances. By default, public IPs can access Vertex AI Workbench notebooks and instances.
|
| Vertex AI Workbench | Restrict VPC networks on new Vertex AI Workbench instances | List |
This list constraint defines the VPC networks a user can select when creating new Vertex AI Workbench instances where this constraint is enforced. By default, a Vertex AI Workbench instance can be created with any VPC networks. The allowed or denied list of networks must be identified in the form: Supported prefixes:
|
| Vertex AI | Define access to Google proprietary generative AI models on Vertex AI | List |
This list constraint defines the set of generative AI models and features allowed to be used in Vertex AI APIs. The values of the allowlist should follow the format Supported prefix:
|
| Vertex AI | Define access to models on Vertex AI | List |
This list constraint defines the set of models and features allowed to be used in Vertex AI APIs. The values of the allowlist should follow the format " Supported prefix: For more information, see Control access to Model Garden models.
|
| Vertex AI | Define the managed partner model's advanced features that can be used on Vertex AI | List |
This list constraint defines the set of managed partner model's advanced features allowed to be used in Vertex AI APIs. The values of the allowlist should follow the format " Supported prefix:
|
| Vertex AI | Disable Grounding with Google Search in generative AI APIs | Boolean |
This boolean constraint, when enforced, disables Grounding with Google Search feature in generative AI APIs. By default the feature is enabled.
|
| Vertex AI | Control Grounding Sources in Vertex AI Generative APIs | List |
This list constraint defines the set of grounding sources allowed or denied for use with Vertex AI generative APIs. Supported prefix:
|
| App Engine | Disable Source Code Download | Boolean |
Disables code downloads of source code previously uploaded to App Engine.
|
| App Engine | Runtime Deployment Exemption (App Engine) | List |
This list constraint defines the set of App Engine Standard legacy runtimes (Python 2.7, PHP 5.5 and Java 8) allowed for deployments past End of Support. App Engine Standard legacy runtimes will reach End of Support on Jan 30, 2024. Generally, attempts to deploy applications using legacy runtimes after this date will be blocked. See App Engine Standard runtime support schedule. Setting this constraint to “Allow” unblocks App Engine Standard deployments for the legacy runtime(s) that you specify until the Runtime Deprecation Date. Setting this constraint to “Allow All” unblocks App Engine Standard deployments for all legacy runtime(s) until the Runtime Deprecation Date. Runtimes that have reached End of Support do not receive routine security and maintenance patches. We strongly encourage you to upgrade your applications to use a Generally Available runtime version. Supported prefix:
|
| BigQuery | Disable BigQuery Omni for Cloud AWS | Boolean |
This boolean constraint, when enforced, will disable users from using BigQuery Omni to process data on Amazon Web Services where this constraint is enforced.
|
| BigQuery | Disable BigQuery Omni for Cloud Azure | Boolean |
This boolean constraint, when enforced, will disable users from using BigQuery Omni to process data on Microsoft Azure where this constraint is enforced.
|
| Cloud Build | Allowed Integrations (Cloud Build) | List |
This list constraint defines the allowed Cloud Build integrations for performing Builds through receiving webhooks from services outside Google Cloud. When this constraint is enforced, only webhooks for services whose host matches one of the allowed values will be processed. Supported prefix: For more information, see Gate builds on organization policy.
|
| Cloud Build | Disable Create Default Service Account (Cloud Build) | Boolean |
This boolean constraint, when enforced, prevents the legacy Cloud Build service account from being created.
|
| Cloud Build | Use default service account (Cloud Build) | Boolean |
This boolean constraint, when enforced, allows the legacy Cloud Build service account to be used by default.
|
| Cloud Build | Use Compute Engine Service Account by Default (Cloud Build) | Boolean |
This boolean constraint, when enforced, allows the Compute Engine service account to be used by default.
|
| Cloud Deploy | Disable Cloud Deploy service labels | Boolean |
This boolean constraint, when enforced, prevents Cloud Deploy from adding Cloud Deploy identifier labels to deployed objects.
|
| Cloud Run functions | Allowed ingress settings (Cloud Functions) | List |
This list constraint defines the allowed ingress settings for deployment of a Cloud Function (1st gen). When this constraint is enforced, functions will be required to have ingress settings that match one of the allowed values. Supported prefix: For more information, see Set up organization policies.
|
| Cloud Run functions | Allowed VPC Connector egress settings (Cloud Functions) | List |
This list constraint defines the allowed VPC Connector egress settings for deployment of a Cloud Function (1st gen). When this constraint is enforced, functions will be required to have VPC Connector egress settings that match one of the allowed values. Supported prefix: For more information, see Set up organization policies.
|
| Cloud Run functions | Require VPC Connector (Cloud Functions) | Boolean |
This boolean constraint enforces setting a VPC Connector when deploying a Cloud Function (1st gen). When this constraint is enforced, functions will be required to specify a VPC Connector. For more information, see Set up organization policies.
|
| Cloud Run functions | Allowed Cloud Functions Generations | List |
This list constraint defines the set of allowed Cloud Function Generations that can be used to create new Function resources. Valid values are: Supported prefix:
|
| Cloud Key Management Service | Restrict which KMS CryptoKey types may be created. | List |
This list constraint defines the Cloud KMS key types which may be created under a given hierarchy node. When this constraint is enforced, only KMS key types specified within this org policy may be created within the associated hierarchy node. Configuring this org policy will also impact the protection level of import jobs and key versions. By default, all key types are allowed. Valid values are: Supported prefix:
|
| Cloud Key Management Service | Restrict key destruction to disabled key versions | Boolean |
This boolean constraint, when enforced, only allows the destruction of key versions that are in the disabled state. By default, key versions that are in the enabled state and key versions that are in the disabled state can be destroyed. When this constraint is enforced, it applies to both new and existing key versions.
|
| Cloud Key Management Service | Minimum destroy scheduled duration per key | List |
This list constraint defines the minimum destroy scheduled duration in days that the user can specify when creating a new key. No keys with destroy scheduled duration lower than this value may be created after the constraint is enforced. By default, the minimum destroy scheduled duration for all keys is 1 day, except in the case of import-only keys for which it is 0 days. Supported prefixes:
|
| Cloud Scheduler | Allowed target types for jobs | List |
This list constraint defines the list of target types, such as App Engine HTTP, HTTP, or Pubsub, allowed for Cloud Scheduler jobs. Supported prefix:
|
| Cloud SQL | Restrict Authorized Networks on Cloud SQL instances | Boolean |
This boolean constraint restricts adding Authorized Networks for unproxied database access to Cloud SQL instances where this constraint is enforced. This constraint is not retroactive, Cloud SQL instances with existing Authorized Networks will still work even after this constraint is enforced.
|
| Cloud SQL | Disable diagnostic and administrative access pathways in Cloud SQL to meet compliance requirements. | Boolean |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. When this boolean constraint is enforced, certain aspects of supportability will be impaired and all access paths for diagnostics and other customer support use cases that do not meet advanced sovereignty requirements for Assured Workloads will be disabled.
|
| Cloud SQL | Restrict non-compliant workloads for Cloud SQL instances. | Boolean |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. When this boolean constraint is enforced, certain aspects of supportability will be impaired and provisioned resources will strictly follow advanced sovereignty requirements for Assured Workloads. This policy is retroactive in that it will apply to existing projects, but it will not affect resources that have already been provisioned; ie. modifications to the policy will only be reflected in resources created after the policy is modified.
|
| Cloud SQL | Restrict Public IP access on Cloud SQL instances | Boolean |
This boolean constraint restricts configuring Public IP on Cloud SQL instances where this constraint is enforced. This constraint is not retroactive, Cloud SQL instances with existing Public IP access will still work even after this constraint is enforced.
|
| Google Cloud Marketplace | Disable public marketplace | Boolean |
This boolean constraint, when enforced, turns off Google Cloud Marketplace for all users under the organization. By default, public marketplace access is turned on for the organization. This policy only works when the Private Marketplace is enabled (https://cloud.google.com/marketplace/docs/governance/enable-private-marketplace).
|
| Google Cloud Marketplace | Restrict access on marketplace services | List |
This list constraint defines the set of services allowed for marketplace organizations, and can only include values from the list below:
IAAS_PROCUREMENT is in the allowed value list, the IaaS procurement governance experience is enabled for all products. By default, the IaaS procurement governance experience is turned off. The IAAS_PROCUREMENT policy works independently from the Request Procurement governance capability, which is specifically for SaaS products listed on Cloud Marketplace.Note: The PRIVATE_MARKETPLACE value is no longer supported and using it has no effect. To turn on Google Private Marketplace, you must follow the instructions at https://cloud.google.com/marketplace/docs/governance/enable-private-marketplace. Supported prefix:
|
| Compute Engine | Allowed VLAN Attachment encryption settings | List |
This list constraint defines the allowed encryption settings for new VLAN Attachments. Supported prefix:
|
| Compute Engine | Disable All IPv6 usage | Boolean |
This boolean constraint, when enforced, disables the creation of or update to any Google Compute Engine resources involved in IPv6 usage.
|
| Compute Engine | Disable creation of Cloud Armor security policies | Boolean |
This boolean constraint, when enforced, disables the creation of new global Cloud Armor security policies, and the addition or update of rules to existing global Cloud Armor security policies. This constraint doesn't restrict the removal of rules or the removal, description, or listing of global Cloud Armor security policies. Regional Cloud Armor security policies are unaffected by this constraint. All global and regional security policies that exist prior to the enforcement of this constraint remain in effect.
|
| Compute Engine | Disable Global Load Balancing | Boolean |
This boolean constraint disables creation of global load balancing products. When enforced, only regional load balancing products without global dependencies can be created. By default, creation of global load balancing is allowed.
|
| Compute Engine | Disable Creation of global self-managed SSL Certificates | Boolean |
This boolean constraint, when enforced, disables creation of global self-managed SSL Certificates. Creation of google-managed or regional self-managed certificates is not disabled by this constraint.
|
| Compute Engine | Disable Global Access to VM Serial Ports | Boolean |
This boolean constraint disables global serial port access to Compute Engine VMs belonging to the organization, project, or folder where the constraint is enforced. By default, customers can enable serial port access for Compute Engine VMs on a per-VM or per-project basis using metadata attributes. Enforcing this constraint will disable global serial port access for Compute Engine VMs, regardless of the metadata attributes. Regional serial port access is not affected by this constraint. To disable all serial port access, use the compute.disableSerialPortAccess constraint instead.
|
| Compute Engine | Disable Guest Attributes of Compute Engine metadata | Boolean |
This boolean constraint disables Compute Engine API access to the Guest Attributes of Compute Engine VMs belonging to the organization, project, or folder where this constraint is enforced.
|
| Compute Engine | Disable Hybrid Cloud IPv6 usage | Boolean |
This boolean constraint, when enforced, disables the creation of, or updates to, hybrid cloud resources including Interconnect Attachments and Cloud VPN gateways with a
|
| Compute Engine | Disable Instance Data Access APIs | Boolean |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. This boolean constraint, when enforced, will disable the GetSerialPortOutput and GetScreenshot APIs that access VMs serial port output and capture screenshots from VM UIs.
|
| Compute Engine | Disable Internet Network Endpoint Groups | Boolean |
This boolean constraint restricts whether a user can create Internet Network Endpoint Groups (NEG) with a
|
| Compute Engine | Disable VM nested virtualization | Boolean |
This boolean constraint disables hardware-accelerated nested virtualization for all Compute Engine VMs belonging to the organization, project, or folder where this constraint is set to
|
| Compute Engine | Enforce FIPS-compliant machine types | Boolean |
This boolean constraint when enforced, disables creation of VM instance types that do not comply with FIPS requirements.
|
| Compute Engine | Disable Private Service Connect for Consumers | List |
This list constraint defines the set of Private Service Connect endpoint types for which users cannot create forwarding rules. When this constraint is enforced, users will be blocked from creating forwarding rules for the Private Service Connect endpoint type. This constraint is not retroactively enforced.
GOOGLE_APIS in the allowed/denied list will restrict the creation of Private Service Connect forwarding rules for accessing Google APIs. Using SERVICE_PRODUCERS in the allowed/denied list will restrict the creation of Private Service Connect forwarding rules for accessing services in another VPC network.
Supported prefix:
|
| Compute Engine | Disable VM serial port access | Boolean |
This boolean constraint disables serial port access to Compute Engine VMs belonging to the organization, project, or folder where this constraint is enforced.
|
| Compute Engine | Disable VM serial port logging to Stackdriver | Boolean |
This boolean constraint disables serial port logging to Stackdriver from Compute Engine VMs belonging to the organization, project, or folder where this constraint is being enforced.
|
| Compute Engine | Disable SSH-in-browser | Boolean |
This boolean constraint disables the SSH-in-browser tool in the Cloud Console for VMs that use OS Login and App Engine flexible environment VMs. When enforced, the SSH-in-browser button is disabled. By default, using the SSH-in-browser tool is allowed.
|
| Compute Engine | Disable VPC External IPv6 usage | Boolean |
This boolean constraint, when enforced, disables the creation of or update to subnetworks with a
|
| Compute Engine | Disable VPC Internal IPv6 usage | Boolean |
This boolean constraint, when enforced, disables the creation of or update to subnetworks with a
|
| Compute Engine | Enable settings required for compliance memory protection workloads | Boolean |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. This constraint controls settings required to eliminate potential access paths to VM core memory. When enforced it limits the ability to access VM core memory by disabling access pathways and restricts internal data collection when an error occurs.
|
| Compute Engine | Disable fail-open behavior for list methods that display quota information for a region | Boolean |
This boolean constraint, when enforced, disables the fail-open behavior on server-side failures for
|
| Compute Engine | Require OS Config | Boolean |
This boolean constraint, when enforced, enables VM Manager (OS Config) on all new projects. All VM instances created in new projects will have VM Manager enabled. On new and existing projects, this constraint prevents metadata updates that disable VM Manager at the project or instance level. For more information, see Enable OS Config organization policy.
|
| Compute Engine | Require OS Login | Boolean |
This boolean constraint, when enforced, enables OS Login on all newly created Projects. All VM instances created in new projects will have OS Login enabled. On new and existing projects, this constraint prevents metadata updates that disable OS Login at the project or instance level.
|
| Compute Engine | Shielded VMs | Boolean |
This boolean constraint, when enforced, requires that all new Compute Engine VM instances use Shielded disk images with Secure Boot, vTPM, and Integrity Monitoring options enabled. Secure Boot can be disabled after creation, if desired. Existing running instances will continue to work as usual.
|
| Compute Engine | Require SSL Policy | List |
This list constraint defines the set of target SSL proxies and target HTTPS proxies that are allowed to use the default SSL policy. By default, all target SSL proxies and target HTTPS proxies are allowed to use the default SSL policy. When this constraint is enforced, new target SSL proxies and target HTTPS proxies will be required to specify an SSL policy. Enforcement of this constraint is not retroactive. Existing target proxies that use the default SSL policy are not affected. The allowed/denied list of target SSL proxies and target HTTPS proxies must be identified in the form:
Supported prefixes:
|
| Compute Engine | Require predefined policies for VPC flow logs | List |
This list constraint defines the set of predefined policies that can be enforced for VPC Flow logs.
Supported prefix: For more information, see Configure organization policy constraints for VPC Flow Logs.
|
| Compute Engine | Restrict Cloud NAT usage | List |
This list constraint defines the set of subnetworks that are allowed to use Cloud NAT. By default, all subnetworks are allowed to use Cloud NAT. The allowed/denied list of subnetworks must be identified in the form: Supported prefixes: For more information, see Organization policy constraints.
|
| Compute Engine | Restrict cross-project backend buckets and backend services | List |
This list constraint limits backend bucket and backend service resources that a urlMap resource can attach to. This constraint does not apply to backend buckets and backend services within the same project as the urlMap resource. By default, a urlMap resource in one project can reference compatible backend buckets and backend services from other projects in the same organization as long as the user has compute.backendService.use, compute.regionBackendServices.use or compute.backendBuckets.use permission. We recommend not using this constraint with the compute.restrictSharedVpcBackendServices constraint to avoid conflicts. Projects, folders, and organization resources in allowed or denied lists affect all backend buckets and backend services underneath them in the resource hierarchy. Only projects, folders, and organization resources can be included in the allowed or denied list, and must be specified in the form:
Supported prefixes:
|
| Compute Engine | Restrict Dedicated Interconnect usage | List |
This list constraint defines the set of Compute Engine networks that are allowed to use Dedicated Interconnect. By default, networks are allowed to use any type of Interconnect. The allowed/denied list of networks must be identified in the form: Supported prefixes: For more information, see Restrict Cloud Interconnect usage.
|
| Compute Engine | Restrict Load Balancer Creation Based on Load Balancer Types | List |
This list constraint defines the set of load balancer types which can be created for an organization, folder, or project. Every load balancer type to be allowed or denied must be listed explicitly. By default, creation of all types of load balancers is allowed.
To include all internal or all external load balancer types, use the in: prefix followed by INTERNAL or EXTERNAL. For example, allowing in:INTERNAL will allow all load balancer types from the above list that include INTERNAL. For more information about restricting load balancer types, see https://cloud.google.com/load-balancing/docs/org-policy-constraints. Supported prefixes: For more information, see Organization policy constraints for Cloud Load Balancing.
|
| Compute Engine | Restrict Non-Confidential Computing | List |
The deny list of this list constraint defines the set of services that require all new resources to be created with Confidential Computing enabled. By default, new resources are not required to use Confidential Computing. While this list constraint is enforced, Confidential Computing cannot be disabled throughout the lifecycle of the resource. Existing resources will continue to work as usual. The denied list of services must be identified as the string name of an API, and can only include explicitly denied values from the list below. Explicitly allowing APIs is not currently supported. Explicitly denying APIs not in this list will result in an error. List of supported APIs: [compute.googleapis.com, container.googleapis.com] Supported prefix:
|
| Compute Engine | Restrict Partner Interconnect usage | List |
This list constraint defines the set of Compute Engine networks that are allowed to use Partner Interconnect. By default, networks are allowed to use any type of Interconnect. The allowed/denied list of networks must be identified in the form: Supported prefixes: For more information, see Restrict Cloud Interconnect usage.
|
| Compute Engine | Restrict allowed Private Service Connect Consumers | List |
This list constraint defines the organizations, folders, and projects that can connect to service attachments within a producer's organization or project. The allowed or denied lists must be identified in the following form: Supported prefixes: For more information, see Manage security for Private Service Connect consumers.
|
| Compute Engine | Restrict allowed Private Service Connect Producers | List |
This list constraint defines which service attachments Private Service Connect consumers can connect to. The constraint blocks the deployment of Private Service Connect endpoints or backends based on the organization, folder, or project resource of the service attachment that the endpoints or backends refer to. The allowed or denied lists must be identified in the following form: Supported prefixes: For more information, see Manage security for Private Service Connect consumers.
|
| Compute Engine | Restrict the use of protocol forwarding | List |
This list constraint defines the type of protocol forwarding rule objects with target instance that a user can create. When this constraint is enforced, new forwarding rule objects with target instance are limited to internal and/or external IP addresses, based on the types specified. The types to be allowed or denied must be listed explicitly. By default, creation of both internal and external protocol forwarding rule objects with target instance are allowed.
This constraint is automatically provisioned as part of Google Cloud security baseline. Supported prefix: For more information, see Protocol forwarding overview.
|
| Compute Engine | Restrict Shared VPC Backend Services | List |
This list constraint defines the set of shared VPC Backend Services that eligible resources can use. This constraint does not apply to resources within the same project. By default, eligible resources can use any shared VPC Backend Services. The allowed/denied list of Backend Services must be specified in the form: Supported prefixes:
|
| Compute Engine | Restrict Shared VPC Host Projects | List |
This list constraint defines the set of Shared VPC host projects that projects at or below this resource can attach to. By default, a project can attach to any host project in the same organization, thereby becoming a service project. Projects, folders, and organizations in allowed/denied lists affect all objects underneath them in the resource hierarchy, and must be specified in the form: Supported prefixes:
|
| Compute Engine | Restrict Shared VPC Subnetworks | List |
This list constraint defines the set of shared VPC subnetworks that eligible resources can use. This constraint does not apply to resources within the same project. By default, eligible resources can use any shared VPC subnetwork. The allowed/denied list of subnetworks must be specified in the form: Supported prefixes:
|
| Compute Engine | Restrict VPC peering usage | List |
This list constraint defines the set of VPC networks that are allowed to be peered with the VPC networks belonging to this project, folder, or organization. Each peering end is required to have peering permission. By default, a Network Admin for one network can peer with any other network. The allowed/denied list of networks must be identified in the form: Supported prefixes:
|
| Compute Engine | Restrict VPN Peer IPs | List |
This list constraint defines the set of valid IP addresses that can be configured as VPN peer IPs. By default, any IP can be a VPN peer IP for a VPC network. The allowed/denied list of IP addresses must be specified as valid IP addresses in the form: Supported prefix: For more information, see Restricting Peer IP addresses through a Cloud VPN tunnel.
|
| Compute Engine | Sets the internal DNS setting for new projects to Zonal DNS Only | Boolean |
When enforced, newly created projects will use Zonal DNS as default. By default, this constraint is set to This constraint is automatically provisioned as part of Google Cloud security baseline.
|
| Compute Engine | Shared Reservations Owner Projects | List |
This list constraint defines the set of projects that are allowed to create and own shared reservations in the org. A shared reservation is similar to a local reservation, except that instead of being consumable by only owner projects, they can be consumed by other Compute Engine projects in the resource hierarchy. The list of projects allowed to access the shared reservation must be of the form: Supported prefixes:
|
| Compute Engine | Skip default network creation | Boolean |
This boolean constraint skips the creation of the default network and related resources during Google Cloud Platform Project resource creation where this constraint is enforced. By default, a default network and supporting resources are automatically created when creating a Project resource.
|
| Compute Engine | Compute Storage resource use restrictions (Compute Engine disks, images, and snapshots) | List |
This list constraint defines a set of projects that are allowed to use Compute Engine's storage resources. By default, anyone with appropriate Cloud IAM permissions can access Compute Engine resources. When using this constraint, users must have Cloud IAM permissions, and they must not be restricted by the constraint to access the resource. Supported prefixes:
|
| Compute Engine | Define trusted image projects | List |
This list constraint defines the set of projects that can be used for image storage and disk instantiation for Compute Engine. Supported prefix: For more information, see Set image access constraints.
|
| Compute Engine | Restrict VM IP Forwarding | List |
This list constraint defines the set of VM instances that can enable IP forwarding. By default, any VM can enable IP forwarding in any virtual network. VM instances must be specified in the form: Supported prefixes:
|
| Compute Engine | Define allowed external IPs for VM instances | List |
This list constraint defines the set of Compute Engine VM instances that are allowed to use external IPv4 addresses. This constraint doesn't restrict the use of IPv6 addresses. Supported prefix: For more information, see Restrict external IP access to specific instances.
|
| Compute Engine | Disable Enabling Identity-Aware Proxy (IAP) on global resources | Boolean |
This boolean constraint, when enforced, disables turning on Identity-Aware Proxy on global resources. Enabling IAP on regional resources is not restricted by this constraint.
|
| Google Kubernetes Engine | Disable diagnostic administrative access pathways in GKE. | Boolean |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. When this boolean constraint is enforced, all access paths for diagnostics and other customer support use cases that do not comply with Assured Workloads requirements will be disabled.
|
| Dataform | Restrict git remotes for repositories in Dataform | List |
This list constraint defines a set of remotes that repositories in the Dataform project can communicate with. To block communication with all remotes, set the value to Supported prefix: For more information, see Restrict remote repositories.
|
| Datastream | Datastream - Block Public Connectivity Methods | Boolean |
By default, Datastream connection profiles can be created with public or private connectivity methods. If the boolean constraint for this organization policy is enforced, then only private connectivity methods (for example, VPC peering) can be used to create connection profiles.
|
| Essential Contacts | Domain restricted contacts | List |
This list constraint defines the set of domains that email addresses added to Essential Contacts can have. This constraint is automatically provisioned as part of Google Cloud security baseline. Supported prefix:
|
| Essential Contacts | Disable Project Security Contacts | Boolean |
This boolean constraint, when enforced, allows organization policy administrators to ensure that only contacts assigned at the organization or folder level can receive security notifications. Specifically, enforcing this constraint blocks project owners and contact administrators from creating or updating an Essential Contact with a
|
| Firestore | Require Firestore Service Agent for import/export | Boolean |
This boolean constraint, when enforced, requires Firestore imports and exports to use the Firestore Service Agent.
|
| Cloud Healthcare API | Disable Cloud Logging for Cloud Healthcare API | Boolean |
This boolean constraint, when enforced, disables Cloud Logging for the Cloud Healthcare API. For more information, see Disable Cloud Logging for the Cloud Healthcare API.
|
| Identity and Access Management | Allow extending lifetime of OAuth 2.0 access tokens to up to 12 hours | List |
This list constraint defines the set of service accounts that can be granted OAuth 2.0 access tokens with a lifetime of up to 12 hours. By default, the maximum lifetime for these access tokens is 1 hour. Supported prefix: For more information, see Extend lifetime of OAuth 2.0 access tokens.
|
| Identity and Access Management | Domain restricted sharing | List |
This list constraint defines the organization principal sets and Google Workspace customer IDs whose principals can be added to IAM policies. This constraint is automatically provisioned as part of Google Cloud security baseline. Supported prefix: For more information, see Restricting identities by domain.
|
| Identity and Access Management | Disable Audit Logging exemption | Boolean |
This boolean constraint, when enforced, prevents you from exempting additional principals from audit logging. This constraint does not affect any audit-logging exemptions that existed before you enforced the constraint.
|
| Identity and Access Management | Disable Cross-Project Service Account Usage | Boolean |
When enforced, service accounts can only be deployed (using ServiceAccountUser role) to jobs (vms, functions, etc) running in the same project as the service account. For more information, see Configure for a resource in a different project.
|
| Identity and Access Management | Disable service account creation | Boolean |
This boolean constraint disables the creation of service accounts where this constraint is enforced. For more information, see Disable service account creation.
|
| Identity and Access Management | Disable service account key creation | Boolean |
This boolean constraint, when enforced, disables the creation of service account external keys and Cloud Storage HMAC keys. This constraint is automatically provisioned as part of Google Cloud security baseline. For more information, see Disable service account key creation.
|
| Identity and Access Management | Disable Service Account Key Upload | Boolean |
This boolean constraint disables the feature that allows uploading public keys to service accounts where this constraint is enforced. This constraint is automatically provisioned as part of Google Cloud security baseline. For more information, see Disable service account key upload.
|
| Identity and Access Management | Disable Workload Identity Cluster Creation | Boolean |
This boolean constraint, when enforced, requires that all new GKE clusters have Workload Identity disabled at creation time. Existing GKE clusters with Workload Identity already enabled will continue to work as usual. By default, Workload Identity can be enabled for any GKE cluster. For more information, see Disable workload identity cluster creation.
|
| Identity and Access Management | Service account key expiry duration in hours | List |
This list constraint defines the maximum duration allowed for service account key expiry. By default, created keys never expire.
inheritFromParent=false in the policy file if using the gcloud CLI. This constraint can't be merged with a parent policy. Enforcement of the constraint is not retroactive and will not change pre-existing keys.
Supported prefix:
|
| Identity and Access Management | Service account key exposure response | List |
This list constraint defines the response taken if Google detects that a service account linked key is exposed publicly. Keys that are monitored include long-lived service account keys and API keys that are bound to a service account. If not set, defaults to the behavior described for Supported prefix:
|
| Identity and Access Management | Allowed AWS accounts that can be configured for workload identity federation in Cloud IAM | List |
List of AWS account IDs that can be configured for workload identity federation in Cloud IAM. Supported prefix:
|
| Identity and Access Management | Allowed external Identity Providers for workloads in Cloud IAM | List |
Identity Providers that can be configured for workload authentication within Cloud IAM, specified by URI/URLs. Supported prefix:
|
| Cloud Service Mesh | Allowed VPC Service Controls mode for Anthos Service Mesh Managed Control Planes | List |
This constraint determines what VPC Service Controls modes can be set when provisioning a new Anthos Service Mesh Managed Control Plane. Valid values are "NONE" and "COMPATIBLE". Supported prefix:
|
| VM Manager | VM Manager - Restrict inline script and output file usage | Boolean |
This boolean constraint, when set to 'True', enforces compliance with Assured Workloads requirements by restricting the creation or modification of VM Manager resources that use inline scripts or binary output files. Specifically, the 'script' and 'output_file_path' fields within the OSPolicyAssignment and PolicyOrchestrator resources must remain empty.
|
| Pub/Sub | Enforce in-transit regions for Pub/Sub messages | Boolean |
This boolean constraint, when enforced, sets MessageStoragePolicy::enforce_in_transit to true for all new Pub/Sub topics at creation time. This ensures that Customer Data transits only within the allowed regions specified in the message storage policy for the topic.
|
| Resource Manager | Restrict shared VPC project lien removal | Boolean |
This boolean constraint restricts the set of users that can remove a Shared VPC host project lien without organization-level permission where this constraint is enforced.
|
| Resource Manager | Restrict removal of Cross Project Service Account liens | Boolean |
This boolean constraint, when ENFORCED, prevents users from removing a Cross Project Service Account lien without organization-level permission. By default, any user with the permission to update liens can remove a Cross Project Service Account lien. Enforcing this constraint requires that permission to be granted at the organization level. For more information, see Configure for a resource in a different project.
|
| Resource Manager | Restrict resource query visibility | List |
This list constraint, when enforced on an organization resource, defines the set of Google Cloud resources that are returned in list and search methods for users in the domain of the organization where this constraint is enforced. This can be used to limit what resources are visible in various parts of the Cloud Console, such as the Resource Picker, Search, and Manage Resources page. Note that this Constraint is only ever evaluated at the Organization level. Values specified in allow/deny lists must be in the form: Supported prefixes: For more information, see Restricting project visibility for users.
|
| Resource Manager | Require Enabled Services Allow List for Cross-Organization Move | List |
This list constraint acts as a check to verify that a project with a service enabled is eligible for cross-organization move. A resource with a supported service enabled must have this constraint enforced and that supported service included in the allowed values to be eligible for a cross-organization move. The current list of allowed values for supported services that can be used is:
This constraint provides an additional control on top of constraints/resourcemanager.allowedExportDestinations. This list_constraint is empty by default and will not block cross organization moves unless a supported service is enabled on the resource to be exported. This constraint allows more fine-grained control over resources using features that require more caution when being moved to another organization. By default, a resource with a supported service enabled cannot be moved across organizations. Supported prefix:
|
| Resource Manager | Allowed Destinations for Exporting Resources | List |
This list constraint defines the set of external Organizations to which resources can be moved, and denies all moves to all other Organizations. By default, resources cannot be moved between Organizations. If this constraint is applied to a resource, the resource can be moved only to Organizations that are explicitly allowed by this constraint. Moves within an Organization are not governed by this constraint. The move operation will still require the same IAM permissions as normal resource moves. Values specified in allow/deny lists must be in the form: Supported prefixes:
|
| Resource Manager | Allowed Sources for Importing Resources | List |
This list constraint defines the set of external organizations from which resources can be imported, and denies all moves from all other organizations. By default, resources cannot be moved between organizations. If this constraint is applied to a resource, imported resources directly under this resource must be explicitly allowed by this constraint. Moves within an organization or from outside an organization into an organization aren't governed by this constraint. The move operation will still require the same IAM permissions as normal resource moves. Values specified in allow/deny lists must be in the form: Supported prefixes:
|
| Cloud Run | Allowed Binary Authorization Policies (Cloud Run) | List |
This list constraint defines the set of Binary Authorization policy names that are allowed to be specified on a Cloud Run resource. To allow/disallow a default policy, use the value Supported prefix:
|
| Cloud Run | Allowed ingress settings (Cloud Run) | List |
This list constraint defines the allowed ingress settings for Cloud Run services. When this constraint is enforced, services will be required to have ingress settings that match one of the allowed values. Existing Cloud Run services with ingress settings that violate this constraint can continue to be updated until the service's ingress settings are changed to comply with this constraint. Once a service complies with this constraint the service can only use ingress settings allowed by this constraint. Supported prefix: For more information, see Restrict allowed ingress settings.
|
| Cloud Run | Allowed VPC egress settings (Cloud Run) | List |
This list constraint defines the allowed VPC egress settings to be specified on a Cloud Run resource. When this constraint is enforced, Cloud Run resources are required to be deployed with a Serverless VPC Access connector or with Direct VPC egress enabled, and VPC egress settings are required to match one of the allowed values. Supported prefix: For more information, see Restrict allowed VPC egress settings.
|
| Service Consumer Management | Disable Automatic IAM Grants for Default Service Accounts | Boolean |
This boolean constraint, when enforced, prevents the default App Engine and Compute Engine service accounts that are created in your projects from being automatically granted any IAM role on the project when the accounts are created. This constraint is automatically provisioned as part of Google Cloud security baseline.
|
| Multiple Google Cloud services | Allowed Worker Pools (Cloud Build) | List |
This list constraint defines the set of allowed Cloud Build Worker Pools for performing Builds using Cloud Build. When this constraint is enforced, builds will be required to build in a Worker Pool that matches one of the allowed values.
Supported prefixes:
|
| Multiple Google Cloud services | Google Cloud Platform - Resource Location Restriction | List |
This list constraint defines the set of locations where location-based Google Cloud resources can be created. Important: The information on this page does not describe Google Cloud Platform's data location commitments for Customer Data (as defined in the agreement under which Google has agreed to provide Google Cloud Platform services and as described in the Google Cloud Platform Services Summary at https://cloud.google.com/terms/services) to its customers. For the list of Google Cloud Platform services for which Customer Data location may be selected by customers, see Google Cloud Platform Services with Data Residency at https://cloud.google.com/terms/data-residency. Supported prefixes: For more information, see Restricting Resource Locations.
|
| Multiple Google Cloud services | Restrict which projects may supply KMS CryptoKeys for CMEK | List |
This list constraint defines which projects may be used to supply Customer-Managed Encryption Keys (CMEK) when creating resources. Setting this constraint to
Deny or Deny All is not permitted. Enforcement of this constraint is not retroactive. Existing CMEK Google Cloud resources with KMS CryptoKeys from disallowed projects must be reconfigured or recreated manually to ensure enforcement.
Supported prefixes: For more information, see CMEK organization policies.
|
| Multiple Google Cloud services | Restrict endpoint usage | List |
This list constraint defines the set of Google Cloud API endpoints that can be used to access resources in an organization, folder, or project. This constraint can be used in dry-run mode. Supported prefixes: For more information, see Restricting endpoint usage.
|
| Multiple Google Cloud services | Restrict which services may create resources without CMEK | List |
This list constraint defines which services require Customer-Managed Encryption Keys (CMEK). Setting this constraint to
Deny All is not permitted. Setting this constraint to Allow is not permitted. Enforcement of this constraint is not retroactive. Existing non-CMEK Google Cloud resources must be reconfigured or recreated manually to ensure enforcement.
Supported prefix: For more information, see CMEK organization policies.
|
| Multiple Google Cloud services | Restrict Resource Service Usage | List |
This constraint defines the set of Google Cloud resource services that can be used within an organization, folder, or project, such as compute.googleapis.com and storage.googleapis.com. This constraint can be used in dry-run mode. Supported prefix: For more information, see Restricting resource usage.
|
| Multiple Google Cloud services | Restrict TLS Cipher Suites | List |
This list constraint defines the set of TLS cipher suites that can be used to access resources in an organization, folder, or project where this constraint is enforced. This constraint can be used in dry-run mode. Supported prefixes:
|
| Multiple Google Cloud services | Restrict TLS Versions | List |
This constraint defines the set of TLS versions that cannot be used on the organization, folder, or project where this constraint is enforced, or any of that resource's children in the resource hierarchy. This constraint can be used in dry-run mode. Supported prefix: For more information, see Restrict TLS versions.
|
| Multiple Google Cloud services | Disable Enabling Identity-Aware Proxy (IAP) on regional resources | Boolean |
This boolean constraint, when enforced, disables turning on Identity-Aware Proxy on regional resources. Enabling IAP on global resources is not restricted by this constraint.
|
| Multiple Google Cloud services | Restrict allowed Google Cloud APIs and services | List |
This list constraint restricts the set of services and their APIs that can be enabled on this resource. By default, all services are allowed. Supported prefix:
|
| Spanner | Enable advanced service control for compliance workloads | Boolean |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. When this boolean constraint is enforced, certain aspects of supportability will be impaired and provisioned resources will strictly follow advanced sovereignty requirements for Assured Workloads. This policy will apply to existing projects, but it will not affect resources that have already been provisioned; ie. modifications to the policy will only be reflected in resources created after the policy is modified.
|
| Spanner | Disable Cloud Spanner multi-region if no location selected | Boolean |
Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. This boolean constraint, when enforced, prevents the creation of spanner instances using multi region instance config unless a location is selected. Cloud Spanner today does not yet support selecting location, so all multi regions will be disallowed. In the future, Spanner will provide the functionality for users to select a location for multi regions. Enforcement of this constraint is not retroactive. Spanner instances that have been already created will be unaffected.
|
| Cloud Storage | Google Cloud Platform - Detailed Audit Logging Mode | Boolean |
When Detailed Audit Logging Mode is enforced, both the request and response are included in Cloud Audit Logs. Changes to this feature may take up to 10 minutes to reflect. This Org Policy is highly encouraged in coordination with Bucket Lock when seeking compliance with standards such as SEC Rule 17a-4(f), CFTC Rule 1.31(c)-(d), and FINRA Rule 4511(c). This policy is currently only supported in Cloud Storage. For more information, see Organization policy constraints for Cloud Storage.
|
| Cloud Storage | Enforce Public Access Prevention | Boolean |
Secure your Cloud Storage data from public exposure by enforcing public access prevention. This governance policy prevents existing and future resources from being accessed via the public internet by disabling and blocking ACLs and IAM permissions that grant access to For more information, see Organization policy constraints for Cloud Storage.
|
| Cloud Storage | Cloud Storage - restrict authentication types | List |
The constraint defines the set of authentication types that would be restricted from accessing any storage resources under the organization in Cloud Storage. Supported values are Supported prefixes:
|
| Cloud Storage | Retention policy duration in seconds | List |
This list constraint defines the set of durations for retention policies that can be set on Cloud Storage buckets. Supported prefix: For more information, see Organization policy constraints for Cloud Storage.
|
| Cloud Storage | Restrict unencrypted HTTP access | Boolean |
This boolean constraint, when enforced, explicitly denies HTTP (unencrypted) access to all storage resources. By default, the Cloud Storage XML API allows unencrypted HTTP access. Note that the Cloud Storage JSON API, gRPC, and Cloud console only allow encrypted HTTP access to Cloud Storage resources.
|
| Cloud Storage | Cloud Storage - soft delete policy retention duration in seconds | List |
This constraint defines the allowable retention durations for soft delete policies set on Cloud Storage buckets where this constraint is enforced. Any insert, update, or patch operation on a bucket where this constraint is enforced must have a soft delete policy duration that matches the constraint. When a new organization policy is enforced, the soft delete policy of existing buckets remains unchanged and valid. By default, if no organization policy is specified, a Cloud Storage bucket can have a soft delete policy of any duration. Supported prefix:
|
| Cloud Storage | Enforce uniform bucket-level access | Boolean |
This boolean constraint requires buckets to use uniform bucket-level access where this constraint is set to This constraint is automatically provisioned as part of Google Cloud security baseline. For more information, see Organization policy constraints for Cloud Storage.
|
Learn more
To learn more about the core concepts of organization policy:
Read the overview of organization policy.
Read about what constraints are.
Read how to use constraints to create organization policies.
Read about how hierarchical evaluation works.