Skip to main content
Connect your Google Cloud Platform (GCP) project so Myrmex can read your resource configuration, audit your cloud security posture, and help you fix misconfigurations. Myrmex reaches the Google Cloud APIs through a Collector using a least-privilege service account — everything is read in real time, on demand, and nothing from your project is stored on the Myrmex side.

What Myrmex Can Do

Read & inventory

Enumerate projects and resources — Compute Engine, Cloud Storage, IAM, VPC, and more — for read-only analysis.

Cloud posture audit

Run a Security Posture audit against your project using CIS, ISO 27001, and NIST controls.

Find misconfigurations

Surface public buckets, over-permissive IAM bindings, open firewall rules, and unencrypted resources.

Guided remediation

Get prioritized fixes and, on approval, apply changes to close the gaps.

Before You Start

  • A Collector deployed where it can reach the Google Cloud APIs over HTTPS. See Deploying the agent.
  • A service account with a JSON key and least-privilege roles — Viewer and Security Reviewer are enough for analysis; add narrowly scoped roles only for remediation.
  • Your project ID and project number.

Step 1 — Create the Credential in Google Cloud

1

Enable the required APIs

In the Google Cloud console, enable the Cloud Resource Manager API (and any service APIs you want Myrmex to read) for the project you’re connecting.
2

Create a service account

In IAM & Admin → Service Accounts, create a dedicated service account for Myrmex.
3

Grant least-privilege roles

Assign Viewer and Security Reviewer for analysis. Add write-capable roles only when you want Myrmex to remediate.
4

Generate a JSON key

On the service account’s Keys tab, add a key of type JSON and download it. You’ll paste its contents into Myrmex.
Keep the service account read-only for analysis and grant write roles only when you’re ready for the agents to apply changes.

Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Google Cloud Platform (GCP), then fill in:

Connect

Click Connect to validate the credentials and finish. The project then appears under Environment → Integrations, and you can start asking the AI about it in the Workspace.
Prefer least privilege: a Viewer + Security Reviewer service account covers analysis, and you can rotate the JSON key at any time.