Study guide
12.3 Implementing Security Controls to Protect Backups
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
12.3 Implementing Security Controls to Protect Backups
Key Takeaways Explain This Topic AI
Soft delete on a Recovery Services or Backup vault retains deleted backup data for 14 days by default, and enhanced soft delete extends that to a configurable 14–180 days.
An immutable vault blocks operations that would shorten retention or delete recovery points, and locking immutability makes the setting irreversible.
Multi-user authorization uses a Resource Guard placed in a separate subscription or tenant so a compromised backup admin cannot approve their own destructive operation.
MARS agent backups add a security PIN requirement for critical operations such as stopping backup with data deletion or changing the passphrase.
Backup Operator can create and restore backups but cannot delete a vault or disable protection with data deletion — that separation is the point of the role.
Last updated: August 2026
The Attack Pattern You Are Defending Against
A competent ransomware operator does not start by encrypting data. They start by deleting the backups , because that removes the victim's only alternative to paying. The sequence is predictable: obtain a privileged Azure identity, open the Recovery Services vault, stop protection with "delete backup data", then encrypt production. Every control below exists to break one step of that chain.
Vault Soft Delete
Soft delete keeps deleted backup data recoverable rather than destroying it immediately.
- Property Value
- Default state Enabled on Recovery Services vaults and Backup vaults
- Basic retention 14 days after deletion, at no cost
- Enhanced soft delete Retention configurable from 14 to 180 days
- Always-on soft delete Opt-in setting that makes soft delete permanently non-disableable for that vault
The critical nuance: with basic soft delete, an attacker with vault privileges can disable soft delete first and then delete the data, defeating the control. Enabling always-on soft delete removes that option permanently — you cannot turn it back off, which is exactly why it is a security control rather than a convenience toggle.
Immutable Vaults
An immutable vault blocks any operation that could reduce the recoverability of existing data:
Reducing a backup policy's retention duration.
Deleting a recovery point or stopping protection with delete data .
Changing a policy in a way that shortens retention.
Operations that increase protection remain allowed, so immutability is not a freeze on operations — it is a one-way ratchet.
Immutability has two states:
Enabled (unlocked) — reversible while you validate the impact on your operations.
Enabled and locked — irreversible . Neither you nor Microsoft support can remove it.
The exam scenario is almost always "a compliance mandate requires that recovery points cannot be deleted before their retention expires, even by an administrator" → immutable vault, locked .
Multi-User Authorization and Resource Guard
Multi-user authorization (MUA) implements four-eyes control over destructive backup operations.
How it works:
A Resource Guard resource is created — critically, in a different subscription and ideally a different Microsoft Entra tenant from the vault.
The vault is associated with the Resource Guard.
Protected operations (disabling soft delete, removing MUA, reducing retention, stopping backup with data deletion, changing MARS security PIN) now require the caller to hold a role such as Backup MUA Operator on the Resource Guard.
The backup administrator does not hold standing access to the Resource Guard. They request just-in-time access through PIM , which a different security administrator approves.
The security property is separation of blast radius: compromising the backup administrator's account is no longer sufficient, because the approval authority lives in an identity boundary the attacker has not breached. If a scenario says "even a compromised backup administrator must not be able to delete backups", MUA with a cross-tenant Resource Guard is the answer — immutability alone protects existing recovery points but does not require a second human.
MARS Agent and Hybrid Backup Security
For on-premises workloads protected with the Microsoft Azure Recovery Services (MARS) agent, Azure adds agent-specific controls:
Security PIN required for critical operations: changing the passphrase, stopping backup with data deletion, and reducing retention. The PIN is generated in the Azure portal by an identity with vault access, so malware on the protected server cannot produce it.
Deleted backup data is retained for 14 days at no cost, with alerts raised to vault contacts.
Minimum retention enforcement prevents an attacker from reducing retention to near-zero as a precursor to deletion.
The passphrase encrypts data before it leaves the server and is not known to Microsoft, so it must be escrowed — losing it means losing the ability to restore.
Role Separation, Encryption, and Network Isolation
Least-privilege backup roles:
- Role Can do Cannot do
- Backup Reader View backup status and reports Any change
Backup Operator Configure, run, and restore backups Delete the vault, stop protection with delete data, modify vault security settings
Backup Contributor Full backup management Grant access to others (that requires Owner/User Access Administrator)
Give day-to-day teams Backup Operator , keep Backup Contributor in a PIM-eligible role, and never grant subscription Owner as a shortcut.
Encryption: vault data is encrypted at rest with platform-managed keys by default; switch to customer-managed keys where policy requires key ownership, and enable infrastructure encryption for double encryption. For Azure VM backups, the disks' own encryption (ADE or CMK-backed SSE) carries into the recovery points.
Network isolation: deploy private endpoints for the Recovery Services vault so backup and restore traffic from Azure VMs and MARS agents never traverses public endpoints, and disable public network access on the vault.
Cross Region Restore on a geo-redundant vault gives you a restore path in the paired region without waiting for a Microsoft-declared outage — useful when a regional incident coincides with an attack.
Monitoring: route Backup vault diagnostic logs and Azure Monitor alerts for jobs and security events to your Log Analytics workspace, and build a Sentinel analytics rule for "protection stopped with delete data" and "soft delete disabled". Those two events are among the highest-fidelity ransomware precursors available in Azure.