Core Compute & Networking
Custom KVM Isolation
Google replaced QEMU with its own user-space virtual machine monitor, which removes an enormous, historically bug-prone C codebase from the isolation boundary. QEMU escapes are a real category with a real CVE history, so cutting it is a substantive decision rather than a slide. It is also, as on the other two clouds, not the thing that will breach you. Your risk is a service account key in a repository.
Andromeda SDN
Packet Mirroring is built into the Andromeda SDN rather than bolted on, which makes deep packet inspection a policy you write instead of an appliance you route traffic through. It is the best native network forensics story of the three clouds. The costs are the ordinary ones and they are still worth stating: you pay for mirrored bandwidth and for the sensor fleet consuming it, and mirroring encrypted traffic gives you metadata and timing, not content. Decide what question you are trying to answer before you decide what to mirror.
Under the Hood Architecture
Cryptographic Boot
Google's binary provenance system ties the code running on production hosts back to reviewed source, from the boot loader upwards. It is a genuinely strong supply-chain control and it protects Google's layer, not yours — the equivalent guarantee for your own workloads is Binary Authorization, which you have to configure, and which most teams run in dry-run mode indefinitely because enforcing it breaks the first emergency deploy.
IAM Friction & Security Tax
Provisioning is separate from access management, and automated SCIM deprovisioning sits behind Cloud Identity Premium at roughly $7.20 per user per month. Charging for the control that removes a leaver's access on their last day is a poor incentive, and the predictable result is estates running manual offboarding — which fails silently, because nobody notices an account that was not disabled. Price the premium tier against the cost of a dormant account with production IAM roles, and it stops looking expensive.
Real-World Attack Surface
Cloud Shell Escapes (CVE-2026-35428)
Cloud Shell has had command-injection and container-escape research published against it, which is what you would expect from an interactive Linux environment handed out free to anyone with a Google account. The reason it matters is what Cloud Shell holds rather than what it is: an authenticated session with your credentials already loaded and gcloud configured. It is the most convenient path from a browser to your production project, for you and for anyone who takes over your session.
Google Groups Privilege Creep
Granting IAM roles to Google Groups is the recommended pattern, and it quietly moves authorisation into Workspace, where group membership is administered by people who do not think of themselves as granting cloud permissions. A group that is open or joinable on request becomes a self-service path to whatever it was granted. Nothing in the GCP console shows this — the binding looks correct, because it is; the membership is the problem, and it is managed somewhere else entirely.
Mandatory Hardening Baseline
- Audit Google Groups: enumerate every group holding an IAM binding and check its join policy, not just its membership. Then decide who owns that check going forward, because a group's settings can change in Workspace without any signal reaching the cloud estate.
- Limit Cloud Shell Access: restrict and log it. Expect resistance — Cloud Shell is genuinely the fastest way to do almost anything, and taking it away pushes people to local credentials on laptops, which is worse. Restrict it in production projects and leave it alone elsewhere.
- Enforce VPC Service Controls: a service perimeter blocks data movement out of sensitive projects even when the credentials used are entirely valid, which is the one control that survives credential theft. It is also the control most likely to break something legitimate at 3 a.m. — perimeter denials surface as opaque permission errors with no indication that a perimeter is involved. Roll it out in dry-run first and read the logs for a fortnight before enforcing.
Architecture Comparison
| Component | GCP | AWS |
|---|---|---|
| Isolation Architecture | KVM (Custom/Non-QEMU) | Nitro System (Hardware) |
| Network Visibility | Native Packet Mirroring | VPC Flow Logs |
| Identity Security Tax | Severe ($7.20/user/mo SCIM) | Moderate (AD costs) |
| Key Management | KMS / Cloud HSM (L3) | KMS / CloudHSM (L3) |
