← HIPAA · Technical safeguards
164.312(a)(1) — Access control — unique identification and emergency access (R/A)
Requirement
Implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to authorised persons or software programmes, including unique user identification and emergency access procedures, with automatic logoff and encryption/decryption as addressable specifications.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.5.15 | Access control | access-control authentication |
| NIST CSF 2.0 | PR.AA-01 | Identities and credentials are managed | access-control authentication |
| SOC 2 | CC6.1 | Logical access provisioning and restriction | access-control authentication |
| GDPR | Art.29 | Processing under the authority of the controller | access-control |
| CCPA/CPRA | 1798.100(e) & 1798.150 | Reasonable security procedures | access-control |
| SOC 2 | CC6.2 | Registration and authorisation of new users | access-control |
| ISO 27001 | A.5.3 | Segregation of duties | access-control |
| ISO 27001 | A.5.17 | Authentication information | authentication |