Salesforce Backup Compliance Checklist for HIPAA and GDPR Audits

Updated: Nov 2
An audit-ready Salesforce backup compliance checklist covers six areas: retention, access restriction, encryption, recovery testing, audit evidence, and data ownership. For each one, a feature on a vendor's spec sheet isn't enough. You need to show an auditor the mechanism behind it and the evidence that it works. This guide gives enterprise IT teams the checklist, maps each item to what HIPAA and GDPR actually ask for, and shows how to run it before the auditor asks the first question.
Why Salesforce Backup Compliance Needs a Formal Checklist
Salesforce does back up your data. It protects its own platform, keeps deleted records in the Recycle Bin for 15 days, offers weekly or monthly Data Export, and sells Backup & Recover as a paid add-on. But under Salesforce's shared responsibility model, the controls an auditor expects to see are yours to define and prove: a retention policy, restricted access, encryption, tested recovery, and documented evidence.
HIPAA compliance and GDPR compliance both ask for more than a working backup. They ask for a documented process that shows how you protect the backup, how long you keep it, who can reach it, and how fast you can recover. A Salesforce backup compliance checklist turns those requirements into items your team can verify one at a time, well before an audit is on the calendar. Teams that treat it as a one-time checkbox usually find the gaps during the audit itself, when they're far more expensive to fix.
Look for the Mechanism, Not the "Compliant" Label
Vendors often call a product "HIPAA compliant" or "GDPR ready." Neither regulation certifies software. Compliance describes how your organization configures, runs, and documents its systems, including the backup tool you rely on. So the useful question isn't whether a vendor claims compliance. It's whether the architecture gives you the specific controls each regulation requires, and whether you can explain how each one works when an auditor asks.
That's why every item below pairs a control with the mechanism behind it and the regulation it supports.
The Six-Part Salesforce Backup Compliance Checklist

1. Retention Policy Documentation
Set a retention period that meets your longest applicable requirement, and have legal or compliance sign off on the number. HIPAA requires covered entities to keep required compliance documentation for six years (45 CFR 164.316(b)(2)). SEC rules under Sarbanes-Oxley require audit records to be kept for seven years. GDPR pulls the other way: its storage limitation principle expects you not to keep personal data longer than you need it.
Document the retention window in writing, including how it's enforced technically. Automated rules that expire data on a schedule are much easier to defend than a manual, ad hoc deletion process.
2. Access Restriction and Least Privilege
Both HIPAA and GDPR build on least privilege. Confirm that only a small, named group can view backup data, start a restore, or change retention settings. Role-based access control should apply to the backup system itself, separately from permissions in the live Salesforce org. Otherwise the backup repository quietly becomes the weaker link.
Use a dedicated integration user for the Salesforce connection, with read-only access wherever the workflow allows, rather than a personal admin account that can be disabled or reassigned without warning.
3. Encryption in Transit and at Rest
Confirm that data is encrypted while it moves from Salesforce to the backup destination and while it sits in storage. GDPR names encryption as an appropriate technical safeguard (Article 32), and HIPAA's Security Rule lists it as an addressable implementation specification that most covered entities adopt.
Expect specific questions: which algorithm, which key length, and who manages the keys. A general assurance that "data is encrypted" won't hold up.
4. Recovery Testing on a Schedule
A backup that completes without errors isn't proof you can recover. Schedule recovery tests, run them in a sandbox or staging environment, and document each outcome. HIPAA's contingency plan standard expects you to test and revise your plans, and GDPR Article 32 calls for regularly testing how well your safeguards work. Auditors increasingly ask for the test record, not just the backup job log. Our Salesforce recovery testing guide walks through how to run one.
5. Audit Trails and Evidence Collection
HIPAA's audit controls standard (45 CFR 164.312(b)) and GDPR's accountability principle both expect you to show how data changed over time: who changed what, when, and from which value to which. Keep a change history that lives outside the live org, so it survives if someone later edits or deletes the original record. Native Field History Tracking covers up to 20 fields per object for 18 months (24 via API), so most regulated teams need more. Our complete guide to Salesforce audit evidence covers this in depth.
Then build a repeatable way to produce the evidence: backup job logs, retention settings, access lists, and recovery test records, all exportable without a services engagement.
6. Deployment and Data Ownership
Confirm exactly where backup data physically lives and who controls that environment. GDPR data residency expectations, and many organizations' own risk policies, hinge on this one decision. When you choose the storage location yourself, whether on-premises, in a private cloud, or in your own cloud account, you also control network security, encryption keys, and regional hosting. That's why data ownership shapes almost every other item on this checklist. Read more about data residency and self-hosted data infrastructure.
How to Run the Salesforce Backup Compliance Checklist Before Your Next Audit
Step 1: Assign an owner to each of the six areas. A checklist without an owner rarely gets maintained between audits.
Step 2: Walk through each item with the current configuration in hand. Verify live settings instead of relying on last year's documentation.
Step 3: Flag every gap in writing, with a remediation date. A documented gap is far more defensible than one an auditor finds live.
Step 4: Re-run a recovery test. If the last one predates this review, treat that as a finding.
Step 5: File the evidence where you can find it fast. Pulling it should take minutes once the audit starts, not days.

