VPC flow logs for VPC network subnets are disabled Affecting Compute Engine service in Google
Severity Framework
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Snyk CCSS
Rule category
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
Logging/ Configuration
Is your environment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsFrameworks
CIS-ControlsCIS-GoogleHIPAAISO-27001NIST-800-53SOC-2
- Snyk IDSNYK-CC-00386
- creditSnyk Research Team
Description
Flow logs should be enabled for every business-critical VPC subnet, as they provide visibility into network traffic for each VM inside the subnet and can be used to detect anomalous traffic or insight during security workflows.
How to fix?
Define a log_config field with aggregation_interval, flow_sampling and metadata subfields.
Example configuration:
resource "google_compute_subnetwork" "test" {
name = "test-subnetwork"
ip_cidr_range = "10.2.0.0/16"
region = "us-east1"
network = google_compute_network.test.id
log_config {
aggregation_interval = "INTERVAL_10_MIN"
flow_sampling = 0.5
metadata = "INCLUDE_ALL_METADATA"
}
}