CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/15 of 83
1.15Ensure API keys are rotated every 90 days
Control family: Identity and Access Management
Control description
It is recommended to rotate API keys every 90 days.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
API keys don't expire on their own. Replacing each one at least every 90 days limits how long a leaked key stays useful. The console can generate a replacement while the old key keeps working, so applications can move over before the old one is deleted.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree the rotation period for API keys (90 days or less) and who rotates each one.
- Make sure each application can take a new key without a code change, for example from a secrets store.
Evidence
- The API key rotation schedule with owners
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks rotate each key from its edit page in APIs & Services, then watch with Security Command Center.
Task 1Rotate an API key
- Sign in to the Google Cloud console at console.cloud.google.com and open APIs & Services > Credentials.
- In the API keys section, on the row of the key, choose Actions > Edit API key.
- If the Creation date is more than 90 days ago, choose Rotate key, optionally rename it, and choose Create.
- Update the application to use the new key.
- Return to Edit API key and choose Delete the previous key.
- Check it: the key's creation date is within the last 90 days and the application still works.
Task 2Keep it checked with the Security Health Analytics finding API_KEY_NOT_ROTATED
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category API_KEY_NOT_ROTATED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and rotate the key it names.
- Check it: after the next Security Health Analytics scan, no active API_KEY_NOT_ROTATED finding remains.
Evidence
- The API keys list, with every key created in the last 90 days
- Security Command Center, with no active API_KEY_NOT_ROTATED 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.