Azure

How to harden security of Azure Backup Vault

Backups Are Your Last Line of Defense

Azure Backup Vault protects your data against ransomware, accidental deletion, and insider threats. But a backup is only useful if an attacker cannot delete or encrypt it. Hardening your Backup Vault means making backups immutable, requiring multi-user authorization for destructive operations, encrypting with customer-managed keys, and restricting network access to the vault itself.

Threat Landscape and Attack Surface

Hardening Azure Backup Vault requires understanding the threat landscape specific to this service. Azure services are attractive targets because they often store, process, or transmit sensitive data and provide control-plane access to cloud infrastructure. Attackers probe for misconfigured services using automated scanners that continuously sweep Azure IP ranges for exposed endpoints, weak authentication, and default configurations.

The attack surface for Azure Backup Vault includes several dimensions. The network perimeter determines who can reach the service endpoints. The identity and access layer controls what authenticated principals can do. The data plane governs how data is protected at rest and in transit. The management plane controls who can modify the service configuration itself. A comprehensive hardening strategy addresses all four dimensions because a weakness in any single layer can be exploited to bypass the controls in other layers.

Microsoft’s shared responsibility model means that while Azure secures the physical infrastructure, network fabric, and hypervisor, you are responsible for configuring the service securely. Default configurations prioritize ease of setup over security. Every Azure service ships with settings that must be tightened for production use, and this guide walks through the critical configurations that should be changed from their defaults.

The MITRE ATT&CK framework for cloud environments provides a structured taxonomy of attack techniques that adversaries use against Azure services. Common techniques relevant to Azure Backup Vault include initial access through exposed credentials or misconfigured endpoints, lateral movement through overly permissive RBAC assignments, and data exfiltration through unmonitored data plane operations. Each hardening control in this guide maps to one or more of these attack techniques.

Compliance and Regulatory Context

Security hardening is not just a technical exercise. It is a compliance requirement for virtually every regulatory framework that applies to cloud workloads. SOC 2 Type II requires evidence of security controls for cloud services. PCI DSS mandates network segmentation and encryption for payment data. HIPAA requires access controls and audit logging for health information. ISO 27001 demands a systematic approach to information security management. FedRAMP requires specific configurations for government workloads.

Azure Policy and Microsoft Defender for Cloud provide built-in compliance assessments against these frameworks. After applying the hardening configurations in this guide, run a compliance scan to verify your security posture against your applicable regulatory standards. Address any remaining findings to achieve and maintain compliance. Export compliance reports on a scheduled basis to satisfy audit requirements and demonstrate continuous adherence.

The Microsoft cloud security benchmark provides a comprehensive set of security controls mapped to common regulatory frameworks. Use this benchmark as a checklist to verify that your hardening effort covers all required areas. Each control includes Azure-specific implementation guidance and links to the relevant Azure service documentation.

Step 1: Enable Enhanced Soft Delete

Soft delete is now enabled by default and cannot be disabled for new vaults. Extend the retention period beyond the default 14 days.

# Extend soft delete retention to 180 days
az backup vault backup-properties set \
  --name vault-prod --resource-group rg-backup \
  --soft-delete-feature-state Enable \
  --soft-delete-duration 180

Soft-deleted backup data can be recovered during the retention period. Even if an attacker deletes backup items, you have 180 days to restore them.

Step 2: Enable Immutable Vaults

# Enable immutability in locked state
az backup vault backup-properties set \
  --name vault-prod --resource-group rg-backup \
  --immutability-state Locked

Warning: Once locked, immutability cannot be reversed. Start with Unlocked state to test, then move to Locked for production. Locked immutability prevents anyone — including subscription owners — from deleting backup data before its scheduled expiry.

Step 3: Configure Multi-User Authorization (MUA)

MUA requires approval from a Resource Guard (hosted in a separate subscription or resource group) before performing destructive operations like disabling soft delete or stopping protection with delete data.

# Create Resource Guard in a security team's resource group
az dataprotection resource-guard create \
  --resource-group rg-security --name backup-resource-guard --location eastus

# Associate Resource Guard with the vault
az backup vault backup-properties set \
  --name vault-prod --resource-group rg-backup \
  --resource-guard-operation-requests "/subscriptions/{sub}/resourceGroups/rg-security/providers/Microsoft.DataProtection/resourceGuards/backup-resource-guard"

The security team controls the Resource Guard. Backup admins cannot bypass it without the security team’s approval, creating true separation of duties.

