Google CloudOverview
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.
Rationale
Logs can be exported by creating one or more sinks that include a log filter and a destination. As Cloud Logging receives new log entries, they are compared against each sink. If a log entry matches a sink's filter, then a copy of the log entry is written to the destination. Sinks can be configured to export logs in storage buckets. It is recommended to configure a data retention policy for these cloud storage buckets and to lock the data retention policy; thus permanently preventing the policy from being reduced or removed. This way, if the system is ever compromised by an attacker or a malicious insider who wants to cover their tracks, the activity logs are definitely preserved for forensics and security investigations.
Impact
Locking a bucket is an irreversible action. Once you lock a bucket, you cannot remove the retention policy from the bucket or decrease the retention period for the policy. You will then have to wait for the retention period for all items within the bucket before you can delete them, and then the bucket.
Remediation guidance
From Google Cloud Console
- If sinks are not configured, first follow the instructions in the recommendation: Ensure that sinks are configured for all Log entries
- For each storage bucket configured as a sink, go to the Cloud Storage browser at https://console.cloud.google.com/storage/browser/
. - Select the
Bucket Locktab near the top of the page. - In the Retention policy entry, click the Add Duration link. The
Set a retention policydialog box appears. - Enter the desired length of time for the retention period and click
Save policy. - Set the
Lock statusfor this retention policy to Locked.
Using Google Cloud CLI
- To list all sinks destined to storage buckets:
gcloud logging sinks list --folder=<folderID> | --organization=<organizationID> | --project=<projectID>
- For each storage bucket listed above, set a retention policy and lock it:
gsutil retention set <timeDuration> gs://<bucketName>
gsutil retention lock gs://<bucketName>
For more information, visit https://cloud.google.com/storage/docs/using-bucket-lock#setpolicy
Default value
By default, storage buckets used as log sinks do not have retention policies and Bucket Lock configured.
References
- https://cloud.google.com/storage/docs/bucket-lock
- https://cloud.google.com/storage/docs/using-bucket-lock
- https://cloud.google.com/storage/docs/bucket-lock
Multiple Remediation Paths
Google Cloud
SERVICE-WIDE (RECOMMENDED when many resources are affected): Enforce Organization Policies at org/folder level so new resources inherit secure defaults.
gcloud org-policies set-policy policy.yaml
ASSET-LEVEL: Use the product-specific remediation steps above for only the impacted project/resources.
PREVENTIVE: Use org policy constraints/custom constraints and enforce checks in deployment pipelines.
References for Service-Wide Patterns
- GCP Organization Policy overview: https://cloud.google.com/resource-manager/docs/organization-policy/overview
- GCP Organization policy constraints catalog: https://cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints
- gcloud org-policies: https://cloud.google.com/sdk/gcloud/reference/org-policies
Operational Rollout Workflow
Use this sequence to reduce risk and avoid repeated drift.
1. Contain at Service-Wide Scope First (Recommended)
- Google Cloud: apply organization policy constraints at org/folder scope.
gcloud org-policies set-policy policy.yaml
2. Remediate Existing Affected Assets
- Execute the control-specific Console/CLI steps documented above for each flagged resource.
- Prioritize internet-exposed and production assets first.
3. Validate and Prevent Recurrence
- Re-scan after each remediation batch.
- Track exceptions with owner and expiry date.
- Add preventive checks in IaC/CI pipelines.
Query logic
These are the stored checks tied to this control.
Retention policies on log buckets are configured using Bucket Lock
Connectors
Covered asset types
Expected check: eq []
logBuckets(where:{locked:false}){...AssetFragment}
