Compliancemanzill.com
CIS Amazon Web Services Foundations Benchmark v1.2.0

CIS Amazon Web Services Foundations Benchmark v1.2.0/Networking/47 of 49

4.2Ensure no security groups allow ingress from 0.0.0.0/0 to port 3389

Control family: Networking

Control description

Security groups provide stateful filtering of ingress/egress network traffic to AWS resources. It is recommended that no security group allows unrestricted ingress access to port `3389` .

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Remote Desktop open to the world is one of the most attacked services on the internet. Windows instances are reached through Fleet Manager or Session Manager, or through a bastion that only known address ranges can reach, so no security group needs to accept RDP from everywhere.

Before you start

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

  • Agree how administrators reach Windows instances (Fleet Manager, or a bastion reachable only from named address ranges), and record any exception with its approver.
  • Add "no RDP from anywhere" to the network change review checklist.

Evidence

  • The remote access standard and the exception register

On AWS the tasks find security groups that open port 3389 to everyone with the AWS Config rule from the benchmark, then close them and give administrators Fleet Manager instead.

Task 1Find security groups that open RDP to the internet

  1. Sign in to the AWS Management Console at console.aws.amazon.com, open AWS Config in each Region you use, and choose Rules > Add rule.
  2. On Specify rule type, search for restricted-common-ports, select it and choose Next.
  3. On Configure rule, under Parameters, make sure one of the blockedPort values is 3389 (the defaults include it), then choose Next.
  4. On Review and create, check the settings and add the rule.
  5. Once it has finished Evaluating..., open the rule and list the noncompliant security groups.

Task 2Close the open rules and use Fleet Manager instead

  1. Open EC2 > Security Groups and select a flagged group.
  2. On the Inbound rules tab, choose Edit inbound rules.
  3. For the rule on port 3389 with source 0.0.0.0/0 or ::/0, choose Delete, or change the source to your administrators' address range.
  4. Choose Save rules.
  5. Give the Windows instances an instance role with the AmazonSSMManagedInstanceCore policy, so administrators can connect from Systems Manager > Fleet Manager > Node actions > Connect with Remote Desktop.
  6. Check it: the restricted-common-ports rule shows the group compliant, and an administrator can still connect.

Evidence

  • The restricted-common-ports rule in each Region, showing all security groups compliant
  • Security Hub CSPM control EC2.14, showing passed

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.