A SaaS company that hosts, processes or can access PHI for a healthcare customer is almost always a business associate under §160.103. That status comes from what you do with the data, not from whether you signed a BAA: the obligations attach when you start handling PHI for a covered entity or another business associate. Signing the agreement documents the relationship; it does not create it.
Business associates are directly liable for complying with the Security Rule and for certain Privacy Rule and breach notification obligations. For a SaaS company, that means the Security Rule applies to your production environment, your engineering access, your logging and your vendors — and your customers will increasingly ask you to prove it. HIPAA compliance for SaaS companies is mostly about making those obligations operational inside a modern software delivery process.
Key points
- Handling PHI for a covered entity usually makes you a business associate, BAA or not.
- A cloud provider’s BAA covers its layer only; your configuration and access controls are yours.
- Each BAA you sign can add commitments beyond the regulation, such as shorter breach notice windows.
- Using customer PHI to train or improve models is limited by what the BAA permits.
Who is responsible for what
HHS guidance on cloud computing makes clear that a cloud service provider that creates, receives, maintains or transmits ePHI is a business associate, even if it stores only encrypted data without the key. For a SaaS company running on a public cloud, this produces a three-layer arrangement in which responsibilities need to be explicit.
| Layer | Typically responsible | Examples of controls |
|---|---|---|
| Physical infrastructure and core cloud services | Cloud provider (your subcontractor business associate) | Data center physical security, hypervisor isolation, hardware disposal |
| Your application and cloud configuration | Your SaaS company (business associate) | Identity and access management, encryption settings, logging, network rules, backups, tenant isolation, vulnerability management |
| Customer use of your product | Customer (covered entity or upstream business associate) | Provisioning their users, role assignments, minimum necessary use, their own risk analysis |
Where SaaS risk concentrates
Engineering and support access
Standing production access for developers, broad support-tool access to customer records and shared admin credentials are the most common findings in SaaS assessments. Just-in-time access, break-glass procedures and logged support sessions map directly to the access control and audit control standards in §164.312.
Multi-tenancy
A defect that exposes one customer’s data to another is both a security incident and a potential breach for each affected customer. Tenant isolation deserves explicit testing and a place in your risk analysis, not just an architecture diagram.
Sub-processors and the SaaS toolchain
Logging platforms, error trackers, customer support desks, email delivery services and AI APIs can all receive PHI, often unintentionally through log lines or support tickets. Each one that does is a subcontractor that needs a BAA under §164.502(e)(1)(ii) and §164.308(b)(2), or the data flow needs to stop.
AI features and secondary use
A business associate may use and disclose PHI only as its BAA permits or requires. Training models, building benchmarks or creating product analytics from customer PHI needs a contractual basis, or properly de-identified data under §164.514(b). Customers increasingly negotiate these terms explicitly.
Reading the BAAs you sign
Large health system customers often present their own BAA templates. These frequently go beyond the minimum provisions in §164.504(e) and §164.314(a). Before signing, product and legal teams should check commitments such as:
- Breach and incident notification windows much shorter than the regulatory outer limit of 60 days after discovery.
- Restrictions on offshore access or storage, which HIPAA itself does not impose.
- Audit rights, security questionnaire obligations and required attestations.
- Indemnification, cyber insurance minimums and data return or destruction timelines at termination.
SOC 2, HITRUST and HIPAA
SaaS buyers often ask for a SOC 2 report or HITRUST certification. These are third-party attestations against their own frameworks; they are valuable evidence of good practice, but HIPAA does not require either, and neither is a HIPAA certification (there is none). A SOC 2 report also does not replace your own HIPAA risk analysis, which is a specific regulatory requirement. Many SaaS companies run them in parallel, mapping one control set to both.
How we tailor SaaS engagements
We typically start with a HIPAA security risk assessment built around your architecture — cloud accounts, CI/CD, identity provider, support tooling and data stores — rather than a generic checklist. A HIPAA technical safeguards assessment goes deeper on access, audit, integrity and transmission controls where customers are scrutinizing them.
For teams rethinking their infrastructure, HIPAA cloud compliance consulting clarifies shared-responsibility boundaries and subcontractor BAAs. Our HIPAA compliance for software companies guide covers the engineering practices in more depth.
Keeping compliance current as the product ships
SaaS environments change weekly. A risk analysis completed before a major architecture change, a new data store or a new AI integration may no longer be accurate, and the Security Rule expects periodic technical and nontechnical evaluation under §164.308(a)(8) in response to environmental or operational changes. The practical answer is to build HIPAA checkpoints into existing engineering processes rather than running a separate compliance track.
- Add a short PHI impact question to design reviews: does this feature create a new store, flow or vendor for PHI?
- Require a BAA check before any new third-party service receives production data.
- Scrub PHI from logs, error reports and analytics events by default, and test that the scrubbing works.
- Record risk decisions in the same tracker engineers use, so remediation has owners and due dates.
- Review the risk analysis after significant releases, not only on an annual calendar.
Starting checklist for SaaS teams
- Document whether you act as a business associate, a subcontractor to one, or both, for each product line.
- List every service in your stack that could receive PHI, including logs, error tracking and support tools, and confirm BAAs or remove the data flow.
- Remove standing production access where feasible and log every support session that touches customer data.
- Test tenant isolation and record the results.
- Build a breach notification runbook that meets your tightest customer BAA deadline, not only the regulation.
- Decide in writing what your contracts allow regarding AI training and secondary use of customer data.
Frequently asked questions
Are we a business associate if we never look at the data?
Usually yes. Storing or maintaining PHI on behalf of a covered entity makes you a business associate even if you do not view it. HHS cloud guidance applies this even to providers holding only encrypted data without the key. The narrow conduit exception covers transmission-only services, not storage.
Does using AWS, Azure or Google Cloud make us HIPAA compliant?
No. Those providers will sign a BAA for eligible services, but compliance depends on how you configure and operate your environment. Your risk analysis, access controls, logging and policies remain your responsibility.
Can we use customer PHI to train our AI models?
Only if your BAA permits that use, or if the data is properly de-identified under the HIPAA standard. This is a contract and legal question as much as a technical one, so involve counsel.
Will a SOC 2 report satisfy healthcare customers?
It often helps in procurement, but it is not a HIPAA requirement or a substitute for your HIPAA risk analysis. Many customers will ask for both a SOC 2 report and evidence of HIPAA-specific controls.
What should our breach notification window be?
HIPAA requires a business associate to notify the covered entity without unreasonable delay and no later than 60 days after discovery. Many BAAs require much faster notice, so your process should meet the shortest contractual commitment you have signed.
Authoritative sources
- HHS — Guidance on HIPAA and Cloud Computing
- HHS — Sample Business Associate Agreement Provisions
- NIST SP 800-66 Rev. 2
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.