What Is Immutable Backup? How It Stops Ransomware

Immutable backup stores data so it cannot be altered or deleted for a set period. Learn how it works, WORM vs. object lock, and best practices.

Content

    What is an immutable backup?

    An immutable backup is a backup copy that cannot be modified, encrypted, overwritten or deleted by anyone, including administrators, until its retention period ends. Immutability is usually enforced through write once, read many (WORM) storage, object lock or a backup platform's own controls. Because ransomware and malicious insiders cannot alter it, an immutable backup gives you a trustworthy copy to restore from after an attack.

    Key Takeaways

    • Attackers go after backups first. Ransomware crews look for backup consoles and storage so victims have nothing to restore. 
    • Immutable means admin-proof. If a stolen admin account can shorten retention or delete the copy, the backup is not truly immutable.
    • Immutable is not the same as clean. A backup taken after malware landed is locked with the malware inside it. You still need to find a clean restore point.
    • Pair it with isolation. Immutability protects the data; an air gap keeps attackers away from the system that holds it.

    How immutable backup works

    1. The backup is written once. Data lands in storage that accepts new writes but blocks changes to existing objects.
    2. A retention lock is applied. Each copy gets a period, for example 30 or 90 days, during which no one can delete it.
    3. Deletion requests are refused. Requests to delete, overwrite or shorten retention fail, whatever the account's privileges.
    4. The lock expires on schedule. After retention ends, the copy ages out under normal lifecycle rules.

    Types of immutability

    Approach

    How it works

    Watch out for

    WORM hardware or tape

    Storage media physically or logically blocks rewrites

    Hardware cost, slow restores from tape

    Cloud object lock (compliance mode)

    Storage service blocks deletes until retention ends, even for root users

    Mistakes in retention cannot be undone

    Object lock (governance mode)

    Blocks deletes, but users with special permission can override

    A stolen privileged account can bypass it

    SaaS backup platform controls

    The vendor's service enforces retention and blocks deletes from the customer side

    Confirm admin actions need extra approval

    Immutable backup best practices

    • Make retention changes hard. Require multi-person approval to shorten retention or delete backup sets.
    • Separate backup credentials from production. Do not use domain admin or cloud root accounts to manage backups.
    • Keep enough history. Retain copies long enough to reach back before an attacker's dwell time began.
    • Scan before you restore. Check immutable copies for malware and indicators of compromise before putting them back in production.
    • Test restores. Immutability only helps if the copy restores at the speed you need.

    How Druva delivers immutable backup

    The Druva Resilience Cloud is a fully managed SaaS platform that stores backups as air-gapped, immutable copies outside your network. Because Druva runs the infrastructure, attackers can't reach a backup server or storage array in your environment.

    • Immutable by design. Backup data cannot be changed or deleted from the customer environment. 
    • Isolated from your credentials. Backups sit in a separate cloud tenant protected by envelope encryption. Read more on Platform Security.
    • One policy across workloads. Protect cloud, data center, SaaS and endpoint data from one console.
    • Faster clean recovery. Accelerated Recovery & Response helps find the most recent clean copy before you restore.

    Keep a copy attackers cannot touch. Book a Demo 

    FAQs

    Q
    Can ransomware encrypt an immutable backup?
    A

    Ransomware cannot change or encrypt an immutable backup during its retention period. It can still infect the production data that gets backed up next, which is why you also need clean-point detection.

    Q
    What is the difference between immutable and air-gapped backups?
    A

    Immutable backups cannot be altered. Air-gapped backups are isolated from the production network. The strongest designs combine both, so an attacker can neither reach nor change the backup.

    Q
    How long should immutable backups be retained?
    A

    Long enough to restore from a point before an attack began. Many teams keep at least 30 days of immutable copies, and longer for regulated data. Set the period based on dwell time, compliance rules and storage cost.

    Q
    Are cloud snapshots immutable?
    A

    Not by default. Native snapshots can often be deleted by anyone with the right cloud permissions. Immutability needs object lock, a separate account or a backup service that enforces it.

    Further Reading