Yes: you can host electronic protected health information (ePHI) in the cloud, but only after you sign a Business Associate Agreement (BAA) with your provider and build a documented shared responsibility security programme around it. That programme needs risk analysis, encryption, identity and access management (IAM), and logging in place before data moves. Start now with an ePHI inventory and a BAA review, and align your controls to NIST SP 800-66 Rev. 2 ahead of the proposed 2026 Security Rule changes.
TL;DR:
- Only cloud service providers with a signed Business Associate Agreement and a documented shared responsibility program can host ePHI compliantly, requiring encryption, risk analysis, and logging beforehand.
- Cloud vendors are not HIPAA certified; responsibility for security controls and configuration drift remains with the healthcare organization, even when data is encrypted or stored gobally.
- A thorough checklist—including encryption, MFA, audit logs, vulnerability scans, and incident response plans—must be verified by procurement and compliance teams before deploying ePHI in the cloud.
- Properly negotiating BAA terms such as breach notification timelines, audit rights, subcontractor obligations, and data residency is crucial to ensure legal protections and compliance during cloud use.
- Continuous risk analysis, evidence retention, and regular testing are essential, with a focus on phased migration processes that document every step and produce audit-ready evidence.
Table of Contents
- What HIPAA requires for cloud: BAAs and the shared responsibility model
- Checklist: technical and administrative controls to verify for HIPAA in the cloud
- Implementing a HIPAA-compliant cloud migration: phased steps for US health systems
- How to evaluate and negotiate a BAA and key contract terms with a cloud provider
- Operational verification and audit readiness: what evidence to collect and testing cadence
- Nexus practitioner's playbook: a concise 4-phase approach and common failure modes
- Author perspective: what compliance leaders should prioritise in 2026
- How Nexus helps: short CTA and links to services
- Sources
- FAQ
What HIPAA requires for cloud: BAAs and the shared responsibility model
There is no such thing as a government-certified HIPAA cloud. The Department of Health and Human Services has stated plainly that it does not certify any cloud service provider (CSP) as HIPAA compliant, no matter what a vendor's marketing page claims. What exists instead is a legal relationship: any CSP that creates, receives, maintains, or transmits ePHI on your behalf is a business associate, and you need a signed BAA with that CSP before any data moves.
A common misconception is the "no-view" exemption: the idea that a CSP storing only encrypted data it cannot decrypt is somehow outside HIPAA's reach. HHS has rejected that reading directly. The guidance covering encrypted ePHI without a decryption key confirms that the CSP remains a business associate regardless, with full Security Rule obligations attached.
Once the BAA is signed, responsibility splits in a specific, predictable way:
- The CSP typically secures physical data centres, host infrastructure, and the hypervisor layer.
- Your organization configures network segmentation, access controls, encryption settings, and application-level security.
- Both parties share obligations for monitoring, incident response coordination, and breach notification timelines.
- Neither party's controls cover the gap left if the other side treats their portion as "set it and forget it."
That last point matters more than most teams expect. HHS guidance explicitly warns against treating cloud configuration as a one-time task; covered entities retain accountability for application-level security and configuration drift over the life of the deployment, not just at launch. A properly signed BAA gets you the legal foundation. It does not, by itself, get you compliant infrastructure. For a deeper look at how these obligations divide in practice, see our breakdown of shared responsibility for cloud security.
Checklist: technical and administrative controls to verify for HIPAA in the cloud
Before signing off on any cloud deployment handling ePHI, procurement and compliance teams need a concrete list to check against, not a vendor's assurance. Work through these in order:
- Confirm the BAA names breach notification timelines, audit rights, and flow-down obligations to any subcontractors the CSP uses.
- Verify encryption is active for data at rest and in transit, and confirm whether your organization or the CSP holds the encryption keys.
- Require multi-factor authentication (MFA) for all administrative and clinical access, with least-privilege roles enforced by default.
- Confirm audit logging is immutable, retained long enough for investigation, and feeding a SIEM or equivalent monitoring tool.
- Check the vulnerability scanning and penetration testing schedule, and request evidence from the most recent cycle.
- Confirm an asset inventory exists covering every system that touches ePHI, updated on a defined schedule.
- Review the change management process for anything that alters network, access, or encryption configuration.
- Confirm an incident response plan exists, names roles, and has been tested, not just written.
Pro Tip: Ask for the CSP's most recent penetration test report before signing anything. A vendor that cannot produce one, or stalls when asked, has told you everything you need to know.
Customer-managed key options deserve particular attention during this review. Holding your own keys means a compromised CSP account does not automatically expose decrypted ePHI, and it also means your organization carries key-rotation and recovery responsibility that cannot be outsourced quietly.

