Home/By platform/Everything for Google Cloud
Everything for Google Cloud
Every template, lesson, refresher, and planner on this site that applies to Google Cloud, in one place.
The list includes Google Workspace, which uses the same sign-in and logging services.
To compare the four clouds with each other, service by service, read The four clouds side by side.
Alerts
The templates below create 33 alerts for Google Cloud. Each link opens the alerts table filtered to one platform, with what fires each alert, the log it reads, and how someone hears.
Standard and Hardened also install 20 saved queries for working a case. The incident response lesson lists them, with the template that installs each one.
Templates
19 templates have code for Google Cloud, written for Terraform. All 57 levels are Ready. What each level includes.
| Template | Platform | Quick start | Standard | Hardened | Refresher |
|---|---|---|---|---|---|
| Evidence that survives terminationLogging and evidence | Google Cloud | Ready | Ready | Ready | One page |
| Evidence from a compromised containerLogging and evidence | Google Cloud | Ready | Ready | Ready | One page |
| Audit logs nobody can deleteLogging and evidence | Google Cloud | Ready | Ready | Ready | One page |
| Get cloud logs into your SIEMLogging and evidence | Google Cloud | Ready | Ready | Ready | One page |
| Keep network records long enough to be usefulLogging and evidence | Google Cloud | Ready | Ready | Ready | One page |
| An analysis machine that cannot reach productionLogging and evidence | Google Cloud | Ready | Ready | Ready | One page |
| Emergency access that works when login is brokenIdentity and access | Google Cloud | Ready | Ready | Ready | One page |
| Shell access without opening a portIdentity and access | Google Cloud | Ready | Ready | Ready | One page |
| Somewhere to keep secrets that rotates themIdentity and access | Google Cloud | Ready | Ready | Ready | One page |
| Encryption keys you control and can switch offIdentity and access | Google Cloud | Ready | Ready | Ready | One page |
| Cloud access for pipelines and pods without stored keysIdentity and access | Google Cloud | Ready | Ready | Ready | One page |
| Block the changes you never wantGuardrails and compliance | Google Cloud | Ready | Ready | Ready | One page |
| Check every resource against your rules, all the timeGuardrails and compliance | Google Cloud | Ready | Ready | Ready | One page |
| Data that cannot leave your organisationGuardrails and compliance | Google Cloud | Ready | Ready | Ready | One page |
| A record of every action against the cluster APIKubernetes | Google Cloud | Ready | Ready | Ready | One page |
| Notice data walking out the doorDetection and response | Google Cloud | Ready | Ready | Ready | One page |
| Catch account takeover at the identity providerDetection and response | Google Workspace | Ready | Ready | Ready | One page |
| Know who is using your AI modelsAI | Google Cloud | Ready | Ready | Ready | One page |
| A safe place to keep Terraform statePipeline and state | Google Cloud | Ready | Ready | Ready | One page |
Incident response
The lessons to read before an incident on Google Cloud, the most specific first, and to keep open during one.
Audit log defaults, reading identities, containment, VM forensics, and Security Command Center.
Phases, scoping, containment per cloud, preserving evidence, incident command, and reviews.
Audit logs, pod identities, nodes, and managed modes on GKE and EKS, and how to respond on each.
One LLMjacking case from alert to containment, the record each cloud keeps, the saved queries, and how to size the bill and the data exposure.
Roles adapted from the Incident Command System, the first hour and operational periods, decision records, disclosure clocks, NIST SP 800-61r3, and a maturity ladder.
One-page refreshers
Each prints on one page. Every template in the table above links its own.
What Google Cloud records by default, how to read an identity out of it, and the first moves for each kind of compromise.
The same phases as any incident, with evidence that disappears faster, more ways for an attacker to come back, and most actions taken through APIs.
The fastest safe way to cut an attacker off, by what they have, and what each move leaves open.
What each cloud records about a cluster, how to keep a node, and what to rely on when you cannot reach it.
Five roles adapted from the Incident Command System, the rhythm they work to, and how they pass from one person to a team.
AWS, Azure, Google Cloud, and Oracle Cloud share the same building blocks under different names.
A tool that creates and changes cloud resources to match .tf files. OpenTofu is its open-source fork, and takes the same files with tofu in place of terraform.
Log planning
The log source planner lists every log source to turn on, how long each is kept by default, and what it costs. This link opens it set to Google Cloud, GKE, and Google Workspace.