CIS Google Cloud Platform Foundation Benchmark v1.2.0/Networking/34 of 83
3.7Ensure that RDP access is restricted from the Internet
Control family: Networking
Control description
GCP `Firewall Rules` are specific to a `VPC Network`. Each rule either `allows` or `denies` traffic when its conditions are met. Its conditions allow users to specify the type of traffic, such as ports and protocols, and the source or destination of the traffic, including IP addresses, subnets, and instances.
Firewall rules are defined at the VPC network level and are specific to the network in which they are defined. The rules themselves cannot be shared among networks. Firewall rules only support IPv4 traffic. When specifying a source for an ingress rule or a destination for an egress rule by address, an `IPv4` address or `IPv4 block in CIDR` notation can be used. Generic `(0.0.0.0/0)` incoming traffic from the Internet to a VPC or VM instance using `RDP` on `Port 3389` can be avoided.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A firewall rule that lets anyone on the internet reach port 3389 exposes every matching VM to RDP password guessing and exploits. Administrators reach VMs through Identity-Aware Proxy TCP forwarding instead, which only needs Google's IAP range to be allowed, and every RDP rule with a source of 0.0.0.0/0 is removed or narrowed.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree how administrators reach Windows VMs (Identity-Aware Proxy, or named address ranges) and record any exception with its approver.
- Add "no RDP from anywhere" to the firewall change review.
Evidence
- The remote access standard and the exception register
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks narrow the open RDP rules in VPC network, move administrators to IAP TCP forwarding, and watch with Security Command Center.
Task 1Narrow each firewall rule that opens RDP to the internet
- Sign in to the Google Cloud console at console.cloud.google.com and open VPC network > Firewall.
- Sort or filter the list for ingress rules that allow tcp:3389, and choose a rule whose source includes 0.0.0.0/0.
- Choose Edit.
- Under Source IPv4 ranges, delete 0.0.0.0/0.
- Add only the ranges that need to connect: 35.235.240.0/20 for IAP TCP forwarding, plus any fixed administrator ranges.
- Keep only the protocols and ports the instance needs, and choose Save.
- Check it: the rule list shows no ingress rule allowing tcp:3389 from 0.0.0.0/0.
Task 2Connect administrators through IAP instead
- Open Security > Identity-Aware Proxy and choose the SSH and TCP resources tab.
- Select the VMs administrators need, and in the info panel choose Add principal.
- Add the administrators' group with the role IAP-secured Tunnel User, and choose Save.
- Check it: an administrator connects with the console's IAP Desktop or tunnel button for the VM, while a direct connection from the internet fails.
Task 3Keep it checked with the Security Health Analytics finding OPEN_RDP_PORT
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category OPEN_RDP_PORT with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and narrow the rule it names.
- Check it: after the next Security Health Analytics scan, no active OPEN_RDP_PORT finding remains.
Evidence
- VPC network > Firewall, with no rule allowing tcp:3389 from 0.0.0.0/0
- The IAP SSH and TCP resources permissions, showing who may tunnel to the VMs
- Security Command Center, with no active OPEN_RDP_PORT 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.