Inside the GCP connector (Beta): projects, IAM, and what we read

Compute Engine, Cloud SQL, Cloud Storage, IAM, BigQuery, Secret Manager — what we read from a GCP project, and an honest note on how far it has been tested.

The GCP connector is in Beta. Its scanners are verified against emulated GCP APIs; they have not yet been validated on a live customer account.

Today the connector authenticates with a service-account key: you create a service account in your project, grant it read-only roles, and upload a JSON key, which we store encrypted at rest. Workload Identity Federation — no key at all — is where we want to get to, and is not built yet. You can delete the key in your project at any time.

1. Compute

2. Data

3. Identity

4. Security Command Center and Service Health

If SCC is enabled and you grant access, we pull its active findings. This one is opt-in. Personalized Service Health: active Google Cloud incidents that touch the project.

5. Cost

Google has no per-project spend API, so spend comes from your own Cloud Billing export to BigQuery. If you have set one up and given the service account read access to it, a nightly check flags a day well above the week before it and budgets reaching 75, 90 and 100%. It is off unless it is switched on for your account, because the query is billed to your project.

What the GCP connector does NOT do

Service Health incidents are read every 5 minutes on a paid plan (every 15 during a trial). Security Command Center findings are not read yet: that scanner is written but switched off until it has been verified against an SCC Premium project. Exposure scans — buckets open to allUsers, Cloud SQL public IPs, unauthenticated Cloud Run services, public Pub/Sub topics — run every hour. IAM, Secret Manager and logging posture run once a night. An account administrator can ask for a fresh scan of a connection, at most once every 15 minutes per account; it runs with the next hourly scan, and while CloudMonitor is pre-launch nothing scans during the part of each day the service is powered down (see the Terms). Setup steps are on the Connectors page.

← Back to all posts