HHS cloud-computing guidance says a cloud service provider may be a business associate when it maintains electronic protected health information, including when the provider cannot view the information because it is encrypted. That role question is the headline fact for a cloud review.
Map the cloud service
| Review item | Evidence |
|---|---|
| Data handled | Fields, records, and environments |
| Provider role | Service description and contract |
| Access path | Users, administrators, APIs, and support |
| Agreement | Business associate analysis and contract status |
| Exit plan | Export, deletion, and access removal record |
The HHS cloud guidance should be read with the provider's actual configuration. Encryption does not remove the need for a role and contract review.
Review access separately from storage
Ask who can administer the environment, who can reset credentials, where logs are retained, and how support requests are approved. These are operational questions, not a certification claim.
Keep the answer date and the source document beside each response. Reopen the review after a material system or contract change.
FAQ
Does encryption decide the business-associate question?
No. HHS explains that a provider may still be a business associate when it maintains encrypted ePHI. Review the service role.
Is a security questionnaire enough?
Not by itself. Match answers to the contract, configuration, users, logs, and exit process.
Can a VA approve the provider?
A VA can collect the review packet. The agency's privacy, security, and contract owners decide acceptance.
Related research
Start with the HIPAA business-associate threshold and the BAA review.