The HHS-proposed Security Rule update aims to mandate encryption at rest and in transit, MFA for ePHI access, and periodic vulnerability scanning as baseline controls, not optional extras. That proposed rule signals where enforcement is heading, and organizations that already meet this bar face far less rework when it finalizes.
For more detail on how encryption and key management decisions hold up under audit scrutiny, our guide to patient data encryption best practices walks through the trade-offs.
Implementing a HIPAA-compliant cloud migration: phased steps for US health systems
Moving ePHI into the cloud without a phased plan is how organizations end up with partial compliance and no clear record of what was configured, when, or why. Five phases keep the work defensible:
- Scope the migration. Build a complete ePHI inventory, confirm which systems and vendors touch that data, align stakeholders across IT, compliance, and clinical leadership, and scope the BAA language before any contract is signed.
- Design the landing zone. Architect network segmentation, private endpoints, and virtual private cloud (VPC) boundaries so ePHI workloads sit apart from general business traffic, with explicit ingress and egress rules.
- Configure identity and encryption. Set up IAM with MFA and least-privilege roles, decide on customer-managed versus provider-managed encryption keys, and define secrets handling for application credentials.
- Stand up monitoring. Connect audit logging to a SIEM, schedule recurring vulnerability scans, and set a penetration testing cadence before go-live, not after an incident forces the issue.
- Validate and document. Produce the documentation an auditor will ask for, finalize a cutover checklist, and confirm a rollback plan exists if the migration needs to reverse.
Pro Tip: Treat the rollback plan as a compliance document, not just an engineering one. Auditors increasingly ask how you would have protected ePHI if the migration had failed midway.
Each phase produces its own evidence trail: inventory spreadsheets, network diagrams, IAM role definitions, scan reports, and sign-off documentation. That trail is what separates a migration that passes an OCR audit from one that merely feels secure. Our playbook for healthcare IT outsourcing expands on how these phases map to vendor engagements specifically.
How to evaluate and negotiate a BAA and key contract terms with a cloud provider
A signed BAA is only as useful as the terms inside it. Many organizations sign the vendor's standard template without checking whether it actually protects them, then discover the gaps during an incident.
Negotiate for these terms specifically:
- Breach notification windows stated in hours or days, not vague language like "promptly" or "without undue delay."
- Explicit audit rights letting your organization (or a third party on your behalf) review the CSP's controls on request.
- Subcontractor flow-down clauses confirming any downstream vendor the CSP uses is bound by the same BAA terms.
- Data residency commitments confirming ePHI stays within US-based infrastructure, since offshore processing introduces jurisdictional complications.
- Clear incident response SLAs defining who notifies whom, and within what timeframe, when something goes wrong.
Watch for red flags during negotiation. A CSP that refuses to sign a BAA at all is disqualifying, full stop, regardless of how strong its platform looks otherwise. Vague breach language that avoids committing to a specific notification window is a sign the vendor has not thought through its own incident response process. No audit access means you are taking the vendor's word for its security posture with no way to verify it, which is not a position a compliance officer can defend to a regulator. Speech-to-text and other AI-adjacent healthcare tools carry the same risk: being HIPAA-eligible is not the same as being configured correctly, as this breakdown of HIPAA speech-to-text services explains.
Operational verification and audit readiness: what evidence to collect and testing cadence
Risk analysis is the foundation everything else rests on, and HHS guidance treats it that way, framing it as ongoing rather than a one-time exercise performed before an audit. The scope and frequency should match your organization's size and complexity, but the documentation has to be continuous, not a single snapshot filed away and forgotten.
Auditors look for a specific evidence set, and gathering it after a request lands is too late. Keep these current:
- Dataflow maps showing exactly where ePHI moves and rests across your environment.
- Baseline configuration exports for every system handling ePHI.
- Audit logs retained in an immutable store, not just a rotating log file.
- Vulnerability scan and penetration test reports, with remediation tracked to closure.
- Signed BAAs and internal SOPs covering incident response and access management.
NIST SP 800-66 Revision 2, published in February 2024, maps HIPAA Security Rule standards directly to NIST SP 800–53 controls and Cybersecurity Framework subcategories. That crosswalk gives regulated entities of any size a practical way to translate legal language into technical controls they can actually implement and test.
A workable cadence: vulnerability scans monthly, penetration tests annually at minimum, and configuration drift checks whenever a change ticket touches network, access, or encryption settings. Document every remediation with a date and owner, since an open finding with no owner is what turns a routine audit into a prolonged one.
Nexus practitioner's playbook: a concise 4-phase approach and common failure modes
Most HIPAA cloud projects fail in one of three places: an incomplete ePHI inventory that misses a system nobody flagged, IAM roles configured too broadly because least privilege got skipped under deadline pressure, or missing audit evidence because logging was switched on late in the project rather than from day one.
Nexus structures cloud compliance engagements around the same four phases covered above: scoping, landing zone design, implementation of IAM and encryption, and verification through monitoring and testing. The difference in practice is sequencing discipline. Inventory and BAA scoping happen before any infrastructure decision, not alongside it, because retrofitting segmentation around ePHI you discover midway through a migration costs more than planning for it upfront.

