Check ID:
Provider: GCP
Service:
Severity: MEDIUM
Categories:
Resource type:
compute_instance_ip_forwarding_is_enabledProvider: GCP
Service:
computeSeverity: MEDIUM
Categories:
trust-boundariesResource type:
compute.googleapis.com/InstanceWhat this check verifies
Compute Engine VM instances withcanIpForward enabled are identified. This setting allows a VM to process packets not addressed to its own IP.
Instances created by GKE (gke- prefix) are excluded from this evaluation.
Risk
With IP forwarding a VM can route traffic for other addresses. If compromised, it can:- Spoof or tamper flows (integrity)
- Intercept/redirect internal traffic (confidentiality)
- Mask egress for exfiltration and enable lateral movement, degrading availability
Recommendation
Disable IP forwarding on general-purpose VMs and allow it only for vetted network appliances, following least privilege. Enforce network segmentation, restrict routes, review exceptions regularly, and monitor egress to uphold defense in depth. Exclude platform-managed nodes that require forwarding.Remediation
- CLI
- Terraform
- Dashboard steps
References
- https://cloud.google.com/compute/docs/instances/create-start-instance
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/gcp/ComputeEngine/disable-ip-forwarding.html
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_instance_ip_forwarding_is_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