Check ID:
Provider: GCP
Service:
Severity: LOW
Resource type:
cloudstorage_bucket_lifecycle_management_enabledProvider: GCP
Service:
cloudstorageSeverity: LOW
Resource type:
storage.googleapis.com/BucketWhat this check verifies
Cloud Storage buckets use Object Lifecycle Management with at least one valid rule (supportedaction and non-empty condition) to automatically transition storage class or delete objects.
Risk
Without lifecycle rules, data and object versions persist indefinitely, expanding the attack surface and hindering mandated erasure. Stale data amplifies exfiltration impact (confidentiality) and complicates integrity controls, while also driving avoidable cost and retention noncompliance.Recommendation
Define lifecycle policies by data classification to enforce least data retention. UseDelete for TTL/age and SetStorageClass for archival, with version-aware conditions like isLive=false or numNewerVersions. Test on a limited dataset, review regularly, and align with defense in depth.
Remediation
- CLI
- Terraform
- Dashboard steps
References
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/gcp/CloudStorage/enable-lifecycle-management.html
- https://docs.cloud.google.com/storage/docs/managing-lifecycles
- https://docs.cloud.google.com/storage/docs/lifecycle
- https://docs.cloud.google.com/storage/docs/samples/storage-enable-bucket-lifecycle-management
Where this check fires
This check runs on every scheduled scan against your GCP account. Findings appear at Cloud Security → Findings filterable byCheck ID = cloudstorage_bucket_lifecycle_management_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to GCP checks