Immutable Backups Explained: Protect Your Files From Ransomware Without Enterprise Costs

··13 min read
Immutable Backups Explained: Protect Your Files From Ransomware Without Enterprise Costs

Ransomware has changed the economics of data loss. A few years ago, most small businesses and serious home users assumed that a nightly copy to an external drive was enough. Then the attackers started targeting backups too. The modern ransomware playbook is simple: get in quietly, spend days or weeks mapping the network, find the backup server, encrypt or delete the backups, and only then lock the production files. Many victims discover this only when they try to restore and find that every recent copy is also encrypted.

That is the problem an immutable backup solves. Instead of trusting that nobody will touch your backups, you configure storage so that once a backup is written, it cannot be modified or deleted for a defined period, even by an administrator with full credentials. The concept is not new, and for years it lived mostly inside large enterprise storage arrays with six-figure price tags. What has changed is that the same protection is now available from inexpensive object storage, many backup tools, and even some consumer-grade services.

This article explains what immutability actually means at the storage level, how it differs from the backup "features" vendors often advertise, and how to set up an immutable backup layer without enterprise budgets. We will walk through a worked cost example, compare the common approaches on the criteria that matter, and cover the traps that catch people who assume their backups are safe. If you only read one section, read the key takeaways below. If you have a backup routine that has not been tested against a realistic attack, the rest of the article will show you how to find out where it breaks.

Key Takeaways

  • An immutable backup is one that cannot be altered or deleted for a set retention period, even by someone holding administrator credentials.
  • Ransomware gangs routinely hunt for and destroy backups before triggering encryption, so a backup that an attacker can reach is not a real backup.
  • Object storage with Object Lock or equivalent write-once retention gives you immutability for a few dollars per terabyte per month, without buying dedicated appliances.
  • Immutability is only half the strategy. You still need offsite copies, versioning, a tested restore procedure, and separate credentials for the backup system.
  • Retention periods of 14 to 30 days are a practical starting point for most small organizations, balanced against storage cost.
  • Test a full restore at least quarterly. An immutable copy you have never restored from is an assumption, not a plan.

What Is an Immutable Backup, Exactly?

An immutable backup is a copy of your data written in a way that prevents modification or deletion for a defined time window. Once the retention period is set, the storage layer itself refuses any request to overwrite or remove those objects. The restriction is enforced by the storage system, not by a policy your IT team could quietly change.

This distinction matters. Most backup software offers "retention" settings, and most people assume those are protective. In practice, retention in software is a rule the software enforces. Anyone who gets into the backup server with administrative rights can change that rule, delete the backup catalog, or wipe the repository. Ransomware operators know this, and they routinely use stolen domain admin credentials to do exactly that.

Immutability moves the enforcement out of reach of the compromised account. The three properties that define a truly immutable backup are:

  • Write-once or write-protected storage: the object cannot be overwritten during the retention window.
  • Locked retention: the retention period cannot be shortened by a user, sometimes even by the account owner, depending on the mode chosen.
  • Separate control plane: the credentials that can delete backups are distinct from the credentials used by production systems.

If any of those three is missing, you have a backup that is harder to destroy, not an immutable one. The difference matters when the attacker is patient.

Why Ransomware Targets Backups First

Modern ransomware is rarely a single file-encrypting program that runs at 3 a.m. It is usually a human-operated intrusion. Attackers gain initial access through a phished password, an unpatched VPN appliance, or an exposed remote desktop service. They then spend time escalating privileges and moving laterally. Dwell times of several days to a few weeks are common in published incident reports.

During that dwell time, a careful attacker looks for backups. They search for backup agents, scan for network shares named "backup" or "archive," check whether the backup software is reachable from the compromised machine, and look for stored credentials. Once they find the repository, they delete or encrypt it, often hours before deploying the ransomware payload to production. The victim then has nothing to restore from except whatever backup happens to be offline or stored elsewhere.

This is why the old advice to "keep a backup on an external drive" only goes so far. If the drive is permanently connected, it is reachable. If it is disconnected, the backup is only as recent as the last time someone remembered to plug it in. Immutability removes the trade-off by making a connected copy that cannot be destroyed.

A Worked Example: What Does This Actually Cost?

Consider a small design studio with about 2.4 TB of active project files, client assets, and archived work. The studio has a NAS in the office and a backup job that copies everything to an external USB drive every night. The owner, Priya, assumes she is covered. She is not, for the reasons above, but let us put numbers on the fix.

