Azure Policy Regulatory Compliance controls for Azure Batch

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 Batch. You can assign the built-ins for a security control individually to help make your Azure resources compliant with the specific standard.

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

Important

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

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)
Logging and Threat Detection LT-4 Enable logging for Azure resources Resource logs in Batch accounts 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.3 Enable audit logging for Azure resources Resource logs in Batch accounts should be enabled 5.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)
Logging and Monitoring 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

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 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 Batch accounts 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 (1) System-wide / Time-correlated Audit Trail Resource logs in Batch accounts should be enabled 5.0.0
System and Communications Protection SC-12 Cryptographic Key Establishment and Management Azure Batch account should use customer-managed keys to encrypt data 1.0.1

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 Resource logs in Batch accounts should be enabled 5.0.0
System and Communications Protection SC-12 Cryptographic Key Establishment and Management Azure Batch account should use customer-managed keys to encrypt data 1.0.1

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)
Audit Logging 1205.09aa2System.1 - 09.aa Logs of messages sent and received are maintained including the date, time, origin and destination of the message, but not its contents. Resource logs in Batch accounts should be enabled 5.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)
Infrastructure INF-9 10.8.35 Security Architecture Private endpoint connections on Batch accounts should be enabled 1.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

NIST SP 800-53 Rev. 4

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

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
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 (5) Integration / Scanning and Monitoring Capabilities Resource logs in Batch accounts 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 (1) System-wide / Time-correlated Audit Trail Resource logs in Batch accounts should be enabled 5.0.0
System and Communications Protection SC-12 Cryptographic Key Establishment and Management Azure Batch account should use customer-managed keys to encrypt data 1.0.1

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 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 Batch accounts 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 (1) System-wide and Time-correlated Audit Trail Resource logs in Batch accounts should be enabled 5.0.0
System and Communications Protection SC-12 Cryptographic Key Establishment and Management Azure Batch account should use customer-managed keys to encrypt data 1.0.1

Next steps