Edit

Secure your Azure Backup deployment

Azure Backup provides centralized, cloud-based data protection for Azure virtual machines, databases, file shares, and on-premises workloads. It stores recovery data in Recovery Services vaults and Backup vaults. Because backups are often the last line of defense against ransomware, accidental deletion, and destructive attacks, you must harden the backup service so that recovery data stays confidential, tamper-resistant, and recoverable.

This article provides security recommendations to help protect your Azure Backup deployment.

The security recommendations in this article implement Zero Trust principles: "Verify explicitly", "Use least privilege access", and "Assume breach". For comprehensive Zero Trust guidance, see the Zero Trust Guidance Center.

Service-specific security

Azure Backup stores vaulted backup data in a Microsoft-managed subscription and tenant, separate from the production environment where the source data resides. This separation contributes to the Logically air-gapped vault outcome, but it doesn't replace controls over identities that can manage the vault. For this outcome, MUA is required; soft delete and encryption are on by default, and immutability is optional. Protect vaulted data from premature deletion by using either always-on soft delete or locked immutability, where supported.

  • Enable multiuser authorization (MUA) with Resource Guard: Require separate Resource Guard authorization before critical operations such as disabling soft delete, stopping backups with data deletion, or reducing retention can proceed. For more information, see Multiuser authorization using Resource Guard.
    • Create the Resource Guard in a separate subscription or tenant: Ensure that no single backup administrator has both vault permissions and the Resource Guard permissions needed to authorize destructive operations. For more information, see Multiuser authorization using Resource Guard.
  • Use always-on soft delete or locked immutability for deletion protection: Soft delete keeps deleted backup data recoverable for its configured retention period, which ranges from 14 to 180 days; it doesn't provide indefinite retention. Locked immutability blocks destructive operations for the configured retention or immutability duration and can't be reversed. Support varies by vault, workload, and region. For more information, see secure-by-default soft delete and immutable vaults.

Network security

Restrict how backup data transfer and management operations reach your vaults so that traffic stays off the public internet.

  • Use private endpoints for supported Recovery Services vault workloads: Route backup and restore traffic for SQL Server and SAP HANA in Azure VMs, MARS agent backups, DPM, and supported file recovery through private endpoints, and deny public network access on the vault when private endpoint DNS is configured. For more information, see Private endpoints for Azure Backup.
  • Secure hybrid backups from the MARS agent, MABS, and DPM: Harden on-premises backups by keeping the agent current, using security PIN validation for critical operations, and protecting the MARS encryption passphrase. For more information, see Security features to protect hybrid backups.
  • Enforce TLS 1.2 or later for backup communication: Configure Windows Server and the MARS agent to use TLS 1.2 or later so that backup data in transit uses strong encryption. For more information, see Transport Layer Security in Azure Backup.

Identity and access management

Grant each backup operator only the permissions their role requires, and protect the credentials needed to restore backups.

Data protection

Control the encryption of backup data at rest so that it meets your key-management and defense-in-depth requirements.

  • Configure customer-managed keys before protecting items in new Recovery Services vaults: Use your own keys in Azure Key Vault for supported Recovery Services vault workloads when you need control over the encryption key lifecycle beyond the default Microsoft-managed keys. For more information, see Encrypt backup data by using customer-managed keys.
  • Enable infrastructure encryption for a second layer of encryption at rest: Add infrastructure encryption at vault creation when you configure customer-managed keys so that backup data is double-encrypted at the storage infrastructure level. For more information, see Encryption of data in Azure Backup.

Logging and monitoring

Monitor the health of your protection estate and detect suspicious backup activity early.

Compliance and governance

Enforce and audit a consistent backup security configuration across your subscriptions.

  • Enforce backup security controls with Azure Policy: Apply the built-in Azure Policy definitions for Azure Backup to audit or require configurations such as soft delete, private endpoints, MUA, and vault immutability across your estate. For more information, see Azure Policy built-in definitions for Azure Backup.
  • Apply resource locks to Recovery Services vaults and Backup vaults: Add a delete lock to vaults and their resource groups so that no one can accidentally or maliciously remove vaults that protect critical workloads. For more information, see Lock your resources to protect your infrastructure.

Backup and recovery

Business continuity and disaster recovery (DR) planning helps you maintain service through regional outages and other disruptions. Cyber recovery essentials adds preparation for cyber incidents: identify supported recovery destinations, test restore procedures, and review results against your organization's recovery objectives. Cross-subscription restore and cross-tenant restore can provide alternative destinations for supported workloads; check each feature's limitations before relying on it.

  • Configure geo-redundant storage for vaults: Set vault storage redundancy to geo-redundant storage (GRS) so that backup data is replicated to the Azure paired region and survives a regional outage. For more information, see Set storage redundancy.
  • Enable Cross Region Restore: Turn on Cross Region Restore (CRR) so that you can restore backup data from the secondary region on demand for drills, audits, or outages, without waiting for Microsoft to declare a disaster. For more information, see Set Cross Region Restore.
  • Prepare for recovery across subscriptions or tenants: Use cross-subscription restore for supported Azure VM scenarios in another subscription in the same tenant. Cross-tenant restore is in preview and supports only documented workloads and regions. Regional redundancy and restore support DR planning, but don't by themselves establish cyber recovery readiness.