Azure Policy Regulatory Compliance controls for Azure Virtual Network

Regulatory Compliance in Azure Policy provides Microsoft created and managed initiative definitions, known as built-ins, for the compliance domains and security controls related to different compliance standards. This page lists the compliance domains and security controls for Azure Virtual Network. You can assign the built-ins for a security control individually to help make your Azure resources compliant with the specific standard.

The title of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Policy Version column to view the source on the Azure Policy GitHub repo.

Important

Each control below is associated with one or more Azure Policy definitions. These policies may help you assess compliance with the control; however, there often is not a one-to-one or complete match between a control and one or more policies. As such, Compliant in Azure Policy refers only to the policies themselves; this doesn't ensure you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. The associations between controls and Azure Policy Regulatory Compliance definitions for these compliance standards may change over time.

Australian Government ISM PROTECTED

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Australian Government ISM PROTECTED. For more information about this compliance standard, see Australian Government ISM PROTECTED.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Guidelines for Networking - Service continuity for online services 1431 Denial of service strategies - 1431 Azure DDoS Protection Standard should be enabled 3.0.0

Azure Security Benchmark

The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure Security Benchmark, see the Azure Security Benchmark mapping files.

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Azure Security Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Network Security NS-1 Implement security for internal traffic All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Network Security NS-1 Implement security for internal traffic Subnets should be associated with a Network Security Group 3.0.0
Network Security NS-4 Protect applications and services from external network attacks All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Network Security NS-4 Protect applications and services from external network attacks Azure DDoS Protection Standard should be enabled 3.0.0
Network Security NS-4 Protect applications and services from external network attacks Subnets should be associated with a Network Security Group 3.0.0
Network Security NS-4 Protect applications and services from external network attacks Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
Network Security NS-4 Protect applications and services from external network attacks Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
Network Security NS-5 Deploy intrusion detection/intrusion prevention systems (IDS/IPS) All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Logging and Threat Detection LT-3 Enable logging for Azure network activities Network Watcher should be enabled 3.0.0

Azure Security Benchmark v1

The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure Security Benchmark, see the Azure Security Benchmark mapping files.

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Azure Security Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Network Security 1.1 Protect resources using Network Security Groups or Azure Firewall on your Virtual Network All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Network Security 1.1 Protect resources using Network Security Groups or Azure Firewall on your Virtual Network Subnets should be associated with a Network Security Group 3.0.0
Network Security 1.1 Protect resources using Network Security Groups or Azure Firewall on your Virtual Network Virtual machines should be connected to an approved virtual network 1.0.0
Network Security 1.1 Protect resources using Network Security Groups or Azure Firewall on your Virtual Network Virtual networks should use specified virtual network gateway 1.0.0
Network Security 1.2 Monitor and log the configuration and traffic of Vnets, Subnets, and NICs Network Watcher should be enabled 3.0.0
Network Security 1.4 Deny communications with known malicious IP addresses All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Network Security 1.4 Deny communications with known malicious IP addresses Azure DDoS Protection Standard should be enabled 3.0.0
Network Security 1.5 Record network packets and flow logs Network Watcher should be enabled 3.0.0

Canada Federal PBMM

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Canada Federal PBMM. For more information about this compliance standard, see Canada Federal PBMM.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
System and Communications Protection SC-5 Denial of Service Protection Azure DDoS Protection Standard should be enabled 3.0.0

CIS Microsoft Azure Foundations Benchmark 1.1.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CIS Microsoft Azure Foundations Benchmark 1.1.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Security Center 2.9 Ensure ASC Default policy setting "Enable Next Generation Firewall(NGFW) Monitoring" is not "Disabled" Subnets should be associated with a Network Security Group 3.0.0
Networking 6.1 Ensure that RDP access is restricted from the internet RDP access from the Internet should be blocked 2.0.0
Networking 6.2 Ensure that SSH access is restricted from the internet SSH access from the Internet should be blocked 2.0.0
Networking 6.5 Ensure that Network Watcher is 'Enabled' Network Watcher should be enabled 3.0.0

CIS Microsoft Azure Foundations Benchmark 1.3.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CIS Microsoft Azure Foundations Benchmark 1.3.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Networking 6.1 Ensure that RDP access is restricted from the internet RDP access from the Internet should be blocked 2.0.0
Networking 6.2 Ensure that SSH access is restricted from the internet SSH access from the Internet should be blocked 2.0.0
Networking 6.5 Ensure that Network Watcher is 'Enabled' Network Watcher should be enabled 3.0.0

CMMC Level 3

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CMMC Level 3. For more information about this compliance standard, see Cybersecurity Maturity Model Certification (CMMC).

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC.1.001 Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). RDP access from the Internet should be blocked 2.0.0
Access Control AC.1.001 Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). SSH access from the Internet should be blocked 2.0.0
Access Control AC.1.002 Limit information system access to the types of transactions and functions that authorized users are permitted to execute. RDP access from the Internet should be blocked 2.0.0
Access Control AC.1.002 Limit information system access to the types of transactions and functions that authorized users are permitted to execute. SSH access from the Internet should be blocked 2.0.0
Access Control AC.1.003 Verify and control/limit connections to and use of external information systems. All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Access Control AC.1.003 Verify and control/limit connections to and use of external information systems. RDP access from the Internet should be blocked 2.0.0
Access Control AC.1.003 Verify and control/limit connections to and use of external information systems. SSH access from the Internet should be blocked 2.0.0
Access Control AC.2.013 Monitor and control remote access sessions. Network Watcher should be enabled 3.0.0
Access Control AC.2.015 Route remote access via managed access control points. RDP access from the Internet should be blocked 2.0.0
Access Control AC.2.016 Control the flow of CUI in accordance with approved authorizations. All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Access Control AC.2.016 Control the flow of CUI in accordance with approved authorizations. RDP access from the Internet should be blocked 2.0.0
Configuration Management CM.2.064 Establish and enforce security configuration settings for information technology products employed in organizational systems. All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Configuration Management CM.2.064 Establish and enforce security configuration settings for information technology products employed in organizational systems. Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
Configuration Management CM.2.064 Establish and enforce security configuration settings for information technology products employed in organizational systems. Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
Configuration Management CM.2.064 Establish and enforce security configuration settings for information technology products employed in organizational systems. Web Application Firewall (WAF) should use the specified mode for Application Gateway 1.0.0
Configuration Management CM.2.064 Establish and enforce security configuration settings for information technology products employed in organizational systems. Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service 1.0.0
Configuration Management CM.3.068 Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. Subnets should be associated with a Network Security Group 3.0.0
Incident Response IR.2.093 Detect and report events. All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Incident Response IR.2.093 Detect and report events. Flow logs should be configured for every network security group 1.1.0
Incident Response IR.2.093 Detect and report events. Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
Incident Response IR.2.093 Detect and report events. Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
Incident Response IR.2.093 Detect and report events. Web Application Firewall (WAF) should use the specified mode for Application Gateway 1.0.0
Incident Response IR.2.093 Detect and report events. Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service 1.0.0
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Flow logs should be configured for every network security group 1.1.0
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Network Watcher should be enabled 3.0.0
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Web Application Firewall (WAF) should use the specified mode for Application Gateway 1.0.0
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service 1.0.0
System and Communications Protection SC.1.176 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC.3.180 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Flow logs should be configured for every network security group 1.1.0
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Network Watcher should be enabled 3.0.0
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Web Application Firewall (WAF) should use the specified mode for Application Gateway 1.0.0
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service 1.0.0
System and Information Integrity SI.2.216 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Information Integrity SI.2.216 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. Flow logs should be configured for every network security group 1.1.0
System and Information Integrity SI.2.216 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. Network Watcher should be enabled 3.0.0
System and Information Integrity SI.2.216 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Information Integrity SI.2.216 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Information Integrity SI.2.216 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. Web Application Firewall (WAF) should use the specified mode for Application Gateway 1.0.0
System and Information Integrity SI.2.216 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service 1.0.0
System and Information Integrity SI.2.217 Identify unauthorized use of organizational systems. Network Watcher should be enabled 3.0.0

FedRAMP High

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP High. For more information about this compliance standard, see FedRAMP High.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Access Control AC-4 Information Flow Enforcement Subnets should be associated with a Network Security Group 3.0.0
Audit and Accountability AU-6 Audit Review, Analysis, and Reporting Network Watcher should be enabled 3.0.0
Audit and Accountability AU-6 (4) Central Review and Analysis Network Watcher should be enabled 3.0.0
Audit and Accountability AU-6 (5) Integration / Scanning and Monitoring Capabilities Network Watcher should be enabled 3.0.0
Audit and Accountability AU-12 Audit Generation Network Watcher should be enabled 3.0.0
Audit and Accountability AU-12 (1) System-wide / Time-correlated Audit Trail Network Watcher should be enabled 3.0.0
System and Communications Protection SC-5 Denial of Service Protection Azure DDoS Protection Standard should be enabled 3.0.0
System and Communications Protection SC-5 Denial of Service Protection Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-5 Denial of Service Protection Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC-7 Boundary Protection All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC-7 Boundary Protection Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC-7 Boundary Protection Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-7 Boundary Protection Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC-7 (3) Access Points All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC-7 (3) Access Points Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC-7 (3) Access Points Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-7 (3) Access Points Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Information Integrity SI-4 Information System Monitoring All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Information Integrity SI-4 Information System Monitoring Network Watcher should be enabled 3.0.0

FedRAMP Moderate

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP Moderate. For more information about this compliance standard, see FedRAMP Moderate.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Access Control AC-4 Information Flow Enforcement Subnets should be associated with a Network Security Group 3.0.0
Audit and Accountability AU-6 Audit Review, Analysis, and Reporting Network Watcher should be enabled 3.0.0
Audit and Accountability AU-12 Audit Generation Network Watcher should be enabled 3.0.0
System and Communications Protection SC-5 Denial of Service Protection Azure DDoS Protection Standard should be enabled 3.0.0
System and Communications Protection SC-5 Denial of Service Protection Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-5 Denial of Service Protection Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC-7 Boundary Protection All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC-7 Boundary Protection Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC-7 Boundary Protection Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-7 Boundary Protection Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC-7 (3) Access Points All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC-7 (3) Access Points Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC-7 (3) Access Points Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-7 (3) Access Points Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Information Integrity SI-4 Information System Monitoring All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Information Integrity SI-4 Information System Monitoring Network Watcher should be enabled 3.0.0

HIPAA HITRUST 9.2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - HIPAA HITRUST 9.2. For more information about this compliance standard, see HIPAA HITRUST 9.2.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Segregation in Networks 0805.01m1Organizational.12 - 01.m The organization's security gateways (e.g. firewalls) enforce security policies and are configured to filter traffic between domains, block unauthorized access, and are used to maintain segregation between internal wired, internal wireless, and external network segments (e.g., the Internet) including DMZs and enforce access control policies for each of the domains. Gateway subnets should not be configured with a network security group 1.0.0
Segregation in Networks 0805.01m1Organizational.12 - 01.m The organization's security gateways (e.g. firewalls) enforce security policies and are configured to filter traffic between domains, block unauthorized access, and are used to maintain segregation between internal wired, internal wireless, and external network segments (e.g., the Internet) including DMZs and enforce access control policies for each of the domains. Subnets should be associated with a Network Security Group 3.0.0
Segregation in Networks 0805.01m1Organizational.12 - 01.m The organization's security gateways (e.g. firewalls) enforce security policies and are configured to filter traffic between domains, block unauthorized access, and are used to maintain segregation between internal wired, internal wireless, and external network segments (e.g., the Internet) including DMZs and enforce access control policies for each of the domains. Virtual machines should be connected to an approved virtual network 1.0.0
Segregation in Networks 0806.01m2Organizational.12356 - 01.m The organizations network is logically and physically segmented with a defined security perimeter and a graduated set of controls, including subnetworks for publicly accessible system components that are logically separated from the internal network, based on organizational requirements; and traffic is controlled based on functionality required and classification of the data/systems based on a risk assessment and their respective security requirements. Gateway subnets should not be configured with a network security group 1.0.0
Segregation in Networks 0806.01m2Organizational.12356 - 01.m The organizations network is logically and physically segmented with a defined security perimeter and a graduated set of controls, including subnetworks for publicly accessible system components that are logically separated from the internal network, based on organizational requirements; and traffic is controlled based on functionality required and classification of the data/systems based on a risk assessment and their respective security requirements. Subnets should be associated with a Network Security Group 3.0.0
Segregation in Networks 0806.01m2Organizational.12356 - 01.m The organizations network is logically and physically segmented with a defined security perimeter and a graduated set of controls, including subnetworks for publicly accessible system components that are logically separated from the internal network, based on organizational requirements; and traffic is controlled based on functionality required and classification of the data/systems based on a risk assessment and their respective security requirements. Virtual machines should be connected to an approved virtual network 1.0.0
Segregation in Networks 0894.01m2Organizational.7 - 01.m Networks are segregated from production-level networks when migrating physical servers, applications or data to virtualized servers. Deploy network watcher when virtual networks are created 1.0.0
Segregation in Networks 0894.01m2Organizational.7 - 01.m Networks are segregated from production-level networks when migrating physical servers, applications or data to virtualized servers. Gateway subnets should not be configured with a network security group 1.0.0
Segregation in Networks 0894.01m2Organizational.7 - 01.m Networks are segregated from production-level networks when migrating physical servers, applications or data to virtualized servers. Subnets should be associated with a Network Security Group 3.0.0
Segregation in Networks 0894.01m2Organizational.7 - 01.m Networks are segregated from production-level networks when migrating physical servers, applications or data to virtualized servers. Virtual machines should be connected to an approved virtual network 1.0.0
Network Connection Control 0809.01n2Organizational.1234 - 01.n Network traffic is controlled in accordance with the organizations access control policy through firewall and other network-related restrictions for each network access point or external telecommunication service's managed interface. Subnets should be associated with a Network Security Group 3.0.0
Network Connection Control 0809.01n2Organizational.1234 - 01.n Network traffic is controlled in accordance with the organizations access control policy through firewall and other network-related restrictions for each network access point or external telecommunication service's managed interface. Virtual machines should be connected to an approved virtual network 1.0.0
Network Connection Control 0810.01n2Organizational.5 - 01.n Transmitted information is secured and, at a minimum, encrypted over open, public networks. Subnets should be associated with a Network Security Group 3.0.0
Network Connection Control 0810.01n2Organizational.5 - 01.n Transmitted information is secured and, at a minimum, encrypted over open, public networks. Virtual machines should be connected to an approved virtual network 1.0.0
Network Connection Control 0811.01n2Organizational.6 - 01.n Exceptions to the traffic flow policy are documented with a supporting mission/business need, duration of the exception, and reviewed at least annually; traffic flow policy exceptions are removed when no longer supported by an explicit mission/business need. Subnets should be associated with a Network Security Group 3.0.0
Network Connection Control 0811.01n2Organizational.6 - 01.n Exceptions to the traffic flow policy are documented with a supporting mission/business need, duration of the exception, and reviewed at least annually; traffic flow policy exceptions are removed when no longer supported by an explicit mission/business need. Virtual machines should be connected to an approved virtual network 1.0.0
Network Connection Control 0812.01n2Organizational.8 - 01.n Remote devices establishing a non-remote connection are not allowed to communicate with external (remote) resources. Subnets should be associated with a Network Security Group 3.0.0
Network Connection Control 0812.01n2Organizational.8 - 01.n Remote devices establishing a non-remote connection are not allowed to communicate with external (remote) resources. Virtual machines should be connected to an approved virtual network 1.0.0
Network Connection Control 0814.01n1Organizational.12 - 01.n The ability of users to connect to the internal network is restricted using a deny-by-default and allow-by-exception policy at managed interfaces according to the access control policy and the requirements of clinical and business applications. Subnets should be associated with a Network Security Group 3.0.0
Network Connection Control 0814.01n1Organizational.12 - 01.n The ability of users to connect to the internal network is restricted using a deny-by-default and allow-by-exception policy at managed interfaces according to the access control policy and the requirements of clinical and business applications. Virtual machines should be connected to an approved virtual network 1.0.0
Network Controls 0860.09m1Organizational.9 - 09.m The organization formally manages equipment on the network, including equipment in user areas. Deploy Diagnostic Settings for Network Security Groups 1.0.0
Security of Network Services 0837.09.n2Organizational.2 - 09.n Formal agreements with external information system providers include specific obligations for security and privacy. Network Watcher should be enabled 3.0.0
Security of Network Services 0886.09n2Organizational.4 - 09.n The organization employs and documents in a formal agreement or other document, either i) allow-all, deny-by-exception, or, ii) deny-all, permit-by-exception (preferred), policy for allowing specific information systems to connect to external information systems. Network Watcher should be enabled 3.0.0
Security of Network Services 0888.09n2Organizational.6 - 09.n The contract with the external/outsourced service provider includes the specification that the service provider is responsible for the protection of covered information shared. Network Watcher should be enabled 3.0.0

IRS 1075 September 2016

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - IRS 1075 September 2016. For more information about this compliance standard, see IRS 1075 September 2016.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
System and Communications Protection 9.3.16.4 Denial of Service Protection (SC-5) Azure DDoS Protection Standard should be enabled 3.0.0

New Zealand ISM Restricted

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - New Zealand ISM Restricted. For more information about this compliance standard, see New Zealand ISM Restricted.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Network security NS-5 18.3.19 Content of a Denial of Service (DoS) response plan Azure DDoS Protection Standard should be enabled 3.0.0
Network security NS-7 18.4.8 IDS/IPSs on gateways Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
Network security NS-7 18.4.8 IDS/IPSs on gateways Web Application Firewall (WAF) should use the specified mode for Application Gateway 1.0.0
Network security NS-7 18.4.8 IDS/IPSs on gateways Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service 1.0.0
Gateway security GS-3 19.1.12 Configuration of Gateways Subnets should be associated with a Network Security Group 3.0.0

NIST SP 800-171 R2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-171 R2. For more information about this compliance standard, see NIST SP 800-171 R2.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
System and Information Integrity 3.14.6 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. Network Watcher should be enabled 3.0.0

NIST SP 800-53 Rev. 4

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 4. For more information about this compliance standard, see NIST SP 800-53 Rev. 4.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Access Control AC-4 Information Flow Enforcement Subnets should be associated with a Network Security Group 3.0.0
Audit and Accountability AU-6 Audit Review, Analysis, and Reporting Network Watcher should be enabled 3.0.0
Audit and Accountability AU-6 (4) Central Review and Analysis Network Watcher should be enabled 3.0.0
Audit and Accountability AU-6 (5) Integration / Scanning and Monitoring Capabilities Network Watcher should be enabled 3.0.0
Audit and Accountability AU-12 Audit Generation Network Watcher should be enabled 3.0.0
Audit and Accountability AU-12 (1) System-wide / Time-correlated Audit Trail Network Watcher should be enabled 3.0.0
System and Communications Protection SC-5 Denial of Service Protection Azure DDoS Protection Standard should be enabled 3.0.0
System and Communications Protection SC-5 Denial of Service Protection Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-5 Denial of Service Protection Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC-7 Boundary Protection All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC-7 Boundary Protection Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC-7 Boundary Protection Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-7 Boundary Protection Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC-7 (3) Access Points All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC-7 (3) Access Points Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC-7 (3) Access Points Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-7 (3) Access Points Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Information Integrity SI-4 Information System Monitoring All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Information Integrity SI-4 Information System Monitoring Network Watcher should be enabled 3.0.0

NIST SP 800-53 Rev. 5

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 5. For more information about this compliance standard, see NIST SP 800-53 Rev. 5.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
Access Control AC-4 Information Flow Enforcement Subnets should be associated with a Network Security Group 3.0.0
Audit and Accountability AU-6 Audit Record Review, Analysis, and Reporting Network Watcher should be enabled 3.0.0
Audit and Accountability AU-6 (4) Central Review and Analysis Network Watcher should be enabled 3.0.0
Audit and Accountability AU-6 (5) Integrated Analysis of Audit Records Network Watcher should be enabled 3.0.0
Audit and Accountability AU-12 Audit Record Generation Network Watcher should be enabled 3.0.0
Audit and Accountability AU-12 (1) System-wide and Time-correlated Audit Trail Network Watcher should be enabled 3.0.0
System and Communications Protection SC-5 Denial-of-service Protection Azure DDoS Protection Standard should be enabled 3.0.0
System and Communications Protection SC-5 Denial-of-service Protection Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-5 Denial-of-service Protection Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC-7 Boundary Protection All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC-7 Boundary Protection Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC-7 Boundary Protection Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-7 Boundary Protection Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Communications Protection SC-7 (3) Access Points All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Communications Protection SC-7 (3) Access Points Subnets should be associated with a Network Security Group 3.0.0
System and Communications Protection SC-7 (3) Access Points Web Application Firewall (WAF) should be enabled for Application Gateway 1.0.1
System and Communications Protection SC-7 (3) Access Points Web Application Firewall (WAF) should be enabled for Azure Front Door Service service 1.0.1
System and Information Integrity SI-4 System Monitoring All Internet traffic should be routed via your deployed Azure Firewall 3.0.0-preview
System and Information Integrity SI-4 System Monitoring Network Watcher should be enabled 3.0.0

UK OFFICIAL and UK NHS

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - UK OFFICIAL and UK NHS. For more information about this compliance standard, see UK OFFICIAL.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Operational security 5.3 Protective Monitoring Azure DDoS Protection Standard should be enabled 3.0.0

Next steps