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 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.
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 | 3.0.0 |
| Backup and Recovery | BR-2 | Protect backup and recovery data | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
Azure Security Benchmark v1
The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure Security Benchmark, see the Azure Security Benchmark mapping files.
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Azure Security Benchmark.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Data Recovery | 9.1 | Ensure regular automated back ups | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Data Recovery | 9.2 | Perform complete system backups and backup any customer managed keys | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
CMMC Level 3
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CMMC Level 3. For more information about this compliance standard, see Cybersecurity Maturity Model Certification (CMMC).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Recovery | RE.2.137 | Regularly perform and test data back-ups. | Azure Backup should be enabled for Virtual Machines | 3.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 | 3.0.0 |
FedRAMP High
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP High. For more information about this compliance standard, see FedRAMP High.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Contingency Planning | CP-9 | Information System Backup | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
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) |
|---|---|---|---|---|
| Contingency Planning | CP-9 | Information System Backup | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
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 | 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 | 3.0.0 |
| 16 Business Continuity & Disaster Recovery | 1620.09l1Organizational.8-09.l | 1620.09l1Organizational.8-09.l 09.05 Information Back-Up | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| 16 Business Continuity & Disaster Recovery | 1625.09l3Organizational.34-09.l | 1625.09l3Organizational.34-09.l 09.05 Information Back-Up | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
NIST SP 800-53 Rev. 5
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 5. For more information about this compliance standard, see NIST SP 800-53 Rev. 5.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Contingency Planning | CP-9 | System Backup | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
Reserve Bank of India - IT Framework for NBFC
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Reserve Bank of India - IT Framework for NBFC. For more information about this compliance standard, see Reserve Bank of India - IT Framework for NBFC.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| IS Audit | RBI IT Framework 5.2 | Coverage-5.2 | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Business Continuity Planning | RBI IT Framework 6 | Business Continuity Planning (BCP) and Disaster Recovery-6 | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6 | Business Continuity Planning (BCP) and Disaster Recovery-6 | [Preview]: Azure Recovery Services vaults should use private link for backup | 2.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6 | Business Continuity Planning (BCP) and Disaster Recovery-6 | [Preview]: Recovery Services vaults should use private link | 1.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6 | Business Continuity Planning (BCP) and Disaster Recovery-6 | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Business Continuity Planning | RBI IT Framework 6.2 | Recovery strategy / Contingency Plan-6.2 | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6.2 | Recovery strategy / Contingency Plan-6.2 | [Preview]: Azure Recovery Services vaults should use private link for backup | 2.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6.2 | Recovery strategy / Contingency Plan-6.2 | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Business Continuity Planning | RBI IT Framework 6.3 | Recovery strategy / Contingency Plan-6.3 | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6.3 | Recovery strategy / Contingency Plan-6.3 | [Preview]: Azure Recovery Services vaults should use private link for backup | 2.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6.3 | Recovery strategy / Contingency Plan-6.3 | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Business Continuity Planning | RBI IT Framework 6.4 | Recovery strategy / Contingency Plan-6.4 | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6.4 | Recovery strategy / Contingency Plan-6.4 | [Preview]: Azure Recovery Services vaults should use private link for backup | 2.0.0-preview |
| Business Continuity Planning | RBI IT Framework 6.4 | Recovery strategy / Contingency Plan-6.4 | [Preview]: Recovery Services vaults should use private link | 1.0.0-preview |
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) |
|---|---|---|---|---|
| Anti-Phishing | Anti-Phishing-14.1 | [Preview]: Azure Recovery Services vaults should use private link for backup | 2.0.0-preview | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.3 | Azure Backup should be enabled for Virtual Machines | 3.0.0 | |
| Incident Response & Management | Recovery From Cyber - Incidents-19.5 | Azure Backup should be enabled for Virtual Machines | 3.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) |
|---|---|---|---|---|
| Datacenter Operations | RMiT 10.30 | Datacenter Operations - 10.30 | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Cyber Risk Management | RMiT 11.4 | Cyber Risk Management - 11.4 | Configure backup on virtual machines without a given tag to an existing recovery services vault in the same location | 9.0.0 |
| Cyber Risk Management | RMiT 11.4 | Cyber Risk Management - 11.4 | Configure backup on virtual machines without a given tag to an existing recovery services vault in the same location | 9.0.0 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
Feedback
Submit and view feedback for