164.308(b)(1) Business associate contracts
What the standard requires
Business associate contracts and other arrangements. A covered entity may permit a business associate to create, receive, maintain, or transmit electronic protected health information on the covered entity's behalf only if the covered entity obtains satisfactory assurances, in accordance with § 164.314(a), that the business associate will appropriately safeguard the information. A covered entity is not required to obtain such satisfactory assurances from a business associate that is a subcontractor.
Quoted verbatim from 45 CFR Part 164 (eCFR, as in force 2026-01-01), which is in the public domain.
Maps to 1 control in 1 other framework
| Framework | Control |
|---|---|
| HITRUST CSF v11 | 06.d.02 Business Associate Agreements are in place with covered entities and subcontractors |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
These connectors produce data relevant to HIPAA Security Rule’s Administrative Safeguards family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.