Compliancemanzill.com
CIS Google Cloud Platform Foundation Benchmark v1.2.0

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Virtual Machines/43 of 83

4.6Ensure that IP forwarding is not enabled on Instances

Control family: Virtual Machines

Control description

Compute Engine instance cannot forward a packet unless the source IP address of the packet matches the IP address of the instance. Similarly, GCP won't deliver a packet whose destination IP address is different than the IP address of the instance receiving the packet. However, both capabilities are required if you want to use instances to help route packets.

Forwarding of data packets should be disabled to prevent data loss or information disclosure.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

IP forwarding lets a VM send and receive packets addressed to other machines, which only routers, NAT gateways and network appliances need. On any other VM it allows traffic to be routed around your controls. The setting can only be chosen when a VM is created, so ordinary VMs that have it are recreated without it.

Before you start

The same on every cloud, before the steps in the tabs.

  • List the VMs that genuinely route traffic (NAT gateways, firewalls, VPN appliances) and approve them by name.
  • Agree that every other VM has IP forwarding off.

Evidence

  • The approved list of routing appliances

On Google Cloud the tasks recreate VMs that have IP forwarding without it in Compute Engine, restrict who can use it with an organization policy, and watch with Security Command Center.

Task 1Recreate the VM with IP forwarding off

  1. Sign in to the Google Cloud console at console.cloud.google.com and open Compute Engine > VM instances.
  2. Confirm the VM isn't a router or network appliance, and take a machine image or snapshots of its disks so it can be rebuilt.
  3. Select the VM and choose Delete.
  4. Choose Create instance to build its replacement from the machine image or snapshots.
  5. Under Networking (or Management, disks, networking, SSH keys > Networking in older layouts), open the network interface and choose Edit.
  6. Make sure IP forwarding is set to Off, then finish the other settings and choose Create.
  7. Check it: the new VM's details show IP forwarding off.

Task 2Prevent it with the organization policy compute.vmCanIpForward

  1. Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
  2. Search for compute.vmCanIpForward (Restrict VM IP Forwarding) and open it.
  3. Choose Manage policy, select Override parent's policy, choose Add a rule and under Policy values choose Deny all, or Custom and allow only your approved network appliances.
  4. Choose Set policy.
  5. Check it: creating a VM with IP forwarding on is refused except for the allowed appliances.

Task 3Keep it checked with the Security Health Analytics finding IP_FORWARDING_ENABLED

  1. Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
  2. In the query editor, filter on category IP_FORWARDING_ENABLED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and recreate the VM it names unless it is an approved appliance.
  4. Check it: after the next Security Health Analytics scan, no active IP_FORWARDING_ENABLED finding remains.

Evidence

  • VM instances details, showing IP forwarding off except on approved appliances
  • The compute.vmCanIpForward policy
  • Security Command Center, with no active IP_FORWARDING_ENABLED finding

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.