Compliancemanzill.com
CIS Google Cloud Platform Foundation Benchmark v1.2.0

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Virtual Machines/40 of 83

4.3Ensure "Block Project-wide SSH keys" is enabled for VM instances

Control family: Virtual Machines

Control description

It is recommended to use Instance specific SSH key(s) instead of using common/shared project-wide SSH key(s) to access Instances.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

SSH keys added to project metadata let their holders into every VM in the project. Blocking project-wide keys on a VM means only keys added for that VM, or access through OS Login (4.4), can be used, so one leaked shared key doesn't open the whole fleet.

Before you start

The same on every cloud, before the steps in the tabs.

  • Decide how people get SSH access: OS Login (4.4) or keys added per VM, never shared project-wide keys.
  • Remove project-wide keys that nobody owns.

Evidence

  • The SSH access standard

On Google Cloud the tasks block project-wide SSH keys on each VM in Compute Engine, then watch with Security Command Center.

Task 1Block project-wide SSH keys on a VM

  1. Sign in to the Google Cloud console at console.cloud.google.com and open Compute Engine > VM instances.
  2. Choose the VM and, on the VM instance details page, choose Edit (VMs created from instance templates are changed in the template instead).
  3. Under SSH Keys, select Block project-wide SSH keys.
  4. Choose Save.
  5. Check it: a user whose key is only in project metadata can no longer connect, while OS Login or instance keys still work.

Task 2Keep it checked with the Security Health Analytics finding COMPUTE_PROJECT_WIDE_SSH_KEYS_ALLOWED

  1. Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
  2. In the query editor, filter on category COMPUTE_PROJECT_WIDE_SSH_KEYS_ALLOWED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and block project-wide keys on the VM it names.
  4. Check it: after the next Security Health Analytics scan, no active COMPUTE_PROJECT_WIDE_SSH_KEYS_ALLOWED finding remains.

Evidence

  • VM instance details, showing project-wide SSH keys blocked
  • Security Command Center, with no active COMPUTE_PROJECT_WIDE_SSH_KEYS_ALLOWED 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.