Skip to content
HIPAA ComplianceConsulting

HIPAA Resource

HIPAA Cloud Security: Shared Responsibility, BAAs and Configuration

How HIPAA applies when ePHI lives in AWS, Azure, Google Cloud or SaaS — who is responsible for what, and the configuration areas that most often cause problems.

5 min read Reviewed

Putting ePHI in the cloud is permitted under HIPAA, and HHS has published guidance specifically on cloud computing. What the cloud changes is who is responsible for which safeguards. The provider secures its infrastructure; you secure how you use it. Most cloud-related exposures of health data trace back to customer-side configuration, not provider failures.

This page explains the shared responsibility model in HIPAA terms, what a BAA with a cloud service provider (CSP) does and does not do, and the configuration areas to review. Items marked as recommended practice are widely accepted security measures, not explicit requirements of the current Security Rule.

Key points

  • A CSP that creates, receives, maintains or transmits ePHI is a business associate — even if data is encrypted and it holds no key.
  • A signed BAA does not make you compliant; you remain responsible for your configurations and policies.
  • Only use services the CSP designates as covered under its BAA for ePHI.
  • Include every cloud account and SaaS tool holding ePHI in your risk analysis.

What HHS guidance says about cloud providers

HHS's cloud computing guidance makes several points that settle common debates:

  • A CSP that creates, receives, maintains or transmits ePHI on behalf of a covered entity or business associate is itself a business associate and must sign a BAA.
  • This applies even when the CSP stores only encrypted ePHI and does not have the decryption key (sometimes called "no-view" services).
  • The "conduit" exception is narrow — it covers transmission-only services such as internet service providers, not services that store ePHI.
  • Covered entities and business associates should understand the cloud environment well enough to conduct their own risk analysis and set appropriate policies.

The shared responsibility model in HIPAA terms

The split moves with the service model: in SaaS the provider handles more of the stack, in IaaS the customer handles more. The BAA and provider documentation define the specifics for each service.

Typical division of responsibility (varies by service model and contract)
AreaCloud providerCustomer
Physical data center security (§164.310)Primarily the providerVerify through provider documentation and BAA
Hypervisor and underlying infrastructureProvider—
Identity and access management (§164.312(a), (d))Provides the toolsConfigures users, roles, MFA and reviews
Encryption (§164.312(a)(2)(iv), (e)(2)(ii))Provides capabilities and key servicesEnables, configures and manages keys
Audit logging (§164.312(b))Provides logging servicesEnables, retains and reviews logs
Network controlsProvides toolsDesigns segmentation and exposure
Backups and contingency (§164.308(a)(7))Provides backup features and resilienceConfigures, tests restores and documents the plan
Application and data—Customer
Risk analysis, policies, training—Customer

BAAs with cloud providers: what to check

Our guide to the HIPAA business associate agreement covers required terms in detail.

  • Which services are covered. Major providers publish a list of services eligible for use with PHI under their BAA; using non-listed services for ePHI falls outside it.
  • Breach and security incident reporting terms required by §164.314(a)(2)(i)(C).
  • Return or destruction of data at termination, as required by §164.504(e)(2)(ii)(J) where feasible.
  • Subcontractor flow-down obligations (§164.314(a)(2)(i)(B)).
  • How the BAA is executed — many hyperscalers use a click-through BAA that must be accepted in the account console; confirm it is in place for every account holding ePHI.

Configuration areas to review

Identity and access management

  • Unique user IDs for every person (required: §164.312(a)(2)(i)); no shared root or admin credentials.
  • MFA on all console and privileged access (recommended practice).
  • Least-privilege roles; periodic access reviews; prompt removal at termination (§164.308(a)(3)(ii)(C)).
  • Service accounts and API keys inventoried, scoped and rotated.

Encryption and key management

  • Encryption at rest for storage, databases, snapshots and backups (an addressable specification; assess and document).
  • TLS for data in transit, including internal service-to-service traffic where feasible.
  • Keys managed in a key management service with access restricted and logged.
  • Encryption consistent with HHS guidance can also matter for breach notification — properly encrypted data may not be "unsecured PHI."

