164.312(a)(2)(i) Unique user identification (R)

HIPAA Security Rule · 2013

What the standard requires

Unique user identification (Required). Assign a unique name and/or number for identifying and tracking user identity.

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.g.02 Each user is uniquely identified before accessing operating systems
NIST Cybersecurity Framework (1.1, legacy)	PR.AC-1 Identities and credentials issued and managed

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

MFA & identity coverage

Splunk Enterprise Security

Incidents & alerts

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.

Track 164.312(a)(2)(i) with evidence behind it

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.

Start free trial All HIPAA Security Rule controls