Google Compute Engine Organization Security Policy

This page shows how to write Terraform for Compute Engine Organization Security Policy and write them securely.

google_compute_organization_security_policy (Terraform)

The Organization Security Policy in Compute Engine can be configured in Terraform with the resource name google_compute_organization_security_policy. The following sections describe 1 example of how to use the resource and its parameters.

Example Usage from GitHub
resource "google_compute_organization_security_policy" "policy" {
  provider = google

  display_name = "tf-income%{random_suffix}"
  parent       = "organizations/id"

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).


The following arguments are supported:

  • display_name - (Required) A textual name of the security policy.

  • parent - (Required) The parent of this OrganizationSecurityPolicy in the Cloud Resource Hierarchy. Format: organizations/[organization_id] or folders/[folder_id]

  • description - (Optional) A textual description for the organization security policy.

  • type - (Optional) The type indicates the intended use of the security policy. For organization security policies, the only supported type is "FIREWALL". Default value is FIREWALL. Possible values are FIREWALL.

In addition to the arguments listed above, the following computed attributes are exported:

  • id - an identifier for the resource with format locations/global/securityPolicies/[[policy_id]]

  • fingerprint - Fingerprint of this resource. This field is used internally during updates of this resource.

  • policy_id - The unique identifier for the resource. This identifier is defined by the server.

Explanation in Terraform Registry

Organization security policies are used to control incoming/outgoing traffic.

Warning: This resource is in beta, and should be used with the terraform-provider-google-beta provider. See Provider Versions for more details on beta resources. To get more information about OrganizationSecurityPolicy, see:

Tips: Best Practices for The Other Google Compute Engine Resources

In addition to the google_compute_disk, Google Compute Engine has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.



Ensure the encryption key for your GCE disk is stored securely

It is better to store the encryption key for your GCE disk securely. Secret Manager could be used instead.



Ensure your VPC firewall blocks unwanted outbound traffic

It is better to block unwanted outbound traffic not to expose resources in the VPC to unwanted attacks.



Ensure appropriate service account is assigned to your GCE instance

It is better to create a custom service account for the instance and assign it.



Ensure OS login for your GCE instances is enabled at project level

It is better to enable OS login for your GCE instances. Enabling OS login ensures that SSH keys used to connect to instances are mapped with IAM users, allowing centralized and automated SSH key management.



Ensure to use modern TLS protocols

It's better to adopt TLS v1.2+ instead of outdated TLS protocols.



Ensure VPC flow logging is enabled

It is better to enable VPC flow logging. VPC flow logging allows us to audit traffic in your network.

Review your Google Compute Engine settings

In addition to the above, there are other security points you should be aware of making sure that your .tf files are protected in Shisho Cloud.

Frequently asked questions

What is Google Compute Engine Organization Security Policy?

Google Compute Engine Organization Security Policy is a resource for Compute Engine of Google Cloud Platform. Settings can be wrote in Terraform.

Where can I find the example code for the Google Compute Engine Organization Security Policy?

For Terraform, the Aniki-lee/GCP source code example is useful. See the Terraform Example section for further details.