Azure Policy Regulatory Compliance controls for Azure Backup

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 Backup. 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)
Backup and Recovery BR-1 Ensure regular automated backups Azure Backup should be enabled for Virtual Machines 2.0.0
Backup and Recovery BR-2 Encrypt backup data Azure Backup should be enabled for Virtual Machines 2.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)
Data Recovery 9.1 Ensure regular automated back ups Azure Backup should be enabled for Virtual Machines 2.0.0
Data Recovery 9.2 Perform complete system backups and backup any customer managed keys Azure Backup should be enabled for Virtual Machines 2.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)
Recovery RE.2.137 Regularly perform and test data back-ups. Azure Backup should be enabled for Virtual Machines 2.0.0
Recovery RE.3.139 Regularly perform complete, comprehensive and resilient data backups as organizationally-defined. Azure Backup should be enabled for Virtual Machines 2.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)
Back-up 1620.09l1Organizational.8 - 09.l When the backup service is delivered by the third party, the service level agreement includes the detailed protections to control confidentiality, integrity and availability of the backup information. Azure Backup should be enabled for Virtual Machines 2.0.0
Back-up 1625.09l3Organizational.34 - 09.l Three (3) generations of backups (full plus all related incremental or differential backups) are stored off-site, and both on-site and off-site backups are logged with name, date, time and action. Azure Backup should be enabled for Virtual Machines 2.0.0
Back-up 1699.09l1Organizational.10 - 09.l Workforce members roles and responsibilities in the data backup process are identified and communicated to the workforce; in particular, Bring Your Own Device (BYOD) users are required to perform backups of organizational and/or client data on their devices. Azure Backup should be enabled for Virtual Machines 2.0.0

NIST SP 800-53 R4

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 R4. For more information about this compliance standard, see NIST SP 800-53 R4.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Contingency Planning NIST SP 800-53 Rev. 4 CP-9 Information System Backup Azure Backup should be enabled for Virtual Machines 2.0.0
Contingency Planning NIST SP 800-53 Rev. 4 CP-9 Information System Backup Azure Backup should be enabled for Virtual Machines 2.0.0
Contingency Planning NIST SP 800-53 Rev. 4 CP-9 Information System Backup Azure Backup should be enabled for Virtual Machines 2.0.0
Contingency Planning NIST SP 800-53 Rev. 4 CP-9 Information System Backup Azure Backup should be enabled for Virtual Machines 2.0.0
System and Communications Protection NIST SP 800-53 Rev. 4 SC-12 Cryptographic Key Establishment and Management Azure Recovery Services vaults should use customer-managed keys for encrypting backup data 1.0.0-preview
System and Communications Protection NIST SP 800-53 Rev. 4 SC-12 Cryptographic Key Establishment and Management Azure Recovery Services vaults should use customer-managed keys for encrypting backup data 1.0.0-preview
System and Communications Protection NIST SP 800-53 Rev. 4 SC-12 Cryptographic Key Establishment and Management Azure Recovery Services vaults should use customer-managed keys for encrypting backup data 1.0.0-preview

NIST SP 800-53 R5

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 R5. For more information about this compliance standard, see NIST SP 800-53 R5.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Contingency Planning CP-9 System Backup Azure Backup should be enabled for Virtual Machines 2.0.0
System and Communications Protection SC-12 Cryptographic Key Establishment and Management Azure Recovery Services vaults should use customer-managed keys for encrypting backup data 1.0.0-preview

Next steps