Skip to content
Get started · Google Cloud

Connecting your GCP project

GCP is Coming soon. The planned connection will use workload identity federation and a read-only service account. You will control the trust without downloading a service-account key.

Coming soon — design preview

Microsoft Entra ID, Azure and Microsoft 365 are live today. GCP connections cannot be activated yet. This page describes the planned setup and trust model; it is not an installation guide for use today.

The setup sequence below explains what you will configure when the connection is released. It is intended for architecture planning and security assessment. No setup action is required now.

Federated identity, no downloaded key

The planned collector will read IAM principals and role bindings across the resource hierarchy visible to the connection. It will obtain short-lived access through workload identity federation and impersonate a read-only service account in your project.

The trust will have three parts: a workload identity pool with an OIDC provider, a service account with read permissions, and an impersonation binding for the accepted federated identity. Your team will control each resource.

The provider will validate the external identity. The impersonation binding will authorize that identity to use the service account. The service account’s role grants will set the collection scope.

Why federation, and why it stores nothing

A downloaded service-account key creates a long-lived credential that requires protection and rotation. The planned connection will exchange a short-lived OIDC token instead. No service-account key will be generated, uploaded or stored by Permafrost.

Setup will show the issuer, audience and subject used for the trust configuration. The provider’s conditions will restrict access to the expected Permafrost identity rather than accept every identity issued by the same provider.

You will be able to remove the provider or impersonation binding to prevent new exchanges once Google Cloud applies the change. Already issued tokens will remain subject to their expiry and Google Cloud’s access-control rules.

The exact read roles requested

The planned setup will grant the service account read access at the scope selected for collection. The templates will name the roles so your team can assess them before deployment.

  • Security Reviewer (roles/iam.securityReviewer) will supply visibility into IAM policies and role bindings.
  • Cloud Asset Viewer (roles/cloudasset.viewer) will supply Cloud Asset inventory and attached IAM policy information.

Collection will use configuration and credential metadata rather than downloaded key material. It will not request remediation writes. The roles and resource scope will determine the hierarchy visible to the collector.

Conditional IAM bindings can require request-time context. The planned analysis will preserve uncertainty for conditions it cannot evaluate rather than report unconditional access.

Create it: gcloud or Terraform

Setup will offer a gcloud script and a Terraform equivalent for the pool, OIDC provider, service account, impersonation binding and read-role grants. Your team will be able to inspect the resources and trust conditions before deployment.

You will deploy the configuration through Cloud Shell or your infrastructure pipeline. The output will identify the service account and project to connect. The service-account email will identify the target for impersonation; it will not be a credential.

Verify by use, then connect

The final setup step will take the service-account email and project ID. Verification will exchange the OIDC token, impersonate the service account and perform a cloudresourcemanager.projects.list read.

The check will confirm that the target project is visible before collection activates. A failed exchange, denied impersonation or unsuccessful read will leave the connection inactive.

This will test the complete trust path: provider acceptance, impersonation rights and read permissions. No downloaded key will be required at any stage.