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

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

1.14Ensure API keys are restricted to only APIs that application needs access

Control family: Identity and Access Management

Control description

API 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 restrict API keys to use (call) only APIs required by an application.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

By default an API key can call any API enabled in its project. Limiting each key to the APIs its application uses means a copied key can't be turned against everything else the project offers.

Before you start

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

  • For each API key that must stay, record which Google APIs its application calls.
  • Make an API restriction a condition of approving a new key.

Evidence

  • The API key inventory with the APIs each key may call

On Google Cloud the tasks add API restrictions to each key in APIs & Services, then watch with Security Command Center.

Task 1Restrict which APIs each key can call

  1. Sign in to the Google Cloud console at console.cloud.google.com and open APIs & Services > Credentials.
  2. In the API keys section, on the row of the key, choose Actions > Edit API key.
  3. Under API restrictions, select Restrict key (shown as Restrict APIs in some versions).
  4. In Select APIs, choose only the APIs the application calls.
  5. Choose Save; the change can take a few minutes.
  6. Check it: a call with the key to an API not on the list is refused.

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

  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_APIS_UNRESTRICTED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and add API restrictions to the key it names.
  4. Check it: after the next Security Health Analytics scan, no active API_KEY_APIS_UNRESTRICTED finding remains.

Evidence

  • The Edit API key page of each key, showing its API restrictions
  • Security Command Center, with no active API_KEY_APIS_UNRESTRICTED 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.