Her plan has three layers:

  1. Local copy: the NAS keeps its own snapshots, retained for 7 days.
  2. Immutable offsite copy: a nightly backup goes to S3-compatible object storage with Object Lock enabled in compliance mode, retention set to 30 days.
  3. Offline copy: a monthly copy to a drive that stays disconnected except during the backup window.

Priya's cost math looks like this. Her live data is 2.4 TB. Because the immutable copy is incremental, the stored volume grows by the changed data plus the retained versions. Assume a 5 percent daily change rate and 30 days of retention. That works out to roughly 2.4 TB for the base set plus about 0.12 TB of new data per day, or around 3.6 TB total at steady state, depending on how much data is deduplicated. At typical object storage rates of roughly $0.02 to $0.025 per GB per month, that comes to somewhere between $70 and $90 per month. Egress fees, the charge for downloading data, are the surprise. A full restore of 2.4 TB at a common rate of $0.09 per GB could cost over $200, so Priya should check that before she needs it urgently.

Compare that with a dedicated enterprise backup appliance that offers similar protections. Hardware, support contracts, and licenses for a comparable capacity often run into several thousand dollars a year, before staff time. For a studio of four people, the cloud route is the realistic choice.

The point of the example is not that $80 a month is cheap or expensive in the abstract. It is that immutability for a small operation is now a line item measured in tens of dollars, not a capital project. Whether it fits your budget depends on how much your data is worth to you, which is a question worth answering before the attacker does it for you.

Comparing Immutable Backup Options

There is no single right tool. The best choice depends on your data volume, technical comfort, and tolerance for recurring cost. The table below compares the approaches most small teams actually consider. Prices and features change, so verify current numbers with each vendor before committing.

Option Immutability Method Typical Monthly Cost (2.4 TB) Setup Effort Restore Speed Best For
Object storage with Object Lock (S3-compatible) Write-once retention enforced by storage About $70 to $90 plus egress Moderate, needs a backup tool that supports it Good, depends on bandwidth Small businesses and technical solo users
Backup SaaS with built-in immutability Vendor-managed retention lock Often $100 to $200 per month Low, mostly point-and-click Good Teams without dedicated IT
Linux repository with hardened, append-only access Filesystem permissions and append-only mode Hardware cost only, roughly one-time High Fast on local network Users with spare hardware and Linux skills
Offline rotated drives Physical air gap Drive cost, roughly one-time Low, but relies on discipline Fast locally Home users and small offices as a third layer
Enterprise backup appliance Vendor WORM and retention controls Several thousand dollars per year High Very fast Organizations with compliance mandates

For most readers of this article, the first row or the first two rows are the practical starting points. The offline drive is a worthwhile addition regardless, because it protects against the scenario where your cloud credentials are compromised along with everything else.

How to Set Up an Immutable Backup Layer, Step by Step

The following walkthrough uses object storage with Object Lock, which is the most common path for small teams. The exact menu names vary by provider and backup tool, but the sequence is the same.

  1. Choose a provider and create a dedicated bucket. Pick a provider that supports Object Lock or an equivalent write-once feature. Create a new bucket used only for backups. Do not reuse a bucket that production applications write to.
  2. Enable Object Lock at bucket creation. On most platforms, Object Lock must be turned on when the bucket is created. You generally cannot add it afterward. Enable versioning at the same time, since Object Lock depends on it.
  3. Choose the retention mode. Governance mode lets users with special permissions shorten or remove retention. Compliance mode prevents anyone, including the account root user, from deleting locked objects until the period expires. For ransomware protection, compliance mode is the stronger choice. Understand that it is also irreversible until expiry, so test with a small bucket first.
  4. Set a default retention period. A common starting point is 30 days. Shorter periods save money but give attackers who dwell for two weeks a chance to outlast the window. Longer periods cost more in storage.
  5. Create a dedicated backup user with minimal permissions. This account should be able to write objects and read them back for restores. It should not be able to change bucket settings, alter retention, or delete versions. Store its keys in your backup software's configuration, not in a shared document.
  6. Configure the backup tool to write to the bucket. Point your backup software at the bucket using its S3 or compatible connector. Enable the option to apply retention on upload if the tool supports it. Run one manual backup and confirm the objects show a retention date in the provider console.
  7. Verify immutability.Cover image: Software by I.Gouss, licensed under BY-SA 2.0 via Openverse.

Recent Posts

View all →

Most Popular Software

View all →

Browse by Platform

View all →