Step 4: Use Customer-Managed Keys

# Configure CMK encryption
az backup vault encryption update \
  --name vault-prod --resource-group rg-backup \
  --encryption-key-id "https://kv-prod.vault.azure.net/keys/backup-cmk/version" \
  --infrastructure-encryption-state Enabled \
  --mi-system-assigned

Infrastructure encryption (double encryption) adds a second layer using a platform-managed key. Combined with CMK, this provides two independent encryption layers.

Step 5: Configure Private Endpoints

# Create private endpoint for the vault
az network private-endpoint create \
  --name pe-backup --resource-group rg-network \
  --vnet-name vnet-prod --subnet snet-pe \
  --private-connection-resource-id "/subscriptions/{sub}/resourceGroups/rg-backup/providers/Microsoft.RecoveryServices/vaults/vault-prod" \
  --group-id AzureBackup --connection-name backup-conn

# Disable public access
az backup vault backup-properties set \
  --name vault-prod --resource-group rg-backup \
  --public-network-access Disabled

Identity and Access Management Deep Dive

Identity is the primary security perimeter in cloud environments. For Azure Backup Vault, implement a robust identity and access management strategy that follows the principle of least privilege.

Managed Identities: Use system-assigned or user-assigned managed identities for service-to-service authentication. Managed identities eliminate the need for stored credentials (connection strings, API keys, or service principal secrets) that can be leaked, stolen, or forgotten in configuration files. Azure automatically rotates the underlying certificates, removing the operational burden of credential rotation.

Custom RBAC Roles: When built-in roles grant more permissions than required, create custom roles that include only the specific actions needed. For example, if a monitoring service only needs to read metrics and logs from Azure Backup Vault, create a custom role with only the Microsoft.Insights/metrics/read and Microsoft.Insights/logs/read actions rather than assigning the broader Reader or Contributor roles.

Conditional Access: For human administrators accessing Azure Backup Vault through the portal or CLI, enforce Conditional Access policies that require multi-factor authentication, compliant devices, and approved locations. Set session lifetime limits so that administrative sessions expire after a reasonable period, forcing re-authentication.

Just-In-Time Access: Use Azure AD Privileged Identity Management (PIM) to provide time-limited, approval-required elevation for administrative actions. Instead of permanently assigning Contributor or Owner roles, require administrators to activate their role assignment for a specific duration with a business justification. This reduces the window of exposure if an administrator’s account is compromised.

Service Principal Hygiene: If managed identities cannot be used (for example, for external services or CI/CD pipelines), use certificate-based authentication for service principals rather than client secrets. Certificates are harder to accidentally expose than text secrets, and Azure Key Vault can automate their rotation. Set short expiration periods for any client secrets and monitor for secrets that are approaching expiration.

Step 6: Enable Security PIN

The Security PIN is a 6-digit code generated from the Azure portal that is required before performing critical operations:

  • Stopping protection with delete data
  • Changing the backup passphrase
  • Reducing retention period
  • Disabling security features

Navigate to Recovery Services vault > Settings > Properties > Security Settings > Generate Security PIN. The PIN expires after 5 minutes.

Step 7: Configure RBAC with Least Privilege

# Backup Operator — can trigger and manage backups but NOT delete
az role assignment create \
  --assignee backup-team@contoso.com \
  --role "Backup Operator" \
  --scope "/subscriptions/{sub}/resourceGroups/rg-backup/providers/Microsoft.RecoveryServices/vaults/vault-prod"

# Backup Reader — monitoring only
az role assignment create \
  --assignee audit-team@contoso.com \
  --role "Backup Reader" \
  --scope "/subscriptions/{sub}/resourceGroups/rg-backup/providers/Microsoft.RecoveryServices/vaults/vault-prod"

Avoid assigning the Backup Contributor role broadly. This role can delete backup items and stop protection — combine it with MUA for safety.

Step 8: Enable Diagnostic Logging and Alerts

# Enable diagnostics
az monitor diagnostic-settings create \
  --name vault-diag \
  --resource "/subscriptions/{sub}/resourceGroups/rg-backup/providers/Microsoft.RecoveryServices/vaults/vault-prod" \
  --workspace law-prod-id \
  --logs '[
    {"category":"CoreAzureBackup","enabled":true},
    {"category":"AddonAzureBackupAlerts","enabled":true},
    {"category":"AddonAzureBackupJobs","enabled":true},
    {"category":"AddonAzureBackupPolicy","enabled":true}
  ]'

