
HIPAA-compliant cloud hosting in 2026: the proposed Security Rule and what you need
· Updated
Aron Wagner
CEO & Co-Founder
HHS has proposed the most significant overhaul of the HIPAA Security Rule in over a decade. The proposed rule, published in January 2025, would remove the "addressable" implementation specifications that let covered entities document why they chose not to implement a control and still call it compliant.
It is not law yet. In its 2026 regulatory agenda, HHS moved the final rule from May 2026 to July 2027 and listed it as a long-term action. The current Security Rule stays in force until a final rule takes effect, and the final version may differ from the proposal.
Don't wait for it, though. The proposal shows where enforcement is heading, and every control it names is already good practice for ePHI. If you host healthcare data in the cloud, or if your customers do, here is what you need to know.
What the proposed rule would change
The proposal makes several changes that directly impact cloud hosting decisions:
- All implementation specifications would be required. The "addressable vs. required" distinction would go, with limited exceptions. If the rule says encryption at rest, you would encrypt at rest.
- Encryption would be explicitly mandated. ePHI at rest and in transit would have to be encrypted, with limited exceptions. Today, organizations can document why other controls make encryption unnecessary.
- Multi-factor authentication would be required for systems that access electronic protected health information (ePHI), with limited exceptions.
- Annual compliance audits would be mandatory. Organizations would audit their compliance with the Security Rule at least every 12 months.
- Business associates would verify their safeguards every year. Covered entities would get written verification, at least every 12 months, that each business associate (including your cloud provider) has deployed the required technical safeguards.
- Contingency planning would get deadlines. Business associates would have to notify you within 24 hours of activating their contingency plan, and you would need procedures to restore critical systems within 72 hours.
Technical requirements for your cloud infrastructure
Meeting the current rule, and getting ready for the proposed one, means your cloud hosting environment should provide:
Encryption everywhere. AES-256 encryption at rest for all storage volumes, databases, and backups containing ePHI. TLS 1.2 or higher for all data in transit. Manage encryption keys with proper access controls and rotation policies. The proposed rule would make encryption required; today it is an addressable specification.
Multi-factor authentication. Every user and service account accessing ePHI systems should authenticate with at least two factors, which the proposed rule would require. This applies to your application, database connections, SSH access, and cloud management console.
Comprehensive audit logging. Every ePHI access must be logged with who, when, where, and what. Logs should be tamper-resistant and kept as long as your retention policy says. Many teams keep them for six years, to match HIPAA's six-year retention rule for required documentation.
Access controls and least privilege. RBAC with minimum necessary permissions. Regular access reviews. Automatic deprovisioning when employees leave. No shared accounts.
Network segmentation. Systems containing ePHI must be isolated from non-compliant systems. Firewalls, security groups, and VPC configurations must enforce boundaries. Your cloud provider should support network-level isolation.
Backup and disaster recovery. Encrypted backups with tested recovery procedures. Your DR plan must include ePHI systems and meet documented RTO and RPO targets.
The BAA: what it is and why it matters
A Business Associate Agreement is a legal contract between a covered entity and any vendor that handles ePHI, including your cloud provider. Without a signed BAA, storing ePHI on a cloud provider is a HIPAA violation regardless of how secure the environment is.
Not all providers will sign a BAA. Some offer HIPAA-eligible services only for specific products. On AWS, only certain services are covered. Use a non-eligible service for ePHI and you are out of compliance even though AWS signed the agreement.
The proposed rule would add an annual verification requirement: confirm each year that your provider still has the required safeguards in place. Building that check into your yearly review now costs little.
Common compliance mistakes
Using non-eligible services. On hyperscalers, not every service is covered under the BAA. Using a non-eligible storage bucket or messaging queue for ePHI breaks compliance even if the rest of your infrastructure is compliant.
Assuming the provider handles everything. Your provider secures the infrastructure. You secure everything on top of it. A HIPAA-compliant cloud provider does not make your application HIPAA-compliant.
Neglecting audit logs. The current rule already requires audit controls that record activity in systems with ePHI. Teams that enabled basic logging and never reviewed the configuration are likely missing required log events.
Skipping the regular risk analysis. The current rule requires an accurate and thorough risk analysis, kept up to date, and the proposed rule would add a mandatory audit every 12 months.
Storing ePHI in unclear jurisdictions. If your cloud provider replicates data across regions, you may not know where ePHI resides. You need to know where ePHI is stored and processed to protect it, and the proposed rule would require a written asset inventory and a network map that show it. This ties directly into why your cloud provider's location matters more than ever.
Choosing a HIPAA-compliant cloud provider
Key questions: Will they sign a BAA covering all services you use? Do they support encryption everywhere and enforceable MFA? Can you control exactly where your data resides? Do they own their infrastructure, or are they reselling hyperscaler capacity? Our small business cloud security checklist covers the controls that stay on your side.
American Cloud: HIPAA hosting on infrastructure you control
American Cloud provides US-based, independently owned infrastructure with the security controls healthcare organizations need. Encryption in transit. Multi-factor authentication. Network segmentation and firewall management. And a straightforward BAA process that covers the services you use.
Because American Cloud owns its data centers and infrastructure, there is no ambiguity about where your data lives or whose compliance obligations govern it. Your ePHI stays on US soil, on hardware that is not shared with a hyperscaler's global platform.
No juggling lists of "eligible" and "non-eligible" services. No worrying about data replication to unknown regions. Transparent pricing that does not penalize you with egress fees when you need to move data for backups, audits, or DR testing.
Healthcare data demands infrastructure you can trust and verify. Build your HIPAA-compliant environment on American Cloud, with US-based infrastructure, transparent controls, and zero egress fees.