# Ensure that UDP access from the Internet is evaluated and restricted

- Source: https://support.icompaas.com/support/solutions/articles/62000229926-ensure-that-udp-access-from-the-internet-is-evaluated-and-restricted
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [General](https://support.icompaas.com/support/solutions/62000037933) › [Azure Compliance / Control / Check](https://support.icompaas.com/support/solutions/folders/62000168797)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

UDP access from the Internet should be evaluated and restricted to prevent unnecessary exposure of network resources. Only required UDP ports should be open, and all other UDP traffic from external sources should be blocked using Network Security Groups.

  

Rationale:

UDP is a connectionless protocol and is commonly used in attacks such as reflection, spoofing, amplification, and DDoS. Limiting UDP access from the Internet reduces the attack surface and helps prevent unauthorised or malicious traffic from reaching Azure resources.

  

Impact:

If UDP access from the Internet is not restricted, external hosts may be able to send traffic directly to virtual machines or applications. This can lead to exploitation, service disruption, unauthorized access attempts, or resource exhaustion caused by UDP-based attacks.

  

Default Value:

By default, Azure Network Security Groups deny inbound traffic unless an allow rule is created. However, manually added allow rules can expose UDP ports to the Internet if not reviewed and restricted.

  

Pre-requisites:

-   Permissions to manage Network Security Groups, such as Owner, Contributor, or Network Contributor.
    
-    Knowledge of which applications or services require UDP access.
    
-    Awareness of valid IP ranges or networks that should be allowed if UDP is required.
    

  

Test Plan:

1.  Sign in to the Azure Portal [https://portal.azure.com](https://portal.azure.com/)
    
2.  Navigate to Network Security Groups.
    
3.  Select the NSG associated with the virtual machine or service.
    
4.  Under Settings, open Inbound security rules.
    
5.  Review inbound rules where the Protocol is UDP.
    
6.  Verify there is no UDP rule allowing access from Any or 0.0.0.0/0.
    
7.  If such a rule exists, follow the implementation steps.
    

  

![](https://support.icompaas.com/assets/kb/498286d4bbc7c63f.png)

  

Implementation Steps:

1.  Log in to the Azure Portal at [https://portal.azure.com](https://portal.azure.com/).
    
2.  Navigate to Network Security Groups.
    
3.  Select the NSG associated with the resource.
    
4.  Under Settings, open Inbound security rules.
    

  

                              ![](https://support.icompaas.com/assets/kb/56b18f361bcfbacc.png)

  

5.  Identify any UDP rule allowing access from Any or 0.0.0.0/0.
    
6.  Delete or modify the rule.
    
7.  If UDP is required, allow UDP only from trusted IP addresses and specific destination ports.
    

  

![](https://support.icompaas.com/assets/kb/a9c2ee010b95fa2a.png)

8.  Save the updated rule.
    

  

Backout Plan:

1.  Sign in to the Azure Portal.
    
2.  Navigate to Network Security Groups.
    
3.  Select the NSG where changes were made.
    
4.  Under Settings, open Inbound security rules.
    
5.  Edit the UDP rule and restore the previous approved source configuration if required.
    
6.  Save the changes.
    

  

References:

-   [https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview](https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview)
    
-   [https://learn.microsoft.com/azure/virtual-network/manage-network-security-group](https://learn.microsoft.com/azure/virtual-network/manage-network-security-group)
    
-   [https://learn.microsoft.com/azure/virtual-network/network-security-group-how-it-works](https://learn.microsoft.com/azure/virtual-network/network-security-group-how-it-works)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
