Azure Policy Regulatory Compliance controls for Azure Monitor
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 Monitor. 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 System Monitoring - Event logging and auditing | 582 | Events to be logged - 582 | Audit diagnostic setting for selected resource types | 2.0.1 |
| Guidelines for System Monitoring - Event logging and auditing | 1537 | Events to be logged - 1537 | Audit diagnostic setting for selected resource types | 2.0.1 |
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) |
|---|---|---|---|---|
| Data Protection | DP-8 | Ensure security of key and certificate repository | Resource logs in Key Vault should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | App Service apps should have resource logs enabled | 2.0.1 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Event Hub should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Key Vault should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Search services should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Service Bus should be enabled | 5.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) |
|---|---|---|---|---|
| Logging and Monitoring | 2.2 | Configure central security log management | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 |
| Logging and Monitoring | 2.2 | Configure central security log management | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | App Service apps should have resource logs enabled | 2.0.1 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Audit diagnostic setting for selected resource types | 2.0.1 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Event Hub should be enabled | 5.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Key Vault should be enabled | 5.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Search services should be enabled | 5.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Service Bus should be enabled | 5.0.0 |
| Data Protection | 4.9 | Log and alert on changes to critical Azure resources | Azure Monitor should collect activity logs from all regions | 2.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) |
|---|---|---|---|---|
| Audit and Accountability | AU-5 | Response to Audit Processing Failures | Audit diagnostic setting for selected resource types | 2.0.1 |
| Audit and Accountability | AU-12 | Audit Generation | Audit diagnostic setting for selected resource types | 2.0.1 |
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) |
|---|---|---|---|---|
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.1 | Ensure that a Log Profile exists | Azure subscriptions should have a log profile for Activity Log | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.2 | Ensure that Activity Log Retention is set 365 days or greater | Activity log should be retained for at least one year | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.3 | Ensure audit profile captures all the activities | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.4 | Ensure the log profile captures activity logs for all regions including global | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.6 | Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.7 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Azure Key Vault Managed HSM should be enabled | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.7 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Key Vault should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.1 | Ensure that Activity Log Alert exists for Create Policy Assignment | An activity log alert should exist for specific Policy operations | 3.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.2 | Ensure that Activity Log Alert exists for Create or Update Network Security Group | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.3 | Ensure that Activity Log Alert exists for Delete Network Security Group | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.4 | Ensure that Activity Log Alert exists for Create or Update Network Security Group Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.5 | Ensure that activity log alert exists for the Delete Network Security Group Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.6 | Ensure that Activity Log Alert exists for Create or Update Security Solution | An activity log alert should exist for specific Security operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.7 | Ensure that Activity Log Alert exists for Delete Security Solution | An activity log alert should exist for specific Security operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.8 | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.8 | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.9 | Ensure that Activity Log Alert exists for Update Security Policy | An activity log alert should exist for specific Security operations | 1.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) |
|---|---|---|---|---|
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.4 | Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.5 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Key Vault should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.1 | Ensure that Activity Log Alert exists for Create Policy Assignment | An activity log alert should exist for specific Policy operations | 3.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.2 | Ensure that Activity Log Alert exists for Delete Policy Assignment | An activity log alert should exist for specific Policy operations | 3.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.3 | Ensure that Activity Log Alert exists for Create or Update Network Security Group | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.4 | Ensure that Activity Log Alert exists for Delete Network Security Group | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.5 | Ensure that Activity Log Alert exists for Create or Update Network Security Group Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.6 | Ensure that activity log alert exists for the Delete Network Security Group Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.7 | Ensure that Activity Log Alert exists for Create or Update Security Solution | An activity log alert should exist for specific Security operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.8 | Ensure that Activity Log Alert exists for Delete Security Solution | An activity log alert should exist for specific Security operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.9 | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.9 | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | App Service apps should have resource logs enabled | 2.0.1 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Batch accounts should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Event Hub should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in IoT Hub should be enabled | 3.0.1 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Key Vault should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Logic Apps should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Search services should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Service Bus should be enabled | 5.0.0 |
CIS Microsoft Azure Foundations Benchmark 1.4.0
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for CIS v1.4.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) |
|---|---|---|---|---|
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.4 | Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.5 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Key Vault should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.1 | Ensure that Activity Log Alert exists for Create Policy Assignment | An activity log alert should exist for specific Policy operations | 3.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.2 | Ensure that Activity Log Alert exists for Delete Policy Assignment | An activity log alert should exist for specific Policy operations | 3.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.3 | Ensure that Activity Log Alert exists for Create or Update Network Security Group | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.4 | Ensure that Activity Log Alert exists for Delete Network Security Group | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.5 | Ensure that Activity Log Alert exists for Create or Update Network Security Group | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.6 | Ensure that activity log alert exists for the Delete Network Security Group Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.7 | Ensure that Activity Log Alert exists for Create or Update Security Solution | An activity log alert should exist for specific Security operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.8 | Ensure that Activity Log Alert exists for Delete Security Solution | An activity log alert should exist for specific Security operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.9 | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.2.9 | Ensure that Activity Log Alert exists for Create or Update or Delete SQL Server Firewall Rule | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | App Service apps should have resource logs enabled | 2.0.1 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Batch accounts should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Event Hub should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in IoT Hub should be enabled | 3.0.1 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Key Vault should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Logic Apps should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Search services should be enabled | 5.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Service Bus should be enabled | 5.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.3.018 | Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.018 | Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.018 | Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.018 | Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.018 | Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.021 | Authorize remote execution of privileged commands and remote access to security-relevant information. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.021 | Authorize remote execution of privileged commands and remote access to security-relevant information. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.021 | Authorize remote execution of privileged commands and remote access to security-relevant information. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.021 | Authorize remote execution of privileged commands and remote access to security-relevant information. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.021 | Authorize remote execution of privileged commands and remote access to security-relevant information. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Access Control | AC.3.021 | Authorize remote execution of privileged commands and remote access to security-relevant information. | An activity log alert should exist for specific Security operations | 1.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | An activity log alert should exist for specific Policy operations | 3.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | An activity log alert should exist for specific Security operations | 1.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | Audit diagnostic setting for selected resource types | 2.0.1 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| Audit and Accountability | AU.2.041 | Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. | Azure subscriptions should have a log profile for Activity Log | 1.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | Activity log should be retained for at least one year | 1.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | An activity log alert should exist for specific Policy operations | 3.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | An activity log alert should exist for specific Security operations | 1.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | Audit diagnostic setting for selected resource types | 2.0.1 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| Audit and Accountability | AU.2.042 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. | Azure subscriptions should have a log profile for Activity Log | 1.0.0 |
| Audit and Accountability | AU.3.046 | Alert in the event of an audit logging process failure. | Audit diagnostic setting for selected resource types | 2.0.1 |
| Audit and Accountability | AU.3.048 | Collect audit information (e.g., logs) into one or more central repositories. | App Service apps should have resource logs enabled | 2.0.1 |
| Audit and Accountability | AU.3.048 | Collect audit information (e.g., logs) into one or more central repositories. | Audit diagnostic setting for selected resource types | 2.0.1 |
| Audit and Accountability | AU.3.048 | Collect audit information (e.g., logs) into one or more central repositories. | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit and Accountability | AU.3.049 | Protect audit information and audit logging tools from unauthorized access, modification, and deletion. | An activity log alert should exist for specific Policy operations | 3.0.0 |
| Audit and Accountability | AU.3.049 | Protect audit information and audit logging tools from unauthorized access, modification, and deletion. | Audit diagnostic setting for selected resource types | 2.0.1 |
| Security Assessment | CA.2.158 | Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. | An activity log alert should exist for specific Security operations | 1.0.0 |
| Security Assessment | CA.3.161 | Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. | An activity log alert should exist for specific Security operations | 1.0.0 |
| Configuration Management | CM.2.061 | Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. | An activity log alert should exist for specific Policy operations | 3.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | An activity log alert should exist for specific Policy operations | 3.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | An activity log alert should exist for specific Security operations | 1.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| Configuration Management | CM.2.065 | Track, review, approve or disapprove, and log changes to organizational systems. | Azure subscriptions should have a log profile for Activity Log | 1.0.0 |
| Incident Response | IR.2.093 | Detect and report events. | An activity log alert should exist for specific Security operations | 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. | An activity log alert should exist for specific Administrative operations | 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. | An activity log alert should exist for specific Administrative operations | 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. | An activity log alert should exist for specific Administrative operations | 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. | An activity log alert should exist for specific Administrative operations | 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. | An activity log alert should exist for specific Administrative operations | 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. | An activity log alert should exist for specific Policy operations | 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. | An activity log alert should exist for specific Security operations | 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. | Azure Monitor should collect activity logs from all regions | 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. | Azure subscriptions should have a log profile for Activity Log | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | Activity log should be retained for at least one year | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | An activity log alert should exist for specific Policy operations | 3.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | An activity log alert should exist for specific Security operations | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| System and Information Integrity | SI.2.217 | Identify unauthorized use of organizational systems. | Azure subscriptions should have a log profile for Activity Log | 1.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) |
|---|---|---|---|---|
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | App Service apps should have resource logs enabled | 2.0.1 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Search services should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Service Bus should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | App Service apps should have resource logs enabled | 2.0.1 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Search services should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Service Bus should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | App Service apps should have resource logs enabled | 2.0.1 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Search services should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Service Bus should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | App Service apps should have resource logs enabled | 2.0.1 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Search services should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Service Bus should be enabled | 5.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) |
|---|---|---|---|---|
| Audit And Accountability | AU-12 | Audit Generation | App Service apps should have resource logs enabled | 2.0.1 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Search services should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Service Bus should be enabled | 5.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) |
|---|---|---|---|---|
| 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 |
| 11 Access Control | 1120.09ab3System.9-09.ab | 1120.09ab3System.9-09.ab 09.10 Monitoring | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| 12 Audit Logging & Monitoring | 1202.09aa1System.1-09.aa | 1202.09aa1System.1-09.aa 09.10 Monitoring | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1203.09aa1System.2-09.aa | 1203.09aa1System.2-09.aa 09.10 Monitoring | Resource logs in Logic Apps should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1204.09aa1System.3-09.aa | 1204.09aa1System.3-09.aa 09.10 Monitoring | Resource logs in IoT Hub should be enabled | 3.0.1 |
| 12 Audit Logging & Monitoring | 1205.09aa2System.1-09.aa | 1205.09aa2System.1-09.aa 09.10 Monitoring | Resource logs in Batch accounts should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1207.09aa2System.4-09.aa | 1207.09aa2System.4-09.aa 09.10 Monitoring | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1207.09aa2System.4-09.aa | 1207.09aa2System.4-09.aa 09.10 Monitoring | Resource logs in Event Hub should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1208.09aa3System.1-09.aa | 1208.09aa3System.1-09.aa 09.10 Monitoring | Resource logs in Search services should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1208.09aa3System.1-09.aa | 1208.09aa3System.1-09.aa 09.10 Monitoring | Resource logs in Service Bus should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1209.09aa3System.2-09.aa | 1209.09aa3System.2-09.aa 09.10 Monitoring | App Service apps should have resource logs enabled | 2.0.1 |
| 12 Audit Logging & Monitoring | 1210.09aa3System.3-09.aa | 1210.09aa3System.3-09.aa 09.10 Monitoring | Audit diagnostic setting for selected resource types | 2.0.1 |
| 12 Audit Logging & Monitoring | 1210.09aa3System.3-09.aa | 1210.09aa3System.3-09.aa 09.10 Monitoring | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1211.09aa3System.4-09.aa | 1211.09aa3System.4-09.aa 09.10 Monitoring | Resource logs in Azure Key Vault Managed HSM should be enabled | 1.0.0 |
| 12 Audit Logging & Monitoring | 1211.09aa3System.4-09.aa | 1211.09aa3System.4-09.aa 09.10 Monitoring | Resource logs in Key Vault should be enabled | 5.0.0 |
| 12 Audit Logging & Monitoring | 1212.09ab1System.1-09.ab | 1212.09ab1System.1-09.ab 09.10 Monitoring | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 |
| 12 Audit Logging & Monitoring | 1214.09ab2System.3456-09.ab | 1214.09ab2System.3456-09.ab 09.10 Monitoring | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| 12 Audit Logging & Monitoring | 1219.09ab3System.10-09.ab | 1219.09ab3System.10-09.ab 09.10 Monitoring | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 |
| 12 Audit Logging & Monitoring | 1270.09ad1System.12-09.ad | 1270.09ad1System.12-09.ad 09.10 Monitoring | An activity log alert should exist for specific Administrative operations | 1.0.0 |
| 12 Audit Logging & Monitoring | 1271.09ad1System.1-09.ad | 1271.09ad1System.1-09.ad 09.10 Monitoring | An activity log alert should exist for specific Administrative operations | 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) |
|---|---|---|---|---|
| Awareness and Training | 9.3.3.11 | Audit Generation (AU-12) | Audit diagnostic setting for selected resource types | 2.0.1 |
| Awareness and Training | 9.3.3.5 | Response to Audit Processing Failures (AU-5) | Audit diagnostic setting for selected resource types | 2.0.1 |
ISO 27001:2013
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - ISO 27001:2013. For more information about this compliance standard, see ISO 27001:2013.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Operations Security | 12.4.1 | Event Logging | Audit diagnostic setting for selected resource types | 2.0.1 |
| Operations Security | 12.4.3 | Administrator and operator logs | Audit diagnostic setting for selected resource types | 2.0.1 |
| Operations Security | 12.4.4 | Clock Synchronization | Audit diagnostic setting for selected resource types | 2.0.1 |
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) |
|---|---|---|---|---|
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | App Service apps should have resource logs enabled | 2.0.1 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Event Hub should be enabled | 5.0.0 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Key Vault should be enabled | 5.0.0 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Search services should be enabled | 5.0.0 |
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Service Bus should be enabled | 5.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) |
|---|---|---|---|---|
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | App Service apps should have resource logs enabled | 2.0.1 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Search services should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Service Bus should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | App Service apps should have resource logs enabled | 2.0.1 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Search services should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Service Bus should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | App Service apps should have resource logs enabled | 2.0.1 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Search services should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Service Bus should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | App Service apps should have resource logs enabled | 2.0.1 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Event Hub should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Search services should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Service Bus should be enabled | 5.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) |
|---|---|---|---|---|
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | App Service apps should have resource logs enabled | 2.0.1 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Azure Kubernetes Service should be enabled | 1.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Batch accounts should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Data Lake Analytics should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Event Hub should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Key Vault should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Logic Apps should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Search services should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Service Bus should be enabled | 5.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-19 | 16.6.12 Event log protection | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
PCI DSS 3.2.1
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see PCI DSS 3.2.1. For more information about this compliance standard, see PCI DSS 3.2.1.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Requirement 1 | PCI DSS v3.2.1 1.3.4 | PCI DSS requirement 1.3.4 | Audit diagnostic setting for selected resource types | 2.0.1 |
| Requirement 10 | PCI DSS v3.2.1 10.5.4 | PCI DSS requirement 10.5.4 | Audit diagnostic setting for selected resource types | 2.0.1 |
PCI v3.2.1:2018
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for PCI v3.2.1:2018. For more information about this compliance standard, see PCI v3.2.1 2018.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Requirement 1 | PCI DSS v3.2.1 1.3.4 | PCI DSS requirement 1.3.4 | Audit diagnostic setting for selected resource types | 2.0.1 |
| Requirement 10 | PCI DSS v3.2.1 10.5.4 | PCI DSS requirement 10.5.4 | Audit diagnostic setting for selected resource types | 2.0.1 |
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.
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) |
|---|---|---|---|---|
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | App Service apps should have resource logs enabled | 2.0.1 | |
| Audit Log Settings | Audit Log Settings-17.1 | App Service apps should have resource logs enabled | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | App Service apps should have resource logs enabled | 2.0.1 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Application Insights components should block log ingestion and querying from public networks | 1.1.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Application Insights components should block log ingestion and querying from public networks | 1.1.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Application Insights components should block non-Azure Active Directory based ingestion. | 1.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Application Insights components should block non-Azure Active Directory based ingestion. | 1.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Application Insights components with Private Link enabled should use Bring Your Own Storage accounts for profiler and debugger. | 1.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Application Insights components with Private Link enabled should use Bring Your Own Storage accounts for profiler and debugger. | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.2 | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.2 | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.2 | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Azure Monitor Logs for Application Insights should be linked to a Log Analytics workspace | 1.1.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Azure Monitor Logs for Application Insights should be linked to a Log Analytics workspace | 1.1.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Azure Monitor should collect activity logs from all regions | 2.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Azure Monitor should collect activity logs from all regions | 2.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Azure Monitor should collect activity logs from all regions | 2.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Azure Monitor should collect activity logs from all regions | 2.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 | Azure Monitor should collect activity logs from all regions | 2.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Azure Monitor should collect activity logs from all regions | 2.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.2 | Azure subscriptions should have a log profile for Activity Log | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.2 | Azure subscriptions should have a log profile for Activity Log | 1.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.2 | Azure subscriptions should have a log profile for Activity Log | 1.0.0 | |
| Audit Log Settings | Audit Log Settings-17.1 | Resource logs in Azure Data Lake Store should be enabled | 5.0.0 | |
| Audit Log Settings | Audit Log Settings-17.1 | Resource logs in Azure Stream Analytics should be enabled | 5.0.0 | |
| Audit Log Settings | Audit Log Settings-17.1 | Resource logs in Data Lake Analytics should be enabled | 5.0.0 | |
| Audit Log Settings | Audit Log Settings-17.1 | Resource logs in Event Hub should be enabled | 5.0.0 | |
| Audit Log Settings | Audit Log Settings-17.1 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Resource logs in Logic Apps should be enabled | 5.0.0 | |
| Audit Log Settings | Audit Log Settings-17.1 | Resource logs in Logic Apps should be enabled | 5.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Resource logs in Logic Apps should be enabled | 5.0.0 | |
| Audit Log Settings | Audit Log Settings-17.1 | Resource logs in Service Bus should be enabled | 5.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) |
|---|---|---|---|---|
| Cloud Services | RMiT 10.53 | Cloud Services - 10.53 | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Activity log should be retained for at least one year | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | App Service apps should have resource logs enabled | 2.0.1 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Audit diagnostic setting for selected resource types | 2.0.1 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Azure Monitor log profile should collect logs for categories 'write,' 'delete,' and 'action' | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Azure Monitor Logs for Application Insights should be linked to a Log Analytics workspace | 1.1.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Azure Monitor should collect activity logs from all regions | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Azure subscriptions should have a log profile for Activity Log | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy - Configure diagnostic settings for SQL Databases to Log Analytics workspace | 4.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Batch Account to Event Hub | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Batch Account to Log Analytics workspace | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Data Lake Analytics to Event Hub | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Data Lake Analytics to Log Analytics workspace | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Data Lake Storage Gen1 to Event Hub | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Data Lake Storage Gen1 to Log Analytics workspace | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Event Hub to Event Hub | 2.1.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Event Hub to Log Analytics workspace | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Key Vault to Log Analytics workspace | 3.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Logic Apps to Event Hub | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Logic Apps to Log Analytics workspace | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Search Services to Event Hub | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Search Services to Log Analytics workspace | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Service Bus to Event Hub | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Service Bus to Log Analytics workspace | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Stream Analytics to Event Hub | 2.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Stream Analytics to Log Analytics workspace | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Resource logs in Azure Key Vault Managed HSM should be enabled | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Resource logs in Key Vault should be enabled | 5.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Resource logs in Event Hub should be enabled | 5.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Resource logs in Event Hub should be enabled | 5.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) |
|---|---|---|---|---|
| Audit information for users | 13 | Audit information for users | Audit diagnostic setting for selected resource types | 2.0.1 |
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