CIS Google Cloud Platform Foundation Benchmark v1.2.0/Identity and Access Management/10 of 83
1.10Ensure KMS encryption keys are rotated within a period of 90 days
Control family: Identity and Access Management
Control description
Google Cloud Key Management Service stores cryptographic keys in a hierarchical structure designed for useful and elegant access control management.
The format for the rotation schedule depends on the client library that is used. For the gcloud command-line tool, the next rotation time must be in `ISO` or `RFC3339` format, and the rotation period must be in the form `INTEGER[UNIT]`, where units can be one of seconds (s), minutes (m), hours (h) or days (d).
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Rotating a key creates a new key version for new encryption, while older versions stay available to decrypt existing data. A rotation period of 90 days or less limits how much data any one version protects. Cloud KMS rotates automatically once a period is set.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree the rotation period for symmetric keys (90 days or less) and any exceptions, with who approved them.
- Name the owner of each key ring.
Evidence
- The key management standard and the list of key owners
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks set a rotation period on each symmetric key in Key Management, then watch with Security Command Center.
Task 1Set a 90-day rotation period on a key
- Sign in to the Google Cloud console at console.cloud.google.com and open Security > Key Management.
- Choose the key ring, then the key.
- Choose Edit Rotation Period.
- Set the rotation period to 90 days or less and choose the first rotation date.
- Choose Save.
- Check it: the key's details show the rotation period and the next rotation time.
Task 2Keep it checked with the Security Health Analytics finding KMS_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 KMS_KEY_NOT_ROTATED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and set a rotation period on the key it names.
- Check it: after the next Security Health Analytics scan, no active KMS_KEY_NOT_ROTATED finding remains.
Evidence
- The key details of each symmetric key, showing a rotation period of 90 days or less
- Security Command Center, with no active KMS_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.