GCP Vertex AI Workbench Notebook Secure Boot Disabled
The instance will boot unsigned or modified firmware, so a compromise below the operating system survives reinstalls and is invisible to it.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Exposure and fragility, security posture and single points of failure.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable Secure Boot on the Workbench notebook.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Vertex AI Workbench Notebooks on Google Cloud
- The fix, by hand
- Stop the Workbench instance.
- Enable Shielded VM "Secure Boot" (with vTPM + integrity monitoring).
These are the steps the finding carries in the product.
- Category
- Security. Risky configurations: privileged containers, containers running as root, host networking, ingress without TLS.
- Where it appears
- The Risk tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1236- Full reference
Related checks
See the security 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.