Ensure log sinks are configured to export logs
Logs should be exported to external storage for long-term retention.
Security Impact
Without sinks, logs may be lost after retention period expires.
How to Remediate
Create log sinks to export to Cloud Storage, BigQuery, or Pub/Sub.
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 Logging 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 CIS GCP v1.3.0, SOC 2, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- gcp-logging-3
- Service
- Google Cloud Logging
- Category
- Log Management
- Severity
- MEDIUM
- CIS Benchmark
- 2.3
Automate This Check
TigerGate automatically scans your GCP environment for this and 79+ other security checks.
Start Free TrialRelated Google Cloud Logging Checks
View all checksEnsure Cloud Audit Logging is enabled for all services
Ensure log bucket retention is configured
Ensure log metric filters and alerts are configured
Ensure alert for VPC network changes is configured
Ensure alert for Cloud Storage IAM changes is configured