Edited by Jessica Eisenberg, Sr Global Campaigns · Last reviewed: November 2026
Cloud backup is HIPAA compliant when the provider will sign a Business Associate Agreement, encrypts your data at rest and in transit, controls and logs access to it, and can produce retrievable exact copies you’ve actually tested. Miss any one of those and the backup itself becomes a compliance gap, no matter how reliable the technology is.
This matters because HIPAA treats backup as mandatory. The Security Rule’s contingency plan standard requires a documented Data Backup Plan, so any healthcare team running AWS or Azure has to back up ePHI and then prove the setup meets the rule.
Below: what HIPAA requires of your backups, the criteria that separate a compliant solution from a risky one, and how the main options compare.
Quick summary
- The first split is the BAA. Services that hold a copy of your ePHI, such as AWS Backup, Azure Backup and the SaaS editions of Veeam, Commvault and Rubrik, are business associates and sign one.
- N2W runs inside your own AWS or Azure account and never receives your data, so it adds no BAA to your compliance chain. AWS and Azure stay the HIPAA-eligible layer underneath.
- N2W fits healthcare teams on AWS and Azure that need backups as often as every 60 seconds, immutable copies and scheduled full-environment restore tests they can show an auditor. The Standard plan is $249 a month for up to 20 instances.
- AWS Backup and Azure Backup fit single-cloud teams that are happy with native scheduling and resource-level restore tests.
- Veeam, Commvault and Rubrik fit hybrid estates that still run on-prem servers.
- Whichever you choose, compliance comes from the BAA chain, your configuration and restores you can prove. No backup product is HIPAA certified.
In this article:
- Top HIPAA compliant cloud backup solutions compared
- How we evaluated these solutions
- The top HIPAA compliant cloud backup solutions
- Which HIPAA compliant cloud backup solution should you choose?
- What HIPAA requires of your backups
- What a HIPAA disaster recovery plan covers
- What makes a cloud backup solution HIPAA compliant
- What to configure in AWS and Azure
- How N2W handles HIPAA backup requirements
- Where backups go wrong (and become a penalty)
- Frequently asked questions
Top HIPAA compliant cloud backup solutions compared
There’s no official “HIPAA certified” backup product. Any vendor claiming certification is overstating it. What you’re really comparing is how well each option meets the criteria below for your AWS or Azure environment. Confirm BAA availability and scope directly with any vendor before you commit, since terms change.
The BAA column splits these tools into two groups. Services that hold a copy of your ePHI, like AWS Backup, Azure Backup and the SaaS editions of the enterprise suites, are business associates and sign a BAA. N2W runs inside your own AWS or Azure account and never receives your data, so it is not a business associate and adds no BAA to your compliance chain. AWS and Azure remain the HIPAA-eligible layer underneath; N2W automates the backup, immutability, retention and restore testing on top.
| Solution | Best for | BAA | AWS/Azure native | Immutable backups | Shortest RPO | Built-in Complete Restore testing |
|---|---|---|---|---|---|---|
| N2W | AWS and Azure cloud-native backup and DR | Not needed (data stays in your account) | AWS and Azure, agentless (Windows VSS on AWS uses a lightweight agent or AWS SSM) | Yes | 60 seconds | Yes, automate scheduled full environment restores |
| AWS Backup | Single-account AWS shops staying fully native | Via AWS BAA | AWS only | Yes (Vault Lock) | Per backup plan | Scheduled restore testing per resource; no full-environment rebuild |
| Azure Backup | Azure-only workloads | Via Microsoft BAA | Azure only | Yes (immutable vaults) | Per policy | Must incorporate Azure Site Recovery or custom scripts for restore testing support |
| Veeam | Hybrid and on-prem plus cloud | On Veeam Data Cloud (SaaS); not needed self-hosted | Multi-platform, agent-based | Yes | Per job | Requires scripting or a separate orchestration layer for full environmental restore |
| Commvault | Large enterprises standardizing on one data protection suite | On its SaaS services; not needed self-hosted | Multi-platform | Yes | Per policy | Requires additional configuration for full end-to-end cloud rebuilds |
| Rubrik | Enterprises focused on ransomware recovery | On its SaaS services; not needed self-hosted | Multi-platform | Yes | Per policy | Requires additional configuration for full end-to-end cloud rebuilds |
How we evaluated these solutions
We compared each option on the five things a HIPAA auditor or security reviewer will ask about:
- Who holds the ePHI. A vendor that stores a copy of your data is a business associate and must sign a BAA. A tool that runs in your own account is not.
- Immutability. How backups are protected from deletion or encryption during retention, and who, if anyone, can override it.
- Backup frequency. How current the retrievable copy can be, which sets your recovery point objective.
- Restore testing. Whether the tool can rehearse a recovery on a schedule and keep a record you can hand to an auditor.
- Pricing model. What you pay for, and whether the bill grows with instances or with stored data.
The top HIPAA compliant cloud backup solutions
N2W: Best for AWS and Azure cloud-native backup and DR
- Best for: Healthcare and life-sciences teams on AWS, Azure or both that want frequent backups, immutable copies and restore tests they can show an auditor.
- Key features: Backups as often as every 60 seconds. Immutable copies through S3 Object Lock or EBS Snapshot Lock in compliance mode on AWS, and a Delete lock on snapshots plus a lease on archived copies on Azure. Scheduled Recovery Scenarios that rebuild a full environment, with every run logged and emailed. Cross-account and cross-region DR copies on AWS. One console and one license for AWS and Azure.
- BAA: Not needed. N2W runs inside your own AWS or Azure account and never receives your ePHI, so it is not a business associate. Your existing AWS or Microsoft BAA covers the storage.
- Pros: Adds no business associate to your chain. Restore tests leave a logged, repeatable record. Pricing follows the number of protected instances, so it does not grow with data volume. Up to 92% storage savings on AWS and up to 70% on Azure versus keeping native snapshots long-term.
- Cons: Public cloud only, so on-prem servers need another tool. On Azure, the Delete lock and lease protect against accidental deletion and attackers without Azure permissions, but a user with the right Azure permissions can remove them; the guarantee that not even the root user can delete a copy applies to AWS compliance mode only.
- Pricing: Standard plan $249 a month for up to 20 instances. Advanced, Enterprise and Enterprise+ are quote-based.
- Bottom line: The pick when your ePHI lives in AWS or Azure and you want the backup layer to add no vendor custody and no extra BAA. More detail in How N2W handles HIPAA backup requirements below.
AWS Backup: Best for single-cloud AWS shops staying fully native
- Best for: Teams with all their ePHI in AWS that want backup managed from the AWS console.
- Key features: Central backup plans across many AWS services, AWS Backup Vault Lock in governance or compliance mode, scheduled restore testing, and cross-account and cross-region copies through AWS Organizations.
- BAA: Covered by the AWS BAA as a HIPAA-eligible service.
- Pros: Nothing to deploy, billed with the rest of your AWS usage, and wide AWS service coverage.
- Cons: AWS only. Restore testing restores each resource to a temporary copy, validates it and deletes it, so there is no ordered recovery of a full multi-instance environment. Cost grows with the data you store.
- Pricing: Pay as you go per GB-month of backup storage, plus charges for restores and cross-Region data transfer. Rates vary by resource type and Region and are published on the AWS Backup pricing page.
- Bottom line: A sound starting point when everything lives in one AWS estate and resource-level restore tests satisfy your auditors.
Azure Backup: Best for Azure-only workloads
- Best for: Teams whose ePHI sits entirely in Azure and that want backup billed through their Azure subscription.
- Key features: Recovery Services and Backup vaults, immutable vaults that can be locked, soft delete, multi-user authorization for critical operations, and Azure Site Recovery as a separate service for replication and failover.
- BAA: Covered by Microsoft’s HIPAA BAA for in-scope Azure services.
- Pros: Native to Azure, nothing to deploy, one bill.
- Cons: Azure only. Vaults are regional, so an estate spread across subscriptions and regions ends up with many vaults to manage. Full-environment restore tests need Azure Site Recovery or custom scripts.
- Pricing: A monthly protected-instance fee that depends on the size of each protected instance, plus the backup storage you consume. Published on the Azure Backup pricing page.
- Bottom line: Reasonable when Azure is your only cloud and per-VM restore checks are enough evidence for your auditors.
Veeam: Best for hybrid estates with on-prem servers
- Best for: Healthcare organizations with on-prem servers plus some cloud workloads that want one vendor across both.
- Key features: Veeam Backup & Replication for on-prem and hybrid, separate Veeam Backup for AWS and Veeam Backup for Microsoft Azure products for each cloud, immutable repositories, and Veeam Data Cloud as a SaaS option.
- BAA: Only on Veeam Data Cloud (SaaS), where Veeam holds a copy of your data. Not needed when you self-host.
- Pros: Broad workload coverage and a large base of admins who already know it.
- Cons: Agent-based for many workloads, a separate product for each cloud, and full-environment cloud restores need scripting or a separate orchestration layer.
- Pricing: Varies by product. Self-hosted products are licensed per protected workload with no published per-workload price, so most configurations are quote-based.
- Bottom line: Fits when on-prem infrastructure still holds a large share of your ePHI.
Commvault: Best for large enterprises standardizing on one suite
- Best for: Central IT teams that want one data protection suite across on-prem, cloud and SaaS workloads.
- Key features: Commvault Cloud as SaaS or self-managed software, broad workload coverage, immutable storage options, and centralized governance and reporting.
- BAA: On its SaaS services only. Not needed when you self-host.
- Pros: Breadth of workloads and governance controls in a single platform.
- Cons: Heavier architecture to deploy and run, full end-to-end cloud rebuilds need additional configuration, and consumption-based pricing on its other workloads climbs with usage.
- Pricing: VM Backup (SaaS) is published at $102.49 per 10-VM pack per month, covering Azure and Amazon EC2. Other workloads and self-managed deployments are quote-based. On the AWS and Azure marketplaces, Commvault Cloud is sold in usage credits instead.
- Bottom line: Worth a look when one central team runs data protection for every environment and has the staff to operate it.
Rubrik: Best for enterprises focused on ransomware recovery
- Best for: Large organizations whose first concern is detecting and recovering from ransomware across a mixed estate.
- Key features: Rubrik Security Cloud as the management plane, immutable backups, anomaly and threat detection on backup data, and coverage across on-prem and cloud.
- BAA: On its SaaS services only. Not needed when you self-host.
- Pros: Strong ransomware investigation and recovery tooling.
- Cons: Enterprise-oriented footprint and pricing, no published prices, and full end-to-end cloud rebuilds need additional configuration.
- Pricing: Quote-based, set by capacity plus workloads and modules.
- Bottom line: Fits large organizations that put ransomware response ahead of cloud-native depth.
Which HIPAA compliant cloud backup solution should you choose?
- All your ePHI is in AWS and per-resource restore tests are enough: AWS Backup.
- All your ePHI is in Azure, per-VM restore checks are enough, and you have a small environment: Azure Backup.
- You run on AWS and Azure, or you need scheduled full-environment restore tests as audit evidence: N2W, with one console and one license across both clouds.
- You still run on-prem servers alongside the cloud: Veeam, Commvault or Rubrik.
- You want no extra business associate in your chain: a tool that runs inside your own account and never receives your data, such as N2W or a self-hosted suite.
What HIPAA requires of your backups
Three required specifications under the contingency plan standard (45 CFR §164.308(a)(7)) drive everything:
- Data Backup Plan (§164.308(a)(7)(ii)(A)): create and maintain retrievable exact copies of ePHI. “Retrievable” is the operative word. A backup you can’t restore doesn’t satisfy the spec.
- Disaster Recovery Plan (§164.308(a)(7)(ii)(B)): procedures to restore lost data after an incident.
- Emergency Mode Operation Plan (§164.308(a)(7)(ii)(C)): keep critical processes running while you recover.
On top of those, the technical safeguards (45 CFR §164.312) apply to the backup copies themselves. The data needs access controls, audit logging, integrity protection, and encryption. Encryption carries a bonus: under the Breach Notification Rule, properly encrypted ePHI that’s exposed may qualify for safe harbor, which can take a breach notification off the table entirely.
So a HIPAA compliant backup holds ePHI under the same safeguards the original data requires, plus a recovery process you can prove works. One feature alone never gets you there.
What a HIPAA disaster recovery plan covers
Backups satisfy the Data Backup Plan spec. The Disaster Recovery Plan spec (§164.308(a)(7)(ii)(B)) asks a different question: when ePHI is lost, how do you get it back and keep care running? A workable plan covers four things.
- Disaster declaration. Name who decides an event counts as a disaster, and the criteria that trigger recovery. Without a clear trigger, teams lose hours debating whether to act.
- Disaster list. You can’t plan for every scenario, so focus on the high-impact events most likely to hit your environment: ransomware, accidental deletion, a region outage.
- Health data retrieval. Spell out how backed-up records get restored and in what priority. This is where the plan points back to your Data Backup Plan and the recovery point objective your operations can tolerate.
- Alternate site. Define where operations run while you recover. A cloud-native setup makes this far simpler than on-premises: you fail over to a standby environment inside your existing AWS or Azure account instead of standing up replacement hardware.
Write each step down, assign it an owner, and test it. An untested recovery plan fails you the same way an untested backup does, on the day you need it most.
What makes a cloud backup solution HIPAA compliant
When you’re evaluating tools, these are the criteria that actually decide it. Treat the first one as a hard filter.
1. The vendor signs a BAA. A backup provider holds a copy of your ePHI, which makes them a business associate. The 2013 Omnibus Rule extended HIPAA’s compliance obligations to business associates directly, so a cloud backup vendor carries its own liability for the ePHI it stores. Without a signed Business Associate Agreement, you can’t legally send them PHI. This eliminates a surprising number of consumer-grade and even some commercial tools before you look at any other feature. One nuance worth knowing: this requirement applies to tools that receive a copy of your PHI. Software that runs inside your own cloud account and never sends PHI to the vendor doesn’t make that vendor a business associate, so there’s no BAA to sign with them.
2. Encryption at rest and in transit. AES-256 at rest and TLS in transit is the practical baseline. Confirm you control the keys or understand who does.
3. Access controls and audit logging. Unique user IDs, role-based permissions, and logs that let you reconstruct who accessed or restored data. Auditors ask for these.
4. Immutability against ransomware. Backups are a primary ransomware target, because attackers know an organization with no clean recovery copy is more likely to pay. Immutable backups can’t be altered or deleted during a retention window, even by an admin account or a piece of malware. This is the difference between having backups and being able to recover from an attack.
5. Retention and tested restores. The solution should let you set retention policies that match your data’s requirements, and make restore testing easy enough that you do it regularly. An untested backup is a guess.
6. Data stays in covered, controlled infrastructure. The backup should land in HIPAA-eligible services and ideally inside your own cloud account, so ePHI never moves into a service the BAA doesn’t cover.
7. Documentation, audit trails, and compliance reporting. The system should maintain detailed, regularly updated compliance records of backup operations, restore events, configuration changes, and administrative actions. These audit trails should be easily exportable for auditors or internal security reviews.
8. Inventory and tagging for PHI awareness. A compliant system should support tagging or classification of backup data (e.g., marking datasets as containing ePHI). This enables organizations to maintain an updated and accurate inventory of sensitive data, apply differentiated retention policies, and ensure PHI is consistently governed across environments.
What to configure in AWS and Azure
The tool is half the job. The configuration is the other half, and it’s the part you own under the shared responsibility model. At a minimum: keep ePHI in HIPAA-eligible services, enable encryption everywhere, lock down IAM so backup and restore are least-privilege, turn on logging (CloudTrail on AWS, the equivalent on Azure), and enable immutability or vault locking on the backup target.
Platform specifics differ enough to need their own walkthroughs.
How N2W handles HIPAA backup requirements
N2W runs entirely inside your own AWS or Azure account and never receives or stores your ePHI. Your backups stay in the cloud services your existing AWS or Microsoft BAA already covers, so N2W doesn’t become another business associate in your compliance chain or hand you another BAA to negotiate and manage.
The only thing N2W receives from your environment is a license check confirming which software version you run, never your data. It backs up as often as every 60 seconds, which gives you a tight recovery point objective and satisfies the retrievable-copies spec with current data. Backups can be made immutable. On AWS, S3 Object Lock or EBS Snapshot Lock in compliance mode means not even the root user can delete a locked copy before its retention expires. On Azure, N2W applies a Delete lock to snapshots and a lease to archived copies. And the cost angle is real for healthcare teams watching cloud spend: N2W reports up to 92% storage savings on AWS, and up to 70% on Azure, versus keeping native snapshots long-term.
Because N2W runs on AWS and Azure and routes its operations through their APIs, it works entirely within those providers’ HIPAA-eligible, SOC- and ISO-audited infrastructure. AWS, for example, publishes SOC reports independently audited by Ernst & Young. That doesn’t make N2W a “HIPAA compliant product” by itself, since no backup tool is. What it means is that the platform underneath meets those audited standards, and your configuration does the rest.
N2W Software is also independently certified to ISO/IEC 27001:2022 and holds the AWS Government Software Competency, which answers the questions a security review asks of the backup vendor itself.
N2W also supports:
- Backup and restore for Amazon S3 buckets through AWS Backup, so teams can bring a bucket back to the state of a backup taken before corruption
- Scheduled Recovery Scenarios that rehearse a full-environment recovery, including the AWS network layer (VPCs, subnets, route tables and security groups)
- Clear, easy-to-access documentation of backup policies, permissions and configuration history
- Live visibility into unprotected resources across every connected account, and, from v5.0, adding them to a backup policy in one click, up to 200 at a time
Healthcare and life-sciences organizations including Johnson & Johnson run their cloud backup on N2W. You can start a free trial or book a demo to see the configuration that satisfies the Data Backup Plan and Disaster Recovery Plan specs.
Where backups go wrong (and become a penalty)
Inadequate backup and recovery shows up repeatedly in HHS settlements, usually because data couldn’t be restored after a ransomware attack or because backups were never tested. The common failures are avoidable: no immutability so ransomware encrypted the backups too, no signed BAA with the backup vendor, ePHI copied into a service the BAA didn’t cover, or a restore process nobody had run until the day they needed it.
Frequently asked questions
A signed Business Associate Agreement with the provider, encryption of the backed-up ePHI at rest and in transit, access controls and audit logging, and retrievable exact copies you can actually restore. The backup has to meet the same Security Rule safeguards as the original data.
Yes, if the vendor receives or stores your ePHI. Holding a copy of your PHI makes a vendor a business associate, and you need a signed BAA before sending it any PHI. A vendor that won’t sign one can’t legally hold your healthcare data. The exception is software that runs inside your own cloud account and never receives your PHI, like N2W: nothing leaves for the vendor to hold, so there’s no BAA to sign and your existing AWS or Microsoft BAA covers the storage.
The services are eligible under the AWS and Microsoft BAAs, but the tool alone doesn’t make you compliant. You’re responsible for configuring encryption, access controls, logging, retention, and immutability, and for keeping ePHI in covered services.
Encryption is technically an addressable specification rather than a strict requirement, but in practice you should always encrypt. The cost is low, and encrypted ePHI that’s exposed may qualify for breach-notification safe harbor.
HIPAA doesn’t name a specific frequency. It requires retrievable exact copies, and your backup frequency should follow from your own risk analysis and the recovery point objective your operations can tolerate.
No. A BAA settles who may handle your ePHI and what they must do to protect it. The Security Rule still requires you to maintain a data backup plan and a disaster recovery plan and to test them (45 CFR §164.308(a)(7)). Encryption, access control, retention and proof that your restores work are yours to configure and document, whichever vendor signs the BAA.
HIPAA sets no retention period for medical records or for the ePHI in your backups; state law generally governs that, along with your own policies. HIPAA does require you to protect that data with appropriate safeguards for as long as you keep it, through to disposal, and that includes every backup copy (45 CFR §164.530(c)). It also requires you to keep the documentation it mandates, such as your policies, procedures and risk analysis, for six years from the date it was created or last in effect, whichever is later (45 CFR §164.316(b)(2)). Set backup retention to cover the longest period that applies to the data, and keep your backup and recovery procedures for at least six years.
No backup product is HIPAA certified, so the best choice is the one that fits where your ePHI lives and what your auditors ask for. For teams on AWS, Azure or both, N2W runs inside your own account, needs no BAA because it never receives your data, backs up as often as every 60 seconds and runs scheduled full-environment restore tests. AWS Backup and Azure Backup suit single-cloud teams that want to stay native. Veeam, Commvault and Rubrik suit hybrid estates with on-prem servers.
Sources
- 45 CFR §164.308: Administrative safeguards (contingency plan, Data Backup and Disaster Recovery Plans), eCFR
- 45 CFR §164.312: Technical safeguards, eCFR
- Breach Notification Rule guidance: encryption and safe harbor, U.S. Department of Health & Human Services
- Guidance on HIPAA & Cloud Computing: business associate status, U.S. Department of Health & Human Services
- Summary of the HIPAA Security Rule, U.S. Department of Health & Human Services
- 45 CFR §164.316: Policies and procedures and documentation requirements (six-year retention of required documentation), eCFR. Link: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.316
- Does the HIPAA Privacy Rule require covered entities to keep patients’ medical records for any period of time? (FAQ), U.S. Department of Health & Human Services. Link: https://www.hhs.gov/hipaa/for-professionals/faq/does-hipaa-require-covered-entities-to-keep-medical-records-for-any-period/index.html
About the author
Catalin Voicu is a Systems Engineer at N2W who works hands-on with backup and disaster recovery for HIPAA-regulated workloads on AWS and Azure.
This article is for general informational purposes and is not legal advice. HIPAA compliance depends on your specific environment, data, and obligations. Consult a qualified healthcare compliance professional or attorney before making compliance decisions.