Network security groups should be periodically evaluated for port misconfigurations. Where certain ports and protocols may be exposed to the Internet, they should be evaluated for necessity and restricted wherever they are not explicitly required.


The potential security problem with broadly exposing UDP services over the Internet is that attackers can use DDoS amplification techniques to reflect spoofed UDP traffic from Azure Virtual Machines. The most common types of these attacks use exposed

DNS, NTP, SSDP, SNMP, CLDAP and other UDP-based services as amplification sources for disrupting services of other machines on the Azure Virtual Network or even attack networked devices outside of Azure.


From Azure Portal

1. Open the Networking blade for the specific Virtual machine in Azure portal

2. Verify that the INBOUND PORT RULES does not have a rule for UDP such as

• protocol = UDP,

• 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" : "*" or "[port range containing 53, 123, 161, 389,

1900, or other vulnerable UDP-based services]"

"direction" : "Inbound"

"protocol" : "UDP"

"sourceAddressPrefix" : "*" or "" or "<nw>/0" or "/0" or "internet" or



Where UDP is not explicitly required and narrowly configured for resources attached to the Network Security Group, Internet-level access to your Azure resources should be restricted or eliminated.

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


Site-to-site VPN

Point-to-site VPN

Default Value:

By default, UDP access from internet is not enabled.




3. network-security#ns-1-establish-network-segmentation-boundaries

4. ExpressRoute:

5. Site-to-site VPN:

6. Point-to-site VPN: