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 is associated with one or more Azure Policy definitions. These policies might help you assess compliance with the control. However, there often isn't 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 that 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 can 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 | Establish network segmentation boundaries | Subnets should be associated with a Network Security Group | 3.0.0 |
| Network Security | NS-3 | Deploy firewall at the edge of enterprise network | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| Network Security | NS-5 | Deploy DDOS protection | Azure DDoS Protection Standard should be enabled | 3.0.0 |
| Network Security | NS-6 | Deploy web application firewall | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| Network Security | NS-6 | Deploy web application firewall | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 |
| Incident Response | IR-4 | Detection and analysis - investigate an incident | 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 | [Preview]: 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 | [Preview]: 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) |
|---|---|---|---|---|
| 2 Security Center | CIS Microsoft Azure Foundations Benchmark recommendation 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 |
| 6 Networking | CIS Microsoft Azure Foundations Benchmark recommendation 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) |
|---|---|---|---|---|
| 6 Networking | CIS Microsoft Azure Foundations Benchmark recommendation 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.003 | Verify and control/limit connections to and use of external information systems. | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| Access Control | AC.2.013 | Monitor and control remote access sessions. | Network Watcher should be enabled | 3.0.0 |
| Access Control | AC.2.016 | Control the flow of CUI in accordance with approved authorizations. | [Preview]: 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. | [Preview]: 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. | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.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 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. | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| Incident Response | IR.2.093 | Detect and report events. | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.0.0 |
| 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. | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.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 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). | [Preview]: 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). | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.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 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. | [Preview]: 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. | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.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 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 | [Preview]: 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 | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| System And Communications Protection | SC-5 | Denial Of Service Protection | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.0.0 |
| System And Information Integrity | SI-4 | Information System Monitoring | [Preview]: 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.
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) |
|---|---|---|---|---|
| 08 Network Protection | 0805.01m1Organizational.12-01.m | 0805.01m1Organizational.12-01.m 01.04 Network Access Control | Gateway subnets should not be configured with a network security group | 1.0.0 |
| 08 Network Protection | 0805.01m1Organizational.12-01.m | 0805.01m1Organizational.12-01.m 01.04 Network Access Control | Subnets should be associated with a Network Security Group | 3.0.0 |
| 08 Network Protection | 0805.01m1Organizational.12-01.m | 0805.01m1Organizational.12-01.m 01.04 Network Access Control | Virtual machines should be connected to an approved virtual network | 1.0.0 |
| 08 Network Protection | 0806.01m2Organizational.12356-01.m | 0806.01m2Organizational.12356-01.m 01.04 Network Access Control | Gateway subnets should not be configured with a network security group | 1.0.0 |
| 08 Network Protection | 0806.01m2Organizational.12356-01.m | 0806.01m2Organizational.12356-01.m 01.04 Network Access Control | Subnets should be associated with a Network Security Group | 3.0.0 |
| 08 Network Protection | 0806.01m2Organizational.12356-01.m | 0806.01m2Organizational.12356-01.m 01.04 Network Access Control | Virtual machines should be connected to an approved virtual network | 1.0.0 |
| 08 Network Protection | 0809.01n2Organizational.1234-01.n | 0809.01n2Organizational.1234-01.n 01.04 Network Access Control | Subnets should be associated with a Network Security Group | 3.0.0 |
| 08 Network Protection | 0809.01n2Organizational.1234-01.n | 0809.01n2Organizational.1234-01.n 01.04 Network Access Control | Virtual machines should be connected to an approved virtual network | 1.0.0 |
| 08 Network Protection | 0810.01n2Organizational.5-01.n | 0810.01n2Organizational.5-01.n 01.04 Network Access Control | Subnets should be associated with a Network Security Group | 3.0.0 |
| 08 Network Protection | 0810.01n2Organizational.5-01.n | 0810.01n2Organizational.5-01.n 01.04 Network Access Control | Virtual machines should be connected to an approved virtual network | 1.0.0 |
| 08 Network Protection | 0811.01n2Organizational.6-01.n | 0811.01n2Organizational.6-01.n 01.04 Network Access Control | Subnets should be associated with a Network Security Group | 3.0.0 |
| 08 Network Protection | 0811.01n2Organizational.6-01.n | 0811.01n2Organizational.6-01.n 01.04 Network Access Control | Virtual machines should be connected to an approved virtual network | 1.0.0 |
| 08 Network Protection | 0812.01n2Organizational.8-01.n | 0812.01n2Organizational.8-01.n 01.04 Network Access Control | Subnets should be associated with a Network Security Group | 3.0.0 |
| 08 Network Protection | 0812.01n2Organizational.8-01.n | 0812.01n2Organizational.8-01.n 01.04 Network Access Control | Virtual machines should be connected to an approved virtual network | 1.0.0 |
| 08 Network Protection | 0814.01n1Organizational.12-01.n | 0814.01n1Organizational.12-01.n 01.04 Network Access Control | Subnets should be associated with a Network Security Group | 3.0.0 |
| 08 Network Protection | 0814.01n1Organizational.12-01.n | 0814.01n1Organizational.12-01.n 01.04 Network Access Control | Virtual machines should be connected to an approved virtual network | 1.0.0 |
| 08 Network Protection | 0837.09.n2Organizational.2-09.n | 0837.09.n2Organizational.2-09.n 09.06 Network Security Management | Network Watcher should be enabled | 3.0.0 |
| 08 Network Protection | 0860.09m1Organizational.9-09.m | 0860.09m1Organizational.9-09.m 09.06 Network Security Management | Deploy Diagnostic Settings for Network Security Groups | 2.0.1 |
| 08 Network Protection | 0886.09n2Organizational.4-09.n | 0886.09n2Organizational.4-09.n 09.06 Network Security Management | Network Watcher should be enabled | 3.0.0 |
| 08 Network Protection | 0888.09n2Organizational.6-09.n | 0888.09n2Organizational.6-09.n 09.06 Network Security Management | Network Watcher should be enabled | 3.0.0 |
| 08 Network Protection | 0894.01m2Organizational.7-01.m | 0894.01m2Organizational.7-01.m 01.04 Network Access Control | Deploy network watcher when virtual networks are created | 1.0.0 |
| 08 Network Protection | 0894.01m2Organizational.7-01.m | 0894.01m2Organizational.7-01.m 01.04 Network Access Control | Gateway subnets should not be configured with a network security group | 1.0.0 |
| 08 Network Protection | 0894.01m2Organizational.7-01.m | 0894.01m2Organizational.7-01.m 01.04 Network Access Control | Subnets should be associated with a Network Security Group | 3.0.0 |
| 08 Network Protection | 0894.01m2Organizational.7-01.m | 0894.01m2Organizational.7-01.m 01.04 Network Access Control | Virtual machines should be connected to an approved virtual network | 1.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 | 2.0.0 |
| 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-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 | [Preview]: 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 | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| System and Communications Protection | SC-5 | Denial-of-service Protection | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 |
| System and Communications Protection | SC-7 | Boundary Protection | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| System and Communications Protection | SC-7 | Boundary Protection | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.0.0 |
| System and Communications Protection | SC-7 (3) | Access Points | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| System and Communications Protection | SC-7 (3) | Access Points | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| 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 | 2.0.0 |
| System and Information Integrity | SI-4 | System Monitoring | [Preview]: 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 |
NZ ISM Restricted v3.5
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NZ ISM Restricted v3.5. For more information about this compliance standard, see NZ ISM Restricted v3.5.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Gateway security | NZISM Security Benchmark GS-3 | 19.1.12 Configuration of Gateways | Subnets should be associated with a Network Security Group | 3.0.0 |
| Network security | NZISM Security Benchmark 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 | NZISM Security Benchmark NS-8 | 18.4.8 IDS/IPSs on gateways | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| Network security | NZISM Security Benchmark NS-8 | 18.4.8 IDS/IPSs on gateways | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 |
| Network security | NZISM Security Benchmark NS-8 | 18.4.8 IDS/IPSs on gateways | Web Application Firewall (WAF) should use the specified mode for Application Gateway | 1.0.0 |
| Network security | NZISM Security Benchmark NS-8 | 18.4.8 IDS/IPSs on gateways | Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service | 1.0.0 |
Reserve Bank of India - IT Framework for NBFC
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Reserve Bank of India - IT Framework for NBFC. For more information about this compliance standard, see Reserve Bank of India - IT Framework for NBFC.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| IT Governance | RBI IT Framework 1.1 | IT Governance-1.1 | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| Information and Cyber Security | RBI IT Framework 3.1.g | Trails-3.1 | Flow logs should be configured for every network security group | 1.1.0 |
| Information and Cyber Security | RBI IT Framework 3.1.g | Trails-3.1 | Flow logs should be enabled for every network security group | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.g | Trails-3.1 | Network Watcher flow logs should have traffic analytics enabled | 1.0.0 |
| IS Audit | RBI IT Framework 5 | Policy for Information System Audit (IS Audit)-5 | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview |
| IS Audit | RBI IT Framework 5 | Policy for Information System Audit (IS Audit)-5 | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| IS Audit | RBI IT Framework 5 | Policy for Information System Audit (IS Audit)-5 | Flow logs should be configured for every network security group | 1.1.0 |
| IS Audit | RBI IT Framework 5 | Policy for Information System Audit (IS Audit)-5 | Flow logs should be enabled for every network security group | 1.0.0 |
| IS Audit | RBI IT Framework 5 | Policy for Information System Audit (IS Audit)-5 | Subnets should be associated with a Network Security Group | 3.0.0 |
| IS Audit | RBI IT Framework 5 | Policy for Information System Audit (IS Audit)-5 | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 |
| IS Audit | RBI IT Framework 5 | Policy for Information System Audit (IS Audit)-5 | Web Application Firewall (WAF) should use the specified mode for Application Gateway | 1.0.0 |
| IS Audit | RBI IT Framework 5 | Policy for Information System Audit (IS Audit)-5 | Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service | 1.0.0 |
Reserve Bank of India IT Framework for Banks v2016
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RBI ITF Banks v2016. For more information about this compliance standard, see RBI ITF Banks v2016 (PDF).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Management And Security | Network Inventory-4.2 | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview | |
| Network Management And Security | Perimeter Protection And Detection-4.10 | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.3 | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview | |
| Network Management And Security | Anomaly Detection-4.7 | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview | |
| Network Management And Security | Network Device Configuration Management-4.3 | [Preview]: All Internet traffic should be routed via your deployed Azure Firewall | 3.0.0-preview | |
| Incident Response & Management | Recovery From Cyber - Incidents-19.6b | Azure DDoS Protection Standard should be enabled | 3.0.0 | |
| Forensics | Forensics-22.1 | Azure DDoS Protection Standard should be enabled | 3.0.0 | |
| Network Management And Security | Network Device Configuration Management-4.3 | Azure firewall policy should enable TLS inspection within application rules | 1.0.0 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 | |
| Network Management And Security | Anomaly Detection-4.7 | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 | |
| Network Management And Security | Perimeter Protection And Detection-4.10 | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 | |
| Network Management And Security | Network Device Configuration Management-4.3 | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Flow logs should be configured for every network security group | 1.1.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Flow logs should be configured for every network security group | 1.1.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Flow logs should be configured for every network security group | 1.1.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Flow logs should be enabled for every network security group | 1.0.0 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.1 | Flow logs should be enabled for every network security group | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Flow logs should be enabled for every network security group | 1.0.0 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.1 | Flow logs should be enabled for every network security group | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Flow logs should be enabled for every network security group | 1.0.0 | |
| Network Management And Security | Network Inventory-4.2 | Network Watcher flow logs should have traffic analytics enabled | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Network Watcher flow logs should have traffic analytics enabled | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Network Watcher flow logs should have traffic analytics enabled | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Network Watcher flow logs should have traffic analytics enabled | 1.0.0 | |
| Network Management And Security | Security Operation Centre-4.9 | Network Watcher should be enabled | 3.0.0 | |
| Secure Mail And Messaging Systems | Secure Mail And Messaging Systems-10.1 | Subnets should be associated with a Network Security Group | 3.0.0 | |
| Network Management And Security | Network Device Configuration Management-4.3 | Subnets should be associated with a Network Security Group | 3.0.0 | |
| Network Management And Security | Anomaly Detection-4.7 | Subnets should be associated with a Network Security Group | 3.0.0 | |
| Secure Mail And Messaging Systems | Secure Mail And Messaging Systems-10.2 | Subnets should be associated with a Network Security Group | 3.0.0 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Subnets should be associated with a Network Security Group | 3.0.0 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.3 | Subnets should be associated with a Network Security Group | 3.0.0 | |
| Network Management And Security | Perimeter Protection And Detection-4.10 | Subnets should be associated with a Network Security Group | 3.0.0 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 | |
| Network Management And Security | Network Device Configuration Management-4.3 | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 | |
| Network Management And Security | Perimeter Protection And Detection-4.10 | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 | |
| Network Management And Security | Anomaly Detection-4.7 | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | Web Application Firewall (WAF) should enable all firewall rules for Application Gateway | 1.0.1 | |
| Network Management And Security | Network Device Configuration Management-4.3 | Web Application Firewall (WAF) should enable all firewall rules for Application Gateway | 1.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | Web Application Firewall (WAF) should enable all firewall rules for Application Gateway | 1.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | Web Application Firewall (WAF) should use the specified mode for Application Gateway | 1.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.7 | Web Application Firewall (WAF) should use the specified mode for Application Gateway | 1.0.0 |
RMIT Malaysia
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RMIT Malaysia. For more information about this compliance standard, see RMIT Malaysia.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Azure VPN gateways should not use 'basic' SKU | 1.0.0 |
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Flow logs should be configured for every network security group | 1.1.0 |
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Flow logs should be enabled for every network security group | 1.0.0 |
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Subnets should be associated with a Network Security Group | 3.0.0 |
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Virtual machines should be connected to an approved virtual network | 1.0.0 |
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Virtual networks should use specified virtual network gateway | 1.0.0 |
| Network Resilience | RMiT 10.35 | Network Resilience - 10.35 | Network Watcher should be enabled | 3.0.0 |
| Network Resilience | RMiT 10.39 | Network Resilience - 10.39 | A custom IPsec/IKE policy must be applied to all Azure virtual network gateway connections | 1.0.0 |
| Distributed Denial of Service (DDoS) | RMiT 11.13 | Distributed Denial of Service (DDoS) - 11.13 | Azure Web Application Firewall should be enabled for Azure Front Door entry-points | 1.0.2 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Azure DDoS Protection Standard should be enabled | 3.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Azure DDoS Protection Standard should be enabled | 3.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.5 | Control Measures on Cybersecurity - Appendix 5.5 | A custom IPsec/IKE policy must be applied to all Azure virtual network gateway connections | 1.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.6 | Control Measures on Cybersecurity - Appendix 5.6 | Web Application Firewall (WAF) should be enabled for Application Gateway | 2.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.6 | Control Measures on Cybersecurity - Appendix 5.6 | Web Application Firewall (WAF) should use the specified mode for Application Gateway | 1.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.6 | Control Measures on Cybersecurity - Appendix 5.6 | Web Application Firewall (WAF) should use the specified mode for Azure Front Door Service | 1.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.7 | Control Measures on Cybersecurity - Appendix 5.7 | Azure DDoS Protection Standard should be enabled | 3.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.7 | Control Measures on Cybersecurity - Appendix 5.7 | Flow logs should be configured for every network security group | 1.1.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.7 | Control Measures on Cybersecurity - Appendix 5.7 | Flow logs should be enabled for every network security group | 1.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.7 | Control Measures on Cybersecurity - Appendix 5.7 | Subnets should be associated with a Network Security Group | 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
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
Feedback
Submit and view feedback for