CIS Google Cloud Platform Foundation Benchmark v1.2.0/Networking/37 of 83
3.10Ensure Firewall Rules for instances behind Identity Aware Proxy (IAP) only allow the traffic from Google Cloud Loadbalancer (GCLB) Health Check and Proxy Addresses
Control family: Networking
Control description
Access to VMs should be restricted by firewall rules that allow only IAP traffic by ensuring only connections proxied by the IAP are allowed. To ensure that load balancing works correctly health checks should also be allowed.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
When a service sits behind Identity-Aware Proxy, every request should come through IAP and the load balancer. If the firewall also accepts traffic from anywhere else, users can go around IAP's sign-in and authorization. The firewall rules for those instances allow only Google's load balancer proxy and health check ranges, 130.211.0.0/22 and 35.191.0.0/16, on the serving ports.
Before you start
The same on every cloud, before the steps in the tabs.
- List the services protected by Identity-Aware Proxy and the ports they serve.
- Agree that the only other ingress allowed to them is administration through IAP.
Evidence
- The list of IAP-protected services and their allowed traffic
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks replace broad firewall rules for IAP-protected instances with rules limited to the load balancer ranges, then check nothing else can reach them.
Task 1Limit the firewall to the load balancer ranges
- Sign in to the Google Cloud console at console.cloud.google.com and open VPC network > Firewall.
- Choose Create firewall rule, name it allow-lb-to-iap-backends, and choose the network of the instances.
- Set Targets to Specified target tags and enter the tag the IAP-protected instances use.
- Set Source IPv4 ranges to 130.211.0.0/22 and 35.191.0.0/16, and under Protocols and ports allow only the serving ports, such as tcp:80 and tcp:443.
- Choose Create.
- Delete or narrow any other ingress rule that applies to these instances from 0.0.0.0/0 or other wide ranges.
- Check it: the instances' Network interface details list only the new rule (and IAP's 35.235.240.0/20 for administration) as allowing ingress.
Task 2Check that only IAP can reach the service
- Open Security > Identity-Aware Proxy and confirm the backend service shows IAP turned on.
- From a machine on the internet, try the instance's external IP address directly; the connection should fail or the instance should have no external IP.
- Through the load balancer URL, confirm you are asked to sign in and only permitted users get through.
Evidence
- The firewall rules applying to the IAP-protected instances, limited to 130.211.0.0/22 and 35.191.0.0/16
- The Identity-Aware Proxy page, showing IAP on for the backend service
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.