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

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/12 of 83

1.12Ensure API keys are not created for a project

Control family: Identity and Access Management

Control description

Keys are insecure because they can be viewed publicly, such as from within a browser, or they can be accessed on a device where the key resides. It is recommended to use standard authentication flow instead.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

An API key is a plain string that identifies a project, not a person or a workload, and it often ends up in web pages, mobile apps and code. Anyone who finds it can use it. Workloads authenticate with service accounts or OAuth instead, and API keys are kept only for the few Google APIs that require them.

Before you start

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

  • List the applications that use API keys and which Google APIs require them; everything else moves to service accounts or OAuth.
  • Agree who may approve a new API key and why.

Evidence

  • The API key inventory with the reason each one is kept

On Google Cloud the tasks move applications off API keys and delete the keys in APIs & Services, then watch with Security Command Center.

Task 1Delete API keys that aren't needed

  1. Sign in to the Google Cloud console at console.cloud.google.com and pick the project.
  2. Open APIs & Services > Credentials and look at the API keys section.
  3. For each key, find which application uses it and move it to a service account or OAuth where the API allows.
  4. On the row of each key no longer needed, choose Actions > Delete API key and confirm.
  5. Check it: the API keys section lists only keys for APIs that require them, each restricted as in 1.13 and 1.14.

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

  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 API_KEY_EXISTS with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and delete the key it names or record why it must stay.
  4. Check it: after the next Security Health Analytics scan, no active API_KEY_EXISTS finding remains.

Evidence

  • The API keys section of each project, with only justified keys left
  • Security Command Center, with no active API_KEY_EXISTS finding except recorded exceptions

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.