Check ID:
Provider: GCP
Service:
Severity: HIGH
Categories:
Resource type:
compute_loadbalancer_logging_enabledProvider: GCP
Service:
computeSeverity: HIGH
Categories:
loggingResource type:
compute.googleapis.com/BackendServiceWhat this check verifies
Application Load Balancer (HTTP/S) backend services have Cloud Logging for requests enabled at the backend service level. Only load balancers with a backend service support this setting.Risk
Without request logs, visibility into HTTP(S) traffic is reduced, hindering detection of credential stuffing, path traversal, WAF bypass, and data exfiltration. This impacts confidentiality and integrity, and delays incident response; availability issues (surges in5xx) may go unnoticed.
Recommendation
Enable request logging on backend services with a risk-appropriatesampleRate; include key optional fields when needed. Export logs to monitoring for alerts and dashboards, enforce retention and integrity controls, and restrict access using least privilege and defense in depth.
Remediation
- CLI
- Terraform
- Dashboard steps
gcloud compute backend-services update <example_resource_name> —global —enable-logging
References
- https://cloud.google.com/load-balancing/docs/https/https-logging-monitoring#gcloud:-global-mode
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/gcp/CloudLoadBalancing/https-load-balancer-logging-enabled.html
- https://cloud.google.com/load-balancing/docs/l7-internal/monitoring
Where this check fires
This check runs on every scheduled scan against your GCP account. Findings appear at Cloud Security → Findings filterable byCheck ID = compute_loadbalancer_logging_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