Security Control V2: Backup and Recovery

Note

The most up-to-date Azure Security Benchmark is available here.

Backup and Recovery covers controls to ensure that data and configuration backups at the different service tiers are performed, validated, and protected.

To see the applicable built-in Azure Policy, see Details of the Azure Security Benchmark Regulatory Compliance built-in initiative: Backup and Recovery

BR-1: Ensure regular automated backups

Azure ID CIS Controls v7.1 ID(s) NIST SP 800-53 r4 ID(s)
BR-1 10.1 CP-2, CP4, CP-6, CP-9

Ensure you are backing up systems and data to maintain business continuity after an unexpected event. This should be defined by any objectives for Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

Enable Azure Backup and configure the backup source (such as Azure VMs, SQL Server, HANA databases, or File Shares), as well as the desired frequency and retention period.

For a higher level of protection, you can enable the geo-redundant storage option to replicate backup data to a secondary region and recover using cross region restore.

Responsibility: Customer

Customer Security Stakeholders (Learn more):

BR-2: Encrypt backup data

Azure ID CIS Controls v7.1 ID(s) NIST SP 800-53 r4 ID(s)
BR-2 10.2 CP-9

Ensure that your backups are protected against attacks. This should include encryption of the backups to protect against loss of confidentiality.

For on-premises backups using Azure Backup, encryption-at-rest is provided using the passphrase you provide. For regular Azure service backups, backup data is automatically encrypted using Azure platform-managed keys. You can choose to encrypt the backups using customer managed key. In this case, ensure this customer-managed key in the key vault is also in the backup scope.

Use Azure role-based access control in Azure Backup, Azure Key Vault, or other resources to protect backups and customer managed keys. Additionally, you can enable advanced security features to require MFA before backups can be altered or deleted.

Responsibility: Customer

Customer Security Stakeholders (Learn more):

BR-3: Validate all backups including customer-managed keys

Azure ID CIS Controls v7.1 ID(s) NIST SP 800-53 r4 ID(s)
BR-3 10.3 CP-4, CP-9

Periodically perform data restoration of your backup. Ensure that you can restore backed-up customer-managed keys.

Responsibility: Customer

Customer Security Stakeholders (Learn more):

BR-4: Mitigate risk of lost keys

Azure ID CIS Controls v7.1 ID(s) NIST SP 800-53 r4 ID(s)
BR-4 10.4 CP-9

Ensure that you have measures in place to prevent and recover from loss of keys. Enable soft delete and purge protection in Azure Key Vault to protect keys against accidental or malicious deletion.

Responsibility: Customer

Customer Security Stakeholders (Learn more):