164.312(d) Person or entity authentication (R)
What the standard requires
Standard: Person or entity authentication. Implement procedures to verify that a person or entity seeking access to electronic protected health information is the one claimed.
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 2 other frameworks
| Framework | Control |
|---|---|
| HITRUST CSF v11 | 01.c.03 Privileged accounts use strong authentication |
| NIST Cybersecurity Framework (1.1, legacy) | PR.AC-7 Users, devices, and assets authenticated |
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 Technical 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.