Blog Post
Achieve Enhanced Security for Azure Backup with Advancements in Soft Delete and Immutability
2 Comments
- UriShay-CyberSnapTin Contributor
Locked immutability plus soft delete is the right default for vaults that matter. Once a vault is Locked, an attacker with Backup Contributor cannot quietly turn protection off or shave retention, and soft delete still gives you a window after a delete.
What those controls do not answer is which point inside the vault is worth bringing a workload back from. Soft delete and WORM keep the points from disappearing. They do not tell you whether the guest data in Monday's point was already being rewritten for days before anyone noticed. I would put a joint storage and security check into the runbook before cutover: compare a few points across the suspected window for mass renames, odd extensions, ransom notes, and sudden file churn, write the shortlist down, then let the immutability settings protect that shortlist while you work.
MUA on top of Locked is worth it for the destructive vault operations.
Disclosure: I'm founder and CEO of CyberSnap, which looks at existing snapshots for signs of encryption and file tampering.
- carlosavilagilCopper Contributor
Hi! What is new in this announcement? As far as I understad, immutablity (enabled and locked) and soft delete is available in Azure since some time ago.