Resources /
Blog

What Is an Immutable Data Backup?

Submit your details to get a book

9
Min Read
Resources /
Blog

What Is an Immutable Data Backup?

Download

Submit your details to get a book

9
Min Read
Neon shield with a padlock linked to key, database and clock tiles
Neon shield with a padlock linked to key, database and clock tiles

An immutable backup is a copy of data that can't be changed or deleted until its retention period ends, even by an administrator. NIST SP 800-209 describes immutability as the ability to lock data after it has been created, preventing alteration or deletion.

For Salesforce teams, it's the part of Salesforce backup and recovery that a bad integration, a mass delete or a ransomware crew can't rewrite. Salesforce keeps its own backups, but its help page says they can't be used to restore business data outside an infrastructure event.

Under the shared responsibility model, protecting and recovering that data is the customer's job. Attackers know where the copies sit, too: CISA's Akira advisory describes actors exploiting unpatched Veeam backup servers, and a ransomware backup strategy has to plan for that.

How Immutable Backups Work

A traditional backup can be overwritten or deleted by anyone with enough access, administrators included. An immutable one blocks writes at the storage API or hardware layer, so the copy outlives a stolen admin account or a destructive mistake.

The core definition

Once the lock is set, the copy stays as written for the whole retention period. A properly configured policy can't be bypassed with full administrative credentials during that time, which is what separates it from just another layer of deletable copies.

WORM enforcement

Write Once, Read Many (WORM) is the model most immutable storage uses. Cloud providers apply object-level locks that block deletion or changes for a set retention period, and two modes matter for compliance decisions:

  • Compliance mode: no user, including the root user of the cloud account, can overwrite or delete the object, and the retention period can't be shortened.
  • Governance mode: users with special permissions can still change the retention settings or delete objects.

Compliance mode suits regulated records that must stay fixed. Governance mode fits cases where a small group needs a way to override the lock.

Additional enforcement mechanisms

WORM is the main control, and three other mechanisms add to it:

  • Legal holds: a legal hold keeps data in a WORM state until someone clears it. It works apart from time-based retention, so it suits litigation or audits where nobody knows how long the data must be kept.
  • Air-gap isolation: a backup target with no live network path can't receive a remote delete request.
  • Cryptographic hashing: NIST lists hashing among the cryptographic functions that guard data against modification. Matching hashes give auditors evidence that a backup hasn't changed since it was written.

Why Salesforce Native Tools Leave a Gap

Inside the platform, Salesforce relies on immutable storage for its own durability. That protection covers how Salesforce stores data, not the backups customers can reach.

When a user overwrites or deletes a record, the new state becomes the real one. Most causes of data loss in Salesforce start that way, and the native tools each stop short:

  • Data Export Service: Enterprise Edition can export only once every 7 days. The output is CSV files of data, not metadata.
  • Recycle Bin: deleted records stay for 15 days. Records that were overwritten or corrupted never land there.
  • Salesforce Backup & Recover: it runs on a schedule, and Salesforce's own blog notes that even several backups a day still create recovery gaps.
  • Metadata: backing it up is a separate workflow from data backup.

None of these tools produce immutable copies. Each one is deletable, overwritable or time-limited, and in regulated industries that turns into audit exposure that policy alone can't close.

Regulatory Frameworks That Require Data Immutability

Several rules push Salesforce recovery design toward storage users can't rewrite or erase. The provisions below help justify that spend during audit preparation.

SEC Rule 17a-4

SEC Rule 17a-4 covers electronic recordkeeping for broker-dealers. It used to demand WORM storage outright, and since 2022 it allows one alternative.

  • Requirement: the 2022 amendments kept WORM ("non-rewriteable, non-erasable") storage as an option and added an audit-trail alternative. That system must let a firm recreate an original record if it's modified or deleted.
  • Retention: depending on the record type, broker-dealers keep records for at least six years or three years, the first two in an easily accessible place.

HIPAA

HIPAA never uses the word "immutable." Its backup and integrity rules still add up to much the same thing for any Salesforce org that holds ePHI, and our HIPAA data backup post goes into more detail.

  • Exact copies: covered entities must keep retrievable exact copies of electronic protected health information (§ 164.308(a)(7)(ii)(A)).
  • Integrity: the Security Rule requires policies that protect ePHI from improper alteration or destruction (§ 164.312(c)(1)).
  • Retention: required security documentation is kept for 6 years (§ 164.316(b)(2)(i)).
  • What it means for Salesforce: orgs that store ePHI need both exact recovery and integrity protection.

SOX Section 802

SOX ties record destruction to criminal liability, which makes retention a board-level concern rather than an IT preference. A SOX compliance checklist covers the controls around it.

  • Requirement: under the SEC's final rule, auditors keep audit and review records for seven years.
  • Enforcement: 18 U.S.C. § 1519 makes it a crime to knowingly destroy or alter records to obstruct a federal investigation. It carries up to 20 years in prison.
  • Salesforce impact: backup retention for records that support an audit should match that seven-year window.

NIST SP 800-209 and NIST IR 8374r1

These two NIST publications set the federal baseline for what good backup protection looks like. Both treat immutability as part of a backup plan, not an extra.

  • SP 800-209 (October 2020): lists "immutability and locking" among the protection requirements a data protection plan should cover. It also recommends considering immutable storage to isolate recovery data.
  • IR 8374r1 (June 2026): the final ransomware profile lists storing data in an immutable format as a ransomware safeguard. It also says backups should have a copy kept offline or out of an attacker's reach.
  • Effect on Salesforce teams: the bar moves from having a backup to protecting it.

GDPR

