Check ID: compute_subnet_flow_logs_enabled
Provider: GCP
Service: compute
Severity: MEDIUM
Categories: logging, forensics-ready
Resource type: compute.googleapis.com/Subnetwork

What this check verifies

GCP VPC subnets have VPC Flow Logs enabled at the subnet scope to capture connection metadata for traffic to and from VM interfaces.

Risk

Without VPC Flow Logs, network activity lacks visibility, weakening detection and response. Blind spots enable covert data exfiltration (C), undetected lateral movement and policy bypass (I), and hinder containment and recovery (A). Forensics and cost insights are degraded.

Recommendation

Enable VPC Flow Logs on all production subnets. Tune aggregation, sampling, and metadata to balance visibility and cost. Export to centralized logging for analytics and alerting, apply least privilege to log access, and use organization guardrails to enforce consistent coverage as part of defense in depth.

Remediation

gcloud compute networks subnets update <SUBNET_NAME> —region <REGION> —enable-flow-logs

References

Where this check fires

This check runs on every scheduled scan against your GCP account. Findings appear at Cloud Security → Findings filterable by Check ID = compute_subnet_flow_logs_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