Every major cloud provider will sign a business associate agreement. That is often where the misunderstanding starts. The BAA covers the provider’s side of the arrangement — physical data centers, the underlying infrastructure, the services it designates as eligible. Everything you build on top of it, from identity policies to storage permissions to logging, remains your responsibility.
Our HIPAA cloud compliance consulting helps healthcare organizations, SaaS companies and digital health startups map that boundary precisely and verify that their side of it is configured, documented and monitored. We work with AWS, Microsoft Azure and Google Cloud environments, and with hybrid set-ups.
Key points
- A cloud provider that stores ePHI is a business associate, per HHS cloud computing guidance.
- Signing the CSP’s BAA does not make your workload compliant.
- Use only services the provider designates as covered under its BAA for ePHI.
- Your risk analysis must include cloud environments.
Service overview
The engagement focuses on the parts of HIPAA that change when infrastructure moves to a cloud platform: who is responsible for which safeguard, which services can lawfully hold ePHI under your agreement, and whether your configuration matches your policies. We review architecture, account structure, identity and access management, network exposure, encryption and key management, logging and backup.
Findings feed into your enterprise risk analysis rather than sitting in a separate cloud report. Where you need broader Security Rule coverage, we pair this with HIPAA security consulting.
The work is also forward-looking. Cloud environments change weekly: new services get enabled, new accounts are created for experiments, and engineers adopt managed AI or analytics features that may or may not be covered by the provider’s BAA. We help you put lightweight guardrails in place — a process for approving new services for ePHI, tagging of resources that hold ePHI, organization-level policies that block risky configurations, and centralized audit logs — so the environment stays within the boundaries you set after the review is finished. These guardrails are recommended practices rather than explicit HIPAA requirements, but they make the risk management obligation far easier to meet as the platform grows.
Who needs this service
- Healthcare SaaS and digital health companies whose product runs entirely in the cloud — see HIPAA consulting for SaaS companies.
- Hospitals and clinics migrating EHR, imaging or analytics workloads from on-premises data centers.
- Engineering teams that set up their cloud account before anyone thought about HIPAA.
- Organizations using multiple clouds or many accounts and subscriptions with inconsistent controls.
- Companies preparing for enterprise customer security reviews that ask detailed cloud questions.
Regulatory considerations
HHS guidance on cloud computing states that a cloud service provider that creates, receives, maintains or transmits ePHI on behalf of a covered entity or business associate is itself a business associate — even when it stores only encrypted data and holds no key. A BAA is therefore needed, and the customer remains responsible for its own Security Rule compliance, including a risk analysis covering the cloud environment under §164.308(a)(1)(ii)(A).
Cloud providers typically publish a list of services covered by their BAA. Placing ePHI in a service outside that list can put the data outside the agreement’s protection. Lists change, so they should be checked against the provider’s current documentation rather than a cached copy.
| Area | Cloud provider (typical) | Customer (typical) |
|---|---|---|
| Physical facilities and hardware | Provider | Rely on provider attestations; document in vendor review |
| Hypervisor and managed service infrastructure | Provider | Select eligible services; review provider documentation |
| Identity and access management | Provides tooling | Design roles, enforce least privilege, review access |
| Network exposure | Provides tooling | Configure security groups, firewalls, private endpoints |
| Encryption and keys | Provides encryption features and key services | Enable encryption, manage keys and key access |
| Logging and monitoring | Provides log services | Enable, retain and review audit logs (§164.312(b)) |
| Backup and recovery | Provides backup features | Configure backups, test restores, meet contingency plan (§164.308(a)(7)) |
Common cloud compliance challenges
- BAA accepted in the console for one account, while ePHI also lives in sandbox or legacy accounts not covered by the agreement.
- ePHI flowing into non-eligible services — analytics tools, AI services, logging pipelines or third-party marketplace products.
- PHI appearing in application logs, error traces or support tickets outside the intended data stores.
- Broad administrator roles used day to day, with no access reviews.
- Audit logging enabled in one region or account but not centrally collected or retained.
- Infrastructure-as-code templates that reintroduce misconfigurations after they are fixed manually.
Our methodology
We start with your architecture and data flows, then confirm which accounts, subscriptions or projects hold ePHI and whether each is covered by the provider’s BAA. Next we compare services in use to the provider’s current eligible-services list.
Configuration review uses read-only access, native posture tools (such as the provider’s security center or config rules) and your infrastructure-as-code where available. We map each finding to the relevant Security Rule safeguard and to your own policies, and separate legal requirements from recommended practices such as CIS benchmarks or continuous posture monitoring. Where third-party SaaS tools sit in your data path, we feed them into your business associate compliance process.
Typical deliverables
- Shared responsibility matrix specific to your provider(s) and services.
- Inventory of accounts, subscriptions or projects and services holding ePHI, with BAA coverage status.
- Configuration findings mapped to Security Rule safeguards, with remediation guidance.
- Cloud-specific inputs to your risk analysis and risk register.
- Recommended guardrails — baseline policies, logging architecture, tagging for ePHI resources.
Engagement process
- 1
Architecture walkthrough
Your engineers walk us through the environment, data flows and deployment process.
- 2
BAA and service coverage check
Confirm BAA execution and compare services in use with the provider’s eligible list.
- 3
Configuration review
Read-only review of identity, network, encryption, logging and backup settings.
- 4
Findings session
Review draft findings with engineering to confirm accuracy and agree priorities.
- 5
Report and follow-up
Deliver the responsibility matrix, findings and roadmap; optional re-review after fixes.
Cost factors
Scope depends on the number of cloud providers, accounts and environments, the breadth of services in use, the availability of infrastructure-as-code, and whether the work includes the application layer or only infrastructure. Multi-cloud estates and large account sprawl take longer. Our HIPAA cloud security resource covers the topic in more depth.
Frequently asked questions
Is AWS, Azure or Google Cloud HIPAA compliant?
No cloud platform is “HIPAA compliant” on its own, and there is no official HIPAA certification. Each provider offers a BAA and designates eligible services. Whether your use of the platform is compliant depends on how you configure and operate it.
Do we need a BAA if we encrypt everything and keep the keys?
According to HHS cloud computing guidance, yes. A provider that maintains ePHI is a business associate even if it cannot decrypt the data.
Can we use the provider’s AI or analytics services with PHI?
Only if the specific service is covered under your BAA and your risk analysis supports its use. Check the provider’s current eligible-services list; it changes over time.
Will a third-party posture management tool make us compliant?
Posture tools help identify misconfigurations and are a useful practice, but they do not cover policies, risk analysis, workforce training or vendor management, and they still need someone to act on the findings.
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.