Logging and monitoring

  • Control-plane audit logs enabled in every region and account.
  • Data access logging for storage and databases holding ePHI.
  • Log retention set deliberately, with logs protected from tampering.
  • Alerts routed to someone who reviews them (§164.308(a)(1)(ii)(D)).

Network segmentation and exposure

  • No public storage buckets or databases holding ePHI.
  • Production separated from development and test; no real PHI in non-production.
  • Private networking for data stores; restricted inbound rules.

Backups and recovery

  • Automated backups covering all ePHI stores (§164.308(a)(7)(ii)(A)).
  • Backups isolated from production credentials to resist ransomware (recommended practice).
  • Documented and tested restore procedures (testing is addressable under §164.308(a)(7)(ii)(D)).

Including the cloud in your risk analysis

A HIPAA cloud compliance consulting engagement or a focused HIPAA technical safeguards assessment can provide an independent review.

  1. 1

    Inventory accounts and services

    List every cloud account, subscription, project and SaaS tool that stores or processes ePHI.

  2. 2

    Confirm BAA coverage

    Verify a BAA is in place and each service used is covered.

  3. 3

    Map data flows

    Document how ePHI enters, moves through and leaves the environment.

  4. 4

    Review configurations

    Compare settings against provider security benchmarks and your policies.

  5. 5

    Rate and remediate

    Record risks, likelihood and impact, and track fixes in your risk management plan.

SaaS applications: the cloud services teams forget

Discussions of HIPAA cloud security tend to focus on infrastructure platforms, but much ePHI ends up in SaaS: email, file sharing, e-signature, ticketing, CRM, call recording, messaging and, increasingly, AI assistants and transcription tools. Each of these is a cloud service under HHS's guidance, and the same rules apply — if the vendor creates, receives, maintains or transmits ePHI for you, you need a BAA and the service belongs in your risk analysis.

SaaS also shifts the configuration burden in ways that are easy to miss. The vendor runs the platform, but you usually control sharing settings, external link permissions, retention, user provisioning and audit log export. A file-sharing tool covered by a BAA can still expose ePHI if links are set to "anyone with the link" by default.

  • Keep a register of SaaS tools, noting which hold ePHI and whether a BAA is signed and which plan tier it requires.
  • Disable or restrict public and external sharing by default for tools holding ePHI.
  • Connect SaaS tools to single sign-on so terminations remove access everywhere at once (recommended practice).
  • Export or retain audit logs where the plan supports it, and know what the vendor logs on your behalf.
  • Review new tools before teams start using them — shadow IT is a common route for ePHI to land in services without a BAA.

Common cloud mistakes in healthcare environments

MistakeWhy it mattersSafeguard area
Using a service not covered by the provider's BAAePHI falls outside contractual protections§164.308(b), §164.314(a)
Publicly accessible storage or databaseDirect exposure of ePHI; likely breach analysis§164.312(a) access control
Audit logging disabled or not retainedCannot investigate incidents or show activity review§164.312(b), §164.308(a)(1)(ii)(D)
Long-lived shared admin credentialsNo individual accountability; high compromise risk§164.312(a)(2)(i), §164.312(d)
Backups never restore-testedContingency plan may fail when needed§164.308(a)(7)
Cloud accounts missing from the risk analysisRisk analysis is not enterprise-wide§164.308(a)(1)(ii)(A)

A note on proposed rule changes

Frequently asked questions

Is AWS, Azure or Google Cloud HIPAA compliant?

No cloud platform is "HIPAA compliant" on its own, and there is no HIPAA certification. Major providers will sign BAAs and offer services eligible for ePHI. Whether your use is compliant depends on your configuration, policies and risk management.

Do we need a BAA if our data is encrypted and the provider has no key?

Yes. HHS guidance states that a CSP storing ePHI is a business associate even if it cannot view the data because it lacks the decryption key.

Is encryption required for ePHI in the cloud?

Encryption at rest and in transit are addressable specifications under §164.312. Addressable means you must assess it and implement it, implement an equivalent alternative, or document why it is not reasonable and appropriate. In cloud environments, encryption is widely expected and usually practical.

Who is responsible if a misconfigured storage bucket exposes PHI?

Generally the customer that configured it, since access configuration is a customer responsibility under the shared responsibility model. Breach notification obligations would then be assessed under §164.400–414.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.