4.6 Ensure that IP forwarding is not enabled on Instances

Information

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.

Rationale:

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. To enable this source and destination IP check, disable the canIpForward field, which allows an instance to send and receive packets with non-matching destination or source IPs.

Impact:

Deleting instance(s) acting as routers/packet forwarders may break the network connectivity.

Solution

You only edit the canIpForward setting at instance creation time. Therefore, you need to delete the instance and create a new one where canIpForward is set to false.
From Console:

Go to the VM Instances page by visiting: https://pantheon.corp.google.com/compute/instances.

Select the VM Instance you want to remediate.

Click the Delete button.

On the 'VM Instances' page, click 'CREATE INSTANCE'.

Create a new instance with the desired configuration. By default, the instance is configured to not allow IP forwarding.

From Command Line:

Delete the instance:

gcloud compute instances delete INSTANCE_NAME

Create a new instance to replace it, with IP forwarding set to Off

gcloud compute instances create

Default Value:

By default, instances are not configured to allow IP forwarding.

See Also

https://workbench.cisecurity.org/files/3316