Warning Signs Your Salesforce Backup Compliance Won't Hold Up
Most audit failures trace back to a handful of recurring gaps, not one catastrophic error. Check for these:
Stale documentation: a retention policy that no longer matches production because someone changed a setting during a migration.
No separate access model: anyone with admin rights in production also has unrestricted access to every backup, restore, and retention setting.
Encryption nobody can explain: no named algorithm and no key management process, just an assurance that data is "secure."
Retention with no end date: data piles up with no defined deletion process, which runs against GDPR's storage limitation principle.
A replica treated as a backup: a near real-time copy for reporting mirrors bad updates and deletions too, so it can't replace point-in-time backups.
Untested recovery: a job that reports success every night can still fail the one time it matters.
Access sprawl: permissions granted for a one-time project that were never revoked.
How Sesame Software Supports Salesforce Backup Compliance
Sesame Software's Salesforce Backup and Recovery maps directly onto this checklist, and each control comes with a mechanism you can explain to an auditor:
Retention: GDPR Clean lets you define retention rules by backup, object, and date field, and automates deletion once data passes its window. Multiple retention tasks let different objects follow different schedules.
Access: role-based access control protects the backup environment itself, and elevated Super User access is capped at three per environment.
Encryption: data is encrypted in transit with TLS 1.2 or higher and at rest with AES-256, and sensitive configuration values are encrypted with Jasypt (PBEWITHHMACSHA512ANDAES_256).
Recovery testing: full, object-level, and record-level restores let you scope a realistic test to exactly what you need to verify.
Audit trails and evidence: patented History Tracking keeps a history table for each backed-up object, independent of native Field History limits, and job activity logs give compliance staff exportable evidence.
Data ownership: backups go to an Oracle, SQL Server, or PostgreSQL database you choose, on-premises or in the cloud. Sesame Software never stores your data on its servers.
Backed by 30+ years of enterprise data management experience and SOC 2 Type II certification, Sesame Software treats compliance readiness as part of the backup architecture, not an add-on.
A checklist only protects you if your platform can satisfy every item on it. Talk to a Data Expert to see how automated retention, role-based access control, and customer-owned storage can take the guesswork out of your next Salesforce compliance audit.
Salesforce Backup Compliance FAQs
What does a Salesforce backup compliance checklist need to cover?
At minimum: documented retention, access restriction and least privilege, encryption in transit and at rest, scheduled recovery testing, audit trails with exportable evidence, and clear ownership of where backup data is stored.
Does Salesforce back up your data?
Yes. Salesforce protects its platform, offers the Recycle Bin and weekly or monthly Data Export, and sells Backup & Recover as a paid add-on. Under the shared responsibility model, though, your organization still owns its Salesforce backup compliance: the retention policy, access controls, recovery testing, and evidence an auditor will ask for.
Is Salesforce HIPAA or GDPR compliant out of the box?
Salesforce offers infrastructure and features that support compliance, but compliance depends on how your organization configures and runs the platform, including the backup, retention, and access practices layered on top. Neither regulation certifies a vendor's platform as automatically compliant for every use case.
What encryption does Salesforce backup software need for HIPAA and GDPR?
Encryption of data in transit between Salesforce and the backup destination, and encryption of stored data at rest, using a documented, named algorithm. Auditors typically ask for the algorithm, how keys are managed, and where encrypted values live.
How often should Salesforce backups be tested for HIPAA or GDPR audits?
On a regular, documented schedule, not only after an incident. Many enterprise teams align test frequency with their backup schedule and re-test after any significant change to their Salesforce org or backup configuration.
Does GDPR require deleting Salesforce backup data after a certain period?
GDPR doesn't set one universal number. Its storage limitation principle expects you not to keep personal data longer than necessary for a defined purpose, balanced against other legal retention requirements. Automated retention rules make it practical to enforce whatever period your legal and compliance teams set.
Where should compliance-sensitive Salesforce backup data be stored?
In a database your organization controls directly, on-premises or in a customer-managed cloud environment, rather than only inside a vendor's shared infrastructure. Direct control simplifies access restriction, encryption key management, and evidence collection.
Is a real-time data replica the same thing as a compliant backup?
No. A replica that mirrors live Salesforce data captures whatever state the source is in, including accidental deletions and bad updates. A compliant backup process needs point-in-time snapshots, independent retention, and a tested restore path, in addition to any replication you run for reporting.
Related Resources
Found this post helpful? Share it with your network using the links below.



