top of page
Sesame Software

8 Salesforce Backup Controls for HIPAA and GDPR

Writer: Sesame Software
Sesame Software
Oct 8
8 min read

Updated: Oct 21

Quick answer

To keep a Salesforce backup compliant with HIPAA and GDPR, you need eight controls: continuous automated backup, complete field-level audit trails, granular point-in-time recovery, customer-controlled storage, role-based access to backup data, encryption in transit and at rest, governed retention and erasure, and documented recovery testing. Salesforce's native tools cover pieces of this, but not enough to stand up in an audit. Most teams close the gap with a dedicated backup platform that keeps the data in their own environment.


Key takeaways


  • HIPAA and GDPR treat your backup copies as regulated data, just like the records in your live org.

  • Native Salesforce tools keep field history for 18 months, deleted records for 15 days and setup changes for 180 days. Compliance windows run for years.

  • GDPR erasure requests reach your backups too, so you need a documented way to delete or isolate those copies.

  • Auditors want proof, not promises: access logs, encryption details and dated recovery test results.


The compliance gap most IT teams discover too late

Most teams think of Salesforce backup as insurance against a bad day. Compliance asks for something bigger: a governed, auditable record of every change, deletion and access event, kept for as long as the law says, somewhere you control.


The risk usually comes from inside. In Backupify's 2025 State of SaaS Backup and Recovery report, 87% of the more than 3,000 IT professionals surveyed said their organization lost SaaS data in the past year. Accidental deletion or human error caused 34% of those incidents, misconfiguration 30% and third-party integrations 30%. When that happens to regulated data, the question isn't just "can we get it back?" It's "can we prove what happened, when we caught it, and how we fixed it?"


That's the gap. A backup that can restore data but can't show an auditor the evidence trail behind it won't hold up under HIPAA or GDPR.


What HIPAA and GDPR require from your Salesforce data security and compliance

Both regulations apply to backup copies the same way they apply to production data. Here's what each one asks for, in plain terms.


HIPAA

HIPAA requirement

What it means for your Salesforce backup

Contingency plan, 45 CFR 164.308(a)(7)

Keep retrievable, exact copies of ePHI, have a disaster recovery plan, and test and revise it

Audit controls, 164.312(b)

Record and examine activity in systems that hold ePHI, including who changed what and when

Access control, 164.312(a)(1)

Only authorized people can reach ePHI, and that includes the backup

Encryption and transmission security, 164.312(a)(2)(iv) and 164.312(e)(1)

Protect ePHI at rest and as it moves between Salesforce and your backup

Business Associate Agreement, 164.308(b)

Any vendor that stores or processes your ePHI must sign a BAA. A backup that stays in your own environment keeps that list short

Documentation retention, 164.316(b)(2)

Keep required compliance documentation for six years. Many teams apply the same six-year window to audit logs


Two of these, recovery testing and encryption, are "addressable" under HIPAA. That doesn't make them optional: you either put them in place or document why an equivalent alternative is reasonable. Most auditors expect to see both.


GDPR

GDPR article

What it means for your Salesforce backup

Article 5

Backup data must stay accurate, secure, and kept no longer than necessary

Article 17

Erasure requests extend to backup copies, not just your live records

Article 20

You must be able to hand personal data back in a machine-readable format

Article 30

Document your processing, including where backup data lives and why

Article 32

Use appropriate security such as encryption, restore data in a timely way after an incident, and regularly test that you can


When rules overlap, follow the longest retention period. HIPAA documentation runs six years. SOX audit records typically run seven. GDPR says no longer than necessary for the purpose, so set retention per object and document why.


Where Salesforce's native tools fall short

Salesforce gives you useful built-in tools, but they were built for day-to-day admin work, not multi-year compliance. Under Salesforce's shared responsibility model, backing up and restoring your data is your job.

Chart comparing Native Salesforce retention vs compliance: 18 months, 180 days, 15 days vs 6+ years HIPAA documentation.

Native tool

What it gives you

Where it falls short

Field History Tracking

Change history on up to 20 fields per object

Keeps history for 18 months (24 via API). HIPAA documentation runs six years

Recycle Bin

Recovers recently deleted records

Records are purged after 15 days

Setup Audit Trail

Log of configuration changes

Keeps 180 days of history

Data Export Service

Weekly or monthly CSV snapshots

No point-in-time or field-level restore, and restoring from CSV can overwrite current data


There's one more gap: all of it lives inside Salesforce's infrastructure. If your compliance team needs backup data in a specific region, or wants copies outside the system they're protecting, native tools can't help.


The 8 Salesforce backup controls for HIPAA and GDPR

Infographic titled 8 backup controls for HIPAA and GDPR, showing eight numbered compliance steps and the Sesame Software logo.
Click the graphic to view larger.

The first four controls make sure you have the right data. The last four make sure you can protect it, prove it and recover it.


1. Continuous automated backup

Back up data and metadata automatically, as often as every 5 to 15 minutes, across standard objects, custom objects and deleted records. A weekly export leaves days of changes with no recovery point, and that's exactly where a HIPAA contingency plan gets tested.


Supports: HIPAA contingency plan, GDPR Article 32 (restoring availability).


2. Complete field-level audit trails

Track every field on every object, with no 20-field cap and no 18-month expiry. Your audit trail should show the old value, the new value, who changed it and when, including for records that were later deleted. That's the evidence an auditor asks for. For more on building that trail, see our complete guide to Salesforce audit evidence.


