CIS Google Cloud Platform Foundation Benchmark v1.2.0/Virtual Machines/45 of 83
4.8Ensure Compute instances are launched with Shielded VM enabled
Control family: Virtual Machines
Control description
To defend against against advanced threats and ensure that the boot loader and firmware on your VMs are signed and untampered, it is recommended that Compute instances are launched with Shielded VM enabled.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Shielded VM checks that a VM boots only signed, untampered firmware and boot software, and measures each boot so changes can be spotted. Its three parts are Secure Boot, the virtual Trusted Platform Module and integrity monitoring. VMs run with Shielded VM turned on. Container-Optimized OS images support all three and are configured to CIS Level 1 by default, which suits container workloads.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree that VMs use images that support Shielded VM, and which exceptions are allowed (custom or unsigned drivers).
- Decide whether Container-Optimized OS VMs are also checked against that image's own CIS benchmark, and at which level.
Evidence
- The VM image standard and the exception register
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks turn on Shielded VM for each VM in Compute Engine, require it with an organization policy, check the guest OS with the Container-Optimized OS CIS scanner where you use that image, and watch with Security Command Center.
Task 1Turn on Shielded VM for a VM
- Sign in to the Google Cloud console at console.cloud.google.com and open Compute Engine > VM instances.
- Choose the VM and, on the Instance details page, choose Stop.
- When it has stopped, choose Edit.
- In the Shielded VM section, turn on vTPM and Integrity Monitoring, and Secure Boot unless the VM uses custom or unsigned drivers.
- Choose Save, then Start.
- Check it: the Instance details page shows the Shielded VM options on. If the image doesn't support Shielded VM, rebuild the VM from one that does.
Task 2Prevent it with the organization policy compute.requireShieldedVm
- Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
- Search for compute.requireShieldedVm (Shielded VMs) and open it.
- Choose Manage policy, select Override parent's policy, choose Add a rule and set Enforcement to On.
- Choose Set policy.
- Check it: creating a VM from an image without Shielded VM support is refused.
Task 3Check the guest OS against its own CIS benchmark on Container-Optimized OS
- Where a VM runs Container-Optimized OS, open it in VM instances and choose SSH.
- Check the built-in Level 1 scan: the cis-level1 service runs at boot and reports the number of non-compliant checks, which should be zero.
- For Level 2, start the cis-level2 service, or set it in the VM's user-data metadata so it runs on every boot; evaluate first, since Level 2 can affect applications.
- To keep checking daily on many VMs, use Compute Engine > OS policies to create an OS policy assignment that starts the cis-compliance-scanner timer.
- Check it: the scan result on the VM lists no non-compliant checks, or each one is a documented exception.
Task 4Keep it checked with the Security Health Analytics finding SHIELDED_VM_DISABLED
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category SHIELDED_VM_DISABLED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and turn on Shielded VM for the instance it names.
- Check it: after the next Security Health Analytics scan, no active SHIELDED_VM_DISABLED finding remains.
Evidence
- Instance details of each VM, showing Shielded VM on
- The compute.requireShieldedVm policy, enforced
- For Container-Optimized OS VMs, the CIS scanner result
- Security Command Center, with no active SHIELDED_VM_DISABLED finding
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.