Setup GuideGCPGoogle CloudIntegrationIAMSetup

How to Connect Google Cloud Platform to SecureSpect

Set up the GCP integration in SecureSpect using Workload Identity Federation — no long-lived service account keys required.

SecureSpect Team··7 min read

Ready to connect? Follow the steps in SecureSpect — the integration dialog walks you through the same process described here.

Open Integrations →

Overview

SecureSpect connects to GCP using a Workload Identity Federation configuration — the modern, keyless approach recommended by Google. This eliminates the need to create, rotate, and store service account JSON keys, reducing your credential attack surface while maintaining continuous compliance monitoring.

What Gets Monitored

  • IAM policies — Overly permissive roles, primitive roles (Owner/Editor) usage, external identity bindings
  • Security Command Center — Active findings, critical vulnerability counts
  • Cloud Logging — Audit log sink configuration, log retention
  • Cloud KMS — Encryption key rotation status
  • VPC Service Controls — Perimeter configurations
  • Storage buckets — Public access prevention, versioning status
  • Cloud SQL — Authorized networks, SSL requirements

Step 1 — Set Up Workload Identity Federation

Create a Workload Identity Pool and Provider to allow SecureSpect to authenticate without service account keys.

# Create the identity pool

gcloud iam workload-identity-pools create securespect-pool \

--project=YOUR_PROJECT_ID \

--location=global \

--description="SecureSpect integration pool"

# Create a provider (OIDC)

gcloud iam workload-identity-pools providers create-oidc securespect-provider \

--project=YOUR_PROJECT_ID \

--location=global \

--workload-identity-pool=securespect-pool \

--issuer-uri=https://accounts.securespect.io \

--allowed-audiences=securespect-gcp

Step 2 — Create a Read-Only Service Account

# Create the service account

gcloud iam service-accounts create securespect-reader \

--project=YOUR_PROJECT_ID \

--description="SecureSpect read-only access"

# Bind the Workload Identity to the service account

gcloud iam service-accounts add-iam-policy-binding \

securespect-reader@YOUR_PROJECT_ID.iam.gserviceaccount.com \

--project=YOUR_PROJECT_ID \

--role=roles/iam.workloadIdentityUser \

--member="principalSet://iam.googleapis.com/projects/YOUR_PROJECT_NUMBER/locations/global/workloadIdentityPools/securespect-pool/*"

# Grant read-only roles

gcloud projects add-iam-policy-binding YOUR_PROJECT_ID \

--member="serviceAccount:securespect-reader@YOUR_PROJECT_ID.iam.gserviceaccount.com" \

--role=roles/viewer

gcloud projects add-iam-policy-binding YOUR_PROJECT_ID \

--member="serviceAccount:securespect-reader@YOUR_PROJECT_ID.iam.gserviceaccount.com" \

--role=roles/securitycenter.findingsViewer

Step 3 — Connect in SecureSpect

  • Go to Integrations → GCP → Connect.
  • Enter your Project ID and Project Number.
  • Enter the Workload Identity Pool and Provider names you created.
  • Click Verify & Save.
  • SecureSpect will test the connection and run the first scan within 10 minutes.

    Organization-Level Scanning

    For multi-project GCP organizations, grant the service account access at the Organization level instead of per-project:

    gcloud organizations add-iam-policy-binding YOUR_ORG_ID \
    

    --member="serviceAccount:securespect-reader@YOUR_PROJECT_ID.iam.gserviceaccount.com" \

    --role=roles/viewer

    This allows SecureSpect to scan all projects in your organization with a single connection.

    Automate your SOC 2 evidence collection

    Connect your AWS and GitHub environments and start collecting audit-ready evidence today. Free to start.

    Start Free →More Articles