Supports: HIPAA audit controls, GDPR Articles 5 and 30.


3. Granular point-in-time recovery

Restore exactly what broke, at the record, field or value level, to any point in time, without overwriting good data around it. Say a bulk import overwrites a field across thousands of records. A field-level restore puts back only that field on only those records, and keeps parent-child relationships intact.


Supports: HIPAA contingency plan, GDPR Article 32.


4. Customer-controlled storage

Keep backup data in your own environment, on-premises or in your own cloud, in the region your compliance team requires. When the backup never sits on a vendor's servers, you know exactly where regulated data lives, and you have fewer third parties to cover with BAAs.


Supports: HIPAA Business Associate requirements, GDPR Article 30 and data residency rules.


5. Role-based access to backup data

Your backup holds the same sensitive data as production, so lock it down the same way. Limit who can view backups, run restores and change retention settings to a small, named group. Use a dedicated integration user instead of a personal admin account, and log every access.


Supports: HIPAA access control, GDPR Article 32.


6. Encryption in transit and at rest

Encrypt data as it moves from Salesforce to your backup, and while it sits in storage. Auditors will ask for specifics: the algorithm, the key length and who manages the keys. When you hold the keys, nobody else can read your backups.


Supports: HIPAA encryption and transmission security, GDPR Article 32.


7. Governed retention and erasure

Set retention per object to match the longest rule that applies, and have a documented workflow for GDPR erasure requests that reaches backup copies too. Each deletion should leave a record showing what was removed, when and why. Our post on Salesforce backup retention policies goes deeper on setting those periods.


Supports: GDPR Articles 5 and 17, HIPAA documentation retention.


8. Documented recovery testing

A backup you've never restored is a guess. Run recovery tests on a set schedule, ideally in a sandbox, and record each result: what you restored, how long it took and whether relationships came back intact. Re-test after major org changes. See our Salesforce recovery testing guide for a full testing plan, and the Salesforce backup compliance checklist to prep the evidence for your next audit.


Supports: HIPAA contingency plan testing, GDPR Article 32 (regular testing).


How Sesame Software covers all 8 controls

Sesame Software Salesforce Backup and Recovery was built for teams that need to prove compliance, not just hope for it. Here's how it lines up with each control:


  • Continuous backup: automated backups of data and metadata as often as every 5 minutes.

  • Audit trails: patented history tracking on every field, including deleted records, kept as long as you choose.

  • Point-in-time recovery: restore any record, field or value to any point in time, with relational integrity preserved automatically.

  • Your storage, your region: backups run in your environment, on-premises, in your cloud or hybrid, on SQL Server, Oracle or PostgreSQL. Sesame Software never keeps a copy of your data.

  • Access control: role-based access to the backup itself, with single sign-on support.

  • Encryption: encryption in transit and at rest, with options to bring your own keys.

  • Retention and erasure: GDPR Clean lets you set retention rules by backup, object and date field, with a record of every deletion.

  • Recovery testing: run full, object-level or record-level restores into a sandbox, and export the job logs as audit evidence.


Restores don't need a data engineer, either. Compliance managers and admins can run them from a visual interface.


Sesame Software is SOC 2 Type II certified and has over 30 years of experience protecting enterprise data for organizations like Procter & Gamble and the U.S. government. Pricing is a flat annual fee, so it doesn't climb as your record count grows.


Ready to close your compliance gaps? Request a demo and see all 8 controls running for your own Salesforce data security and compliance.


Hands review a clipboard with charts as a pen checks compliance on a transparent overlay, with sesame software logo.


Salesforce Data Security and Compliance Frequently Asked Questions

What makes a Salesforce backup HIPAA compliant?

A HIPAA-compliant Salesforce backup keeps retrievable, exact copies of ePHI, logs who accessed or changed it, restricts access to authorized users, encrypts data at rest and in transit, and is tested regularly. If a vendor stores the backup, it also needs a signed Business Associate Agreement.

Yes. Article 17 erasure applies to backup copies, not just live records. If you can't delete from a backup right away, regulators generally expect you to put that data beyond use, so it's never restored, and remove it when the backup ages out. Either way, document what you did.

An accidental deletion or a bad import can change or destroy regulated data. The compliance problem is proving you caught it, contained it and recovered it. Field-level audit trails and point-in-time restore give you that proof.

Follow the longest rule that applies to you. HIPAA documentation runs six years, SOX audit records typically seven, and GDPR says no longer than the purpose requires. Set retention per object and write down the reason.

No. Field History Tracking keeps 18 months on up to 20 fields per object, the Recycle Bin keeps 15 days, and Setup Audit Trail keeps 180 days. All of it stays in Salesforce's infrastructure. Most regulated teams add a dedicated backup platform.

Under HIPAA, any vendor that stores or processes your ePHI needs a Business Associate Agreement. With a customer-hosted backup like Sesame Software, the data stays in your environment and Sesame Software never holds a copy.

Test on a set schedule, such as quarterly, and again after any major change to your org or backup setup. Record each test's scope, time to restore and results so you have evidence ready for auditors.

With the right platform, yes. Sesame Software's visual interface lets compliance managers, legal staff and admins find records, view audit history and run restores without filing an IT ticket.

Related resources

Talk to a data expert at Sesame Software about meeting HIPAA and GDPR requirements for your Salesforce data.

Found this post helpful? Share it with your network using the links below. 

bottom of page