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

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

4.1Ensure that instances are not configured to use the default service account

Control family: Virtual Machines

Control description

It is recommended to configure your instance to not use the default Compute Engine service account because it has the Editor role on the project.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

The Compute Engine default service account is given the Editor role on the project in many organizations, so any VM using it can change almost everything in the project. Each workload runs as its own service account with only the roles it needs.

Before you start

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

  • Agree that each workload runs as its own service account with only the roles it needs.
  • Name who creates service accounts and reviews their roles.

Evidence

  • The service account standard for VMs

On Google Cloud the tasks create a dedicated service account, move each VM onto it in Compute Engine, and watch for VMs still on the default with Security Command Center.

Task 1Create a service account for the workload

  1. Sign in to the Google Cloud console at console.cloud.google.com and open IAM & Admin > Service accounts.
  2. Choose Create service account, give it a name that matches the workload and choose Create and continue.
  3. Grant only the roles the workload needs, such as Logs Writer and Monitoring Metric Writer, plus access to its own data.
  4. Choose Done.

Task 2Move each VM off the default service account

  1. Open Compute Engine > VM instances and choose the VM.
  2. On the Instance details page, choose Stop and wait for it to stop.
  3. Choose Edit.
  4. Under Service account, choose the dedicated service account instead of the Compute Engine default service account.
  5. Choose Save, then Start.
  6. Check it: the Instance details page shows the new service account.

Task 3Keep it checked with the Security Health Analytics finding DEFAULT_SERVICE_ACCOUNT_USED

  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 DEFAULT_SERVICE_ACCOUNT_USED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and move the VM it names to a dedicated service account.
  4. Check it: after the next Security Health Analytics scan, no active DEFAULT_SERVICE_ACCOUNT_USED finding remains.

Evidence

  • VM instances details, each showing a dedicated service account
  • Security Command Center, with no active DEFAULT_SERVICE_ACCOUNT_USED 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.