Pro Tip: If your migration timeline has no explicit phase for evidence collection, you have planned a technical project, not a compliance one.
Engagements typically start with a compliance assessment to establish the current gap, move into the migration or configuration project itself, and continue into managed detection and response so monitoring does not lapse once the project team moves on. For a closer look at how these pieces fit together operationally, see our guide to cloud security in healthcare.
Author perspective: what compliance leaders should prioritise in 2026
Most compliance programmes still treat risk analysis as an annual checkbox. That habit will not survive the direction HHS is heading. Continuous evidence retention, not a once-a-year snapshot, is what regulators increasingly expect, and the organizations caught flat-footed will be the ones that filed their last risk analysis a year ago and called it done.
If you lead a compliance function, spend the next 90 days on three things: close any IAM gaps where access is broader than the job requires, confirm your risk analysis documentation is current and dated, and verify your monitoring actually produces evidence you could hand an auditor today, not evidence you would need a week to assemble.
— Nick - Sr. Executive
How Nexus helps: short CTA and links to services

The service consolidates cloud migration, compliance assessment, and 24/7 threat monitoring under one contract, so your team is not stitching together a migration vendor, a compliance auditor, and a monitoring provider separately. This approach provides a single point of accountability including one BAA, one escalation path, and one team that understands your environment when something needs fixing.
If you are planning a cloud migration involving ePHI or need a compliance gap assessment before your next audit cycle, review Nexus's cloud solutions and compliance services and request a scoping workshop to find out exactly where your current environment stands.
This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.
Sources
FAQ
Which cloud services are HIPAA compliant?
No cloud service is HIPAA compliant on its own; compliance depends on a signed BAA and how the service is configured. Major providers including AWS, Microsoft Azure, and Google Cloud offer BAAs and HIPAA-eligible services, but HHS is clear that no government certification exists, so the responsibility for correct configuration sits with your organization.
Is Google Cloud HIPAA compliant?
Google Cloud offers a BAA covering specific services, which makes it eligible for ePHI workloads when configured correctly. As with any provider, eligibility is not automatic compliance; your organization still has to implement encryption, IAM, and logging per the shared responsibility model HHS describes.
Is there a HIPAA compliant ChatGPT?
Standard consumer ChatGPT is not covered by a BAA and should not be used with ePHI. Enterprise versions of large language model tools may offer a BAA for specific deployments, but an organization must confirm that agreement is in place and that data handling meets Security Rule requirements before any clinical information is entered.
Is Azure cloud HIPAA compliant?
Microsoft offers a BAA covering Azure services that support HIPAA workloads, making it eligible for ePHI when properly configured. Your organization remains responsible for encryption settings, access controls, and monitoring on top of that agreement, consistent with the shared responsibility model HHS outlines for all cloud providers.
