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

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Logging and Monitoring/18 of 83

2.3Ensure that retention policies on log buckets are configured using Bucket Lock

Control family: Logging and Monitoring

Control description

Enabling retention policies on log buckets will protect logs stored in cloud storage buckets from being overwritten or accidentally deleted. It is recommended to set up retention policies and configure Bucket Lock on all storage buckets that are used as log sinks.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Logs exported to Cloud Storage are evidence, so they shouldn't be deletable early by anyone, including an attacker with admin rights. A retention policy stops objects being deleted or replaced before they reach a set age, and Bucket Lock makes that policy permanent so it can't be shortened or removed.

Before you start

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

  • Agree how long logs must be kept (for example one year, or longer if a law or contract requires it), and get sign-off before locking, since it is permanent.

Evidence

  • The approved retention period

On Google Cloud the tasks set and lock a retention policy on each log sink bucket in Cloud Storage, then watch with Security Command Center.

Task 1Set and lock a retention policy on the log bucket

  1. Sign in to the Google Cloud console at console.cloud.google.com and open Cloud Storage > Buckets.
  2. Choose the bucket a sink writes to.
  3. On the Bucket details page, choose the Retention tab (named Protection in newer layouts).
  4. Choose Set Retention Policy, enter the agreed retention period and choose Save.
  5. Check the period is right, because locking can't be undone: only deleting the whole bucket removes it.
  6. Choose Lock and confirm.
  7. Check it: the bucket shows the retention policy as locked.

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

  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 LOCKED_RETENTION_POLICY_NOT_SET with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and lock a retention policy on the bucket it names.
  4. Check it: after the next Security Health Analytics scan, no active LOCKED_RETENTION_POLICY_NOT_SET finding remains.

Evidence

  • The Retention details of each log sink bucket, showing a locked policy and its period
  • Security Command Center, with no active LOCKED_RETENTION_POLICY_NOT_SET 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.