Step 9: Enforce Azure Policy

# Enforce backup on all VMs
az policy assignment create \
  --name enforce-vm-backup \
  --policy "013e242c-8828-4970-87b3-ab247555486d" \
  --scope "/subscriptions/{sub}" \
  --params '{"effect": {"value": "AuditIfNotExists"}}'

Key policies to assign:

  • Azure Backup should be enabled for VMs — audit or enforce
  • Recovery Services vaults should use private link
  • Soft delete should be enabled for Recovery Services Vault
  • Immutability must be enabled for backup vaults

Step 10: Test Restore Regularly

A backup you cannot restore is worthless. Schedule quarterly restore tests:

# List recovery points for a backup item
az backup recoverypoint list \
  --vault-name vault-prod --resource-group rg-backup \
  --container-name "IaasVMContainer;iaasvmcontainerv2;rg-prod;vm-web" \
  --item-name "VM;iaasvmcontainerv2;rg-prod;vm-web" \
  --query "[0].name" -o tsv

# Trigger test restore to alternate location
az backup restore restore-disks \
  --vault-name vault-prod --resource-group rg-backup \
  --container-name "IaasVMContainer;iaasvmcontainerv2;rg-prod;vm-web" \
  --item-name "VM;iaasvmcontainerv2;rg-prod;vm-web" \
  --rp-name "recovery-point-id" \
  --storage-account strestoretest \
  --target-resource-group rg-restore-test

Defense in Depth Strategy

No single security control is sufficient. Apply a defense-in-depth strategy that layers multiple controls so that the failure of any single layer does not expose the service to attack. For Azure Backup Vault, this means combining network isolation, identity verification, encryption, monitoring, and incident response capabilities.

At the network layer, restrict access to only the networks that legitimately need to reach the service. Use Private Endpoints to eliminate public internet exposure entirely. Where public access is required, use IP allowlists, service tags, and Web Application Firewall (WAF) rules to limit the attack surface. Configure network security groups (NSGs) with deny-by-default rules and explicit allow rules only for required traffic flows.

At the identity layer, enforce least-privilege access using Azure RBAC with custom roles when built-in roles are too broad. Use Managed Identities for service-to-service authentication to eliminate stored credentials. Enable Conditional Access policies to require multi-factor authentication and compliant devices for administrative access.

At the data layer, enable encryption at rest using customer-managed keys (CMK) in Azure Key Vault when the default Microsoft-managed keys do not meet your compliance requirements. Enforce TLS 1.2 or higher for data in transit. Enable purge protection on any service that supports soft delete to prevent malicious or accidental data destruction.

At the monitoring layer, enable diagnostic logging and route logs to a centralized Log Analytics workspace. Configure Microsoft Sentinel analytics rules to detect suspicious access patterns, privilege escalation attempts, and data exfiltration indicators. Set up automated response playbooks that can isolate compromised resources without human intervention during off-hours.

Continuous Security Assessment

Security hardening is not a one-time activity. Azure services evolve continuously, introducing new features, deprecating old configurations, and changing default behaviors. Schedule quarterly security reviews to reassess your hardening posture against the latest Microsoft security baselines.

Use Microsoft Defender for Cloud’s Secure Score as a quantitative measure of your security posture. Track your score over time and investigate any score decreases, which may indicate configuration drift or new recommendations from updated security baselines. Set a target Secure Score and hold teams accountable for maintaining it.

Subscribe to Azure update announcements and security advisories to stay informed about changes that affect your security controls. When Microsoft introduces a new security feature or changes a default behavior, assess the impact on your environment and update your hardening configuration accordingly. Automate this assessment where possible using Azure Policy to continuously evaluate your resources against your security standards.

Conduct periodic penetration testing against your Azure environment. Azure’s penetration testing rules of engagement allow testing without prior notification to Microsoft for most services. Engage a qualified security testing firm to assess your Azure Backup Vault deployment using the same techniques that real attackers would employ. The findings from these tests often reveal gaps that automated compliance scans miss.

Hardening Checklist

  1. Soft delete enabled with extended retention (180 days)
  2. Immutable vaults in Locked state
  3. Multi-User Authorization with Resource Guard
  4. Customer-managed keys with infrastructure encryption
  5. Private endpoints with public access disabled
  6. Security PIN for destructive operations
  7. RBAC with least privilege (Backup Operator, not Contributor)
  8. Diagnostic logging and alerting
  9. Azure Policy enforcement
  10. Regular restore testing

Leave a Reply