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

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

4.9Ensure that Compute instances do not have public IP addresses

Control family: Virtual Machines

Control description

Compute instances should not be configured to have external IP addresses.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

A VM with an external IP address can be reached from the internet whenever a firewall rule allows it, and it can send data straight out. Most VMs don't need one: they can sit behind a load balancer, reach the internet through Cloud NAT, and be administered through IAP.

Before you start

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

  • List the VMs that genuinely need an external address (for example a public endpoint not behind a load balancer) and approve them by name.
  • Agree how other VMs reach the internet (Cloud NAT) and how administrators reach them (IAP).

Evidence

  • The approved list of VMs with external addresses

On Google Cloud the tasks remove external addresses from VMs in Compute Engine, give them outbound access through Cloud NAT, restrict external IPs with an organization policy, and watch with Security Command Center.

Task 1Remove the external IP address from a VM

  1. Sign in to the Google Cloud console at console.cloud.google.com and open Compute Engine > VM instances.
  2. Choose the VM and select Edit.
  3. For each entry under Network interfaces, choose Edit and set External IPv4 address to None.
  4. Choose Done, then Save.
  5. If the VM needs outbound internet access, open Network services > Cloud NAT, choose Create Cloud NAT gateway and pick the VM's network and region.
  6. Check it: the VM instances list shows no external IP for the VM, and it can still reach what it needs.

Task 2Prevent it with the organization policy compute.vmExternalIpAccess

  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.vmExternalIpAccess (Define allowed external IPs for VM instances) 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 approved VMs.
  4. Choose Set policy.
  5. Check it: creating a VM with an external IP is refused unless it is on the allowed list.

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

  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 PUBLIC_IP_ADDRESS with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and remove the external address from the VM it names.
  4. Check it: after the next Security Health Analytics scan, no active PUBLIC_IP_ADDRESS finding remains.

Evidence

  • The VM instances list, showing no external IPs except approved ones
  • The compute.vmExternalIpAccess policy
  • Security Command Center, with no active PUBLIC_IP_ADDRESS 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.