164.308(a)(2) Assigned security responsibility (R)
What the standard requires
Standard: Assigned security responsibility. Identify the security official who is responsible for the development and implementation of the policies and procedures required by this subpart for the covered entity or business associate.
Quoted verbatim from 45 CFR Part 164 (eCFR, as in force 2026-01-01), which is in the public domain.
Maps to 2 controls in 1 other framework
| Framework | Control |
|---|---|
| HITRUST CSF v11 | 00.a.04 Information security program roles and responsibilities are documented |
| 05.a.01 Information security responsibilities are clearly defined and allocated |
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.