GDPR pulls against pure immutability, so Salesforce architects have to design for retention and erasure at once. A copy that can't be deleted also can't be erased on request.

  • Integrity (Article 5(1)(f)): sets integrity and confidentiality as core principles.
  • Erasure (Article 17): the right to erasure sits awkwardly with fully immutable storage.
  • In Salesforce: resolve the conflict with targeted retention periods or documented processes for data under a retention lock.

What an Effective Immutable Backup Solution Requires

Storing copies is only the start. A sound solution protects the data, isolates it from production risk and proves that a restore will work.

SP 800-209 names four security areas specific to storage: data protection, isolation, restoration assurance and encryption. Built around those areas, a solution for Salesforce should offer these eight capabilities:

  • WORM immutability with retention locks that block changes or deletion at the storage API layer.
  • Encryption in transit and at rest, with key management that covers re-keying and key backup.
  • Isolation from production through network separation or an air gap.
  • Coverage of every data asset, wherever it lives, with defined RPO and RTO targets.
  • Restoration assurance, including checks that recovered components are free of malware before they go back into production.
  • Privileged access controls with least privilege, role-based access and multifactor authentication for backup operations.
  • Audit trails that record every backup, restore and configuration change.
  • Integrity checks through hashing and digital signing, so tampering shows up regardless of what the storage layer claims.

Immutability on its own isn't the goal; recoverability is. NIST frames data protection as keeping data accessible, usable, uncorrupted and available, and the restore has to work without paying a ransom.

Implementation Best Practices

These practices come from CISA and NIST guidance, mapped to the gaps Salesforce's native tools leave. Getting them right early saves costly rework later.

Follow the 3-2-1-1 rule

The joint LockBit advisory passes on ACSC's 3-2-1 strategy: three copies of data on two different media, with one copy kept off-site. It adds that backup data should be encrypted, immutable and cover the entire organization's data infrastructure.

Adding that immutable copy to the 3-2-1 backup rule gives what some teams call 3-2-1-1. CISA's #StopRansomware Guide also suggests a multi-cloud setup for cloud-to-cloud backups, in case every account with one vendor is hit.

For Salesforce, keep captured data outside the production control plane. The guide adds a caution worth reading before you lock anything: immutable storage "does not meet compliance criteria for certain regulations."

Define RPO and RTO before choosing technology

Recovery targets should drive the tool choice, not the other way round. If your recovery point target is shorter than the native export interval, native tools can't meet it.

SP 800-209 says the data protection plan should be set before deployment, with backup frequency and retention tiers that meet recovery goals. Using only the Data Export Service, a weekly export means you could lose up to a week of changes, so tighter targets need another backup method.

Test recovery regularly

A backup nobody has restored proves nothing. Testing confirms that the data is intact and that retention locks hold.

CISA's guide recommends regularly testing the availability and integrity of backups in a disaster recovery scenario. The LockBit advisory asks for backup and restoration "daily or weekly at the minimum."

SP 800-209 gives restoration assurance its own section of recommendations. In Salesforce, tests should check backup completion, data integrity and retention enforcement.

Apply Zero Trust principles to backup access

Backup access needs the same controls as production administration, because attackers go after privileged paths first. The RansomHub advisory recommends Just-in-Time access for admin accounts, with admin rights switched off automatically when they aren't needed.

Applied to Salesforce backup and deployment jobs, that narrows the admin paths an attacker could use to reach recovery data. Review those accounts with the same care as production admins.

Protecting Salesforce Data with Purpose-Built Solutions

Closing the gap between native limits and compliance takes tools built for Salesforce. Flosum adds deployment pipelines for metadata and audit trails for compliance reporting, which address the metadata and change-control gaps above.

Backup & Archive covers Salesforce data, metadata, files, attachments and object relationships. It stores backups apart from Salesforce, encrypted at rest and in transit (with keys you hold when backups run in your own cloud), with point-in-time restore down to the field, record or full org.

You choose where backups live: Flosum-hosted cloud, or customer-hosted in your own AWS, Google Cloud, Azure or private cloud. That choice helps with data sovereignty, and Flosum's trust center lists its ISO 27001 and SOC 2 standing.

Retention policies and right-to-erasure support help balance GDPR against long retention. Pair that with the steps in our guide to preventing accidental data loss and the native gaps get much smaller.

FAQs

What is an immutable backup?

It's a backup copy locked against changes and deletion for a set retention period, so not even an administrator can alter it. Once that period ends, the copy can be deleted under your normal policy.

What is WORM storage?

WORM stands for Write Once, Read Many: data can be written a single time and read as often as needed, but not changed. Cloud services such as Amazon S3 Object Lock and Azure immutable blob storage apply it through retention policies and legal holds.

Does Salesforce provide immutable backups?

No, Data Export files, the Recycle Bin and Salesforce Backup & Recover can all be deleted, overwritten or aged out. Salesforce uses immutable storage inside its own platform, but that doesn't reach the backups customers manage.

Do regulations require immutable backups?

Some come close: SEC Rule 17a-4 lets broker-dealers pick WORM storage or an audit-trail system, and HIPAA requires exact ePHI copies kept safe from improper alteration. NIST and CISA guidance recommend immutable or offline copies as a ransomware defense.

How does immutability work with GDPR erasure?

Plan for both from the start, because a locked copy can't honor an erasure request until its lock expires. Keep retention periods targeted, and document how you handle personal data held under a lock.

Book a demo to see how Flosum keeps Salesforce backups apart from production, encrypted and stored where you choose.

Table Of Contents
Author
Stay Up-to-Date
Get flosum.com news in your inbox.

Thank you for subscribing

Ship Salesforce changes faster
Teams on Flosum report 40% higher development velocity and 75%
fewer merge conflicts.
Free to start  |  No credit card required