GCP VM Shielded VM Not Enabled
The VM will boot modified firmware or a tampered kernel without detection, so a persistent compromise survives reinstalls.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable Shielded VM on Compute Engine VM.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Compute Engine on Google Cloud
- The fix, by hand
- Verify the VM boot image supports Shielded VM (most public images do; custom images need UEFI).
- Stop the VM: gcloud compute instances stop ‹name› --zone=‹zone›.
- Enable Shielded options: gcloud compute instances update ‹name› --zone=‹zone› --shielded-secure-boot --shielded-vtpm --shielded-integrity-monitoring.
- Start the VM: gcloud compute instances start ‹name› --zone=‹zone›.
- Watch Cloud Logging for any integrity-monitoring failures over the next 24h. Failures show under compute.googleapis.com/shielded_vm_integrity.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1203- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.