Skip to main content


6.1 Evaluate and restrict Remote Desktop Protocol (RDP) access from the Internet (Automated)

Profile Applicability

• Level 1


Network security groups should be periodically evaluated for port misconfigurations. If a network security group exposes certain ports and protocols to the Internet, evaluate them for necessity and restrict wherever they are not explicitly required.


The potential security problem with using RDP over the Internet is that attackers can use various brute force techniques to gain access to Azure Virtual Machines. Once the attackers gain access, they can use a virtual machine as a launch point for compromising other machines on an Azure Virtual Network or even attack networked devices outside of Azure.


From Azure Portal

  1. For each VM, open the Networking blade
  2. Verify that the INBOUND PORT RULES does not have a rule for RDP such as
    • port = 3389,
    • protocol = TCP,
    • Source = Any OR Internet

From Azure CLI

List Network security groups with corresponding non-default Security rules:

az network nsg list --query [*].[name,securityRules]

Ensure that none of the NSGs have security rule as below

"access" : "Allow"
"destinationPortRange" : "3389" or "*" or "[port range containing 3389]"
"direction" : "Inbound"
"protocol" : "TCP"
"sourceAddressPrefix" : "*" or "" or "<nw>/0" or "/0" or "internet" or "any"


Where RDP is not explicitly required and narrowly configured for resources attached to the Network Security Group, restrict or eliminate Internet-level access to your Azure resources.

For internal access to relevant resources, configure an encrypted network tunnel such as:


Site-to-site VPN

Point-to-site VPN

Express Route
Site-to-Site VPN
Point-to-Site VPN