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

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

4.2Ensure that instances are not configured to use the default service account with full access to all Cloud APIs

Control family: Virtual Machines

Control description

To support principle of least privileges and prevent potential privilege escalation it is recommended that instances are not assigned to default service account `Compute Engine default service account` with Scope `Allow full access to all Cloud APIs`.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Access scopes are an older, coarse limit on what a VM's service account can call. Combining the default service account, which often has Editor, with the scope that allows every Cloud API hands the VM near-full control of the project. VMs that must keep the default service account get default access or per-API scopes instead.

Before you start

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

  • List the VMs that still use the default service account and plan their move to dedicated ones (4.1).
  • Agree that no new VM uses full access to all Cloud APIs.

Evidence

  • The list of affected VMs and the migration plan

On Google Cloud the tasks change the access scopes of affected VMs in Compute Engine, then watch with Security Command Center.

Task 1Remove full API access from the 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 if it is running choose Stop.
  3. When it has stopped, choose Edit.
  4. In Security and access, under Access scopes, choose Allow default access, or Set access for each API with Cloud Platform set to None and only the needed APIs on.
  5. Choose Save, then Start.
  6. Check it: the Instance details page no longer shows full access to all Cloud APIs. Better still, move it to a dedicated service account (4.1).

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

  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 FULL_API_ACCESS with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and change the scopes of the VM it names.
  4. Check it: after the next Security Health Analytics scan, no active FULL_API_ACCESS finding remains.

Evidence

  • VM instances details, showing no VM with the default service account and full API access
  • Security Command Center, with no active FULL_API_ACCESS 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.