Ensure GCS bucket logging is enabled
Access logs should be enabled to track bucket access and operations.
Security Impact
Without logging, unauthorized access cannot be detected or investigated.
How to Remediate
Enable access logs and configure a destination bucket for log storage.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your GCP environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Google Cloud Storage resources across your GCP projects every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- gcp-storage-4
- Service
- Google Cloud Storage
- Category
- Logging
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your GCP environment for this and 79+ other security checks.
Start Free TrialRelated Google Cloud Storage Checks
View all checksEnsure GCS buckets are not publicly accessible
Ensure uniform bucket-level access is enabled
Ensure GCS bucket encryption uses CMEK
Ensure GCS bucket versioning is enabled
Ensure GCS bucket lifecycle policies are configured