Google Security Command Center (SCC) Source

This page shows how to write Terraform for Security Command Center (SCC) Source and write them securely.

google_scc_source (Terraform)

The Source in Security Command Center (SCC) can be configured in Terraform with the resource name google_scc_source. The following sections describe 1 example of how to use the resource and its parameters.

Example Usage from GitHub
resource "google_scc_source" "this" {
  description  = var.description
  display_name = var.display_name
  organization = var.organization

  dynamic "timeouts" {

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 description of the source (max of 1024 characters).

The source’s display name. A source’s display name must be unique amongst its siblings, for example, two sources with the same parent can't share the same display name. The display name must start and end with a letter or digit, may contain letters, digits, spaces, hyphens, and underscores, and can be no longer than 32 characters.

  • id optional computed - string
  • name optional computed - string

The resource name of this source, in the format 'organizations/[[organization]]/sources/[[source]]'.

The organization whose Cloud Security Command Center the Source lives in.

Explanation in Terraform Registry

A Cloud Security Command Center's (Cloud SCC) finding source. A finding source is an entity or a mechanism that can produce a finding. A source is like a container of findings that come from the same scanner, logger, monitor, etc. To get more information about Source, see:

Frequently asked questions

What is Google Security Command Center (SCC) Source?

Google Security Command Center (SCC) Source is a resource for Security Command Center (SCC) of Google Cloud Platform. Settings can be wrote in Terraform.

Where can I find the example code for the Google Security Command Center (SCC) Source?

For Terraform, the niveklabs/google source code example is useful. See the Terraform Example section for further details.


Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.