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.
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 |
Microsoft Cloud for Sovereignty Baseline Confidential Policies
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 MCfS Sovereignty Baseline Confidential Policies. For more information about this compliance standard, see Microsoft Cloud for Sovereignty Policy portfolio.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| SO.3 - Customer-Managed Keys | SO.3 | Azure products must be configured to use Customer-Managed Keys when possible. | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
Microsoft cloud security benchmark
The Microsoft cloud security benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Microsoft cloud 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 - Microsoft cloud 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 |
NIST SP 800-171 R2
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-171 R2. For more information about this compliance standard, see NIST SP 800-171 R2.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| System and Communications Protection | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
| Media Protection | 3.8.9 | Protect the confidentiality of backup CUI at storage locations. | Azure Backup should be enabled for Virtual Machines | 3.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) |
|---|---|---|---|---|
| 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 |
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 |
NL BIO Cloud Theme
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 NL BIO Cloud Theme. For more information about this compliance standard, see Baseline Information Security Government Cybersecurity - Digital Government (digitaleoverheid.nl).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| U.03.1 Business Continuity Services - Redundancy | U.03.1 | The agreed continuity is guaranteed by sufficiently logical or physically multiple system functions. | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| U.03.2 Business Continuity Services - Continuity requirements | U.03.2 | The continuity requirements for cloud services agreed with the CSC are ensured by the system architecture. | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| U.05.2 Data protection - Cryptographic measures | U.05.2 | Data stored in the cloud service shall be protected to the latest state of the art. | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
| U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | [Preview]: Azure Recovery Services vaults should use customer-managed keys for encrypting backup data | 1.0.0-preview |
| U.17.1 Multi-tenant architecture - Encrypted | U.17.1 | CSC data on transport and at rest is encrypted. | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
Reserve Bank of India - IT Framework for NBFC
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Reserve Bank of India - IT Framework for NBFC. For more information about this compliance standard, see Reserve Bank of India - IT Framework for NBFC.
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 |
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 | 10.30 | Datacenter Operations - 10.30 | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Cyber Risk Management | 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.2.0 |
SWIFT CSP-CSCF v2021
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 SWIFT CSP-CSCF v2021. For more information about this compliance standard, see SWIFT CSP CSCF v2021.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Reduce Attack Surface and Vulnerabilities | 2.5A | External Transmission Data Protection | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Detect Anomalous Activity to Systems or Transaction Records | 6.4 | Logging and Monitoring | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
SWIFT CSP-CSCF v2022
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 SWIFT CSP-CSCF v2022. For more information about this compliance standard, see SWIFT CSP CSCF v2022.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| 2. Reduce Attack Surface and Vulnerabilities | 2.5A | External Transmission Data Protection | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| 6. Detect Anomalous Activity to Systems or Transaction Records | 6.4 | Record security events and detect anomalous actions and operations within the local SWIFT environment. | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
System and Organization Controls (SOC) 2
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 System and Organization Controls (SOC) 2. For more information about this compliance standard, see System and Organization Controls (SOC) 2.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Additional Criteria For Availability | A1.2 | Environmental protections, software, data back-up processes, and recovery infrastructure | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
| Additional Criteria For Processing Integrity | PI1.5 | Store inputs and outputs completely, accurately, and timely | Azure Backup should be enabled for Virtual Machines | 3.0.0 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for