Google Cloud (GCP)

LiveIdentity & Access

Google Cloud (GCP) connector — read-only, agentless

Audits your Google Cloud (GCP) project security posture — project IAM (service-account keys, primitive-role sprawl, inactive and external principals, public bindings), enabled APIs and API-key restrictions, Cloud Audit Log coverage and retention, VPC firewall exposure (SSH/RDP open to the internet), and public Cloud Storage buckets. Read-only.

Connect Google Cloud (GCP)← Back to all connectors

What we scan

Project IAM policy bindings, service accounts and their key metadata, API keys and their restrictions, and enabled APIs (never resource data or key material)
Audit-log configuration and retention, VPC firewall rules, and Cloud Storage bucket IAM policies (never object contents)

Read-only monitoring — nothing in your Google Cloud (GCP) data changes unless you turn on auto-remediation and grant write access separately.

Security findings

17 detection rules run on every Google Cloud (GCP) scan. Each finding ships with a plain-language explanation, the evidence behind it and remediation steps.

CRITICALPublic exposure
GCP IAM binding grants access to all (public) users
CRITICALPublic exposure
GCP Cloud Storage bucket is public
HIGHStale access
GCP service-account key not rotated in over 90 days
HIGHOver permission
GCP service account has a project-level Owner/Editor role
HIGHExternal access
External user has access to the GCP project
HIGHMisconfig
GCP API key has no application (referrer/IP) restriction
HIGHPublic exposure
GCP firewall allows SSH/RDP from the entire internet
MEDIUMOver permission
GCP user has a project-level Owner/Editor primitive role
MEDIUMMisconfig
GCP organization does not enforce MFA (2-Step Verification)
MEDIUMMisconfig
GCP project has an overly-permissive API enabled
MEDIUMStale access
GCP API key not rotated in over 90 days
MEDIUMMisconfig
GCP Cloud Audit Logs are disabled for a service
MEDIUMMisconfig
Vertex AI is enabled with no vertexai.* org policy
MEDIUMMisconfig
Vendor AI-training data-contribution posture
LOWStale access
GCP service account has been inactive for over 90 days
LOWMisconfig
GCP log retention is shorter than 30 days
LOWMisconfig
GCP project still has the legacy default network

How to connect Google Cloud (GCP)

Step 1
Sign up or log in to 8200.dev
Step 2
Go to Connectors → Google Cloud (GCP)
Step 3
Click Connect and authorize via Google Cloud (GCP)'s consent screen
Step 4
8200.dev scans automatically — results appear within minutes

Connect your first source in minutes — free, read-only, no sales call.

Connect Google Cloud (GCP)See all 23 connectors →