164.308(a)(4)(ii)(B) Access Authorization (Addressable)
Implement policies for granting access to ePHI via workstation, transaction, program, or process. NIST recommends formal access request workflow with approval and provisioning records.
Source: HIPAA Security Rule, 164.308(a)(4)(ii)(B). The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open HIPAA Security Rule in the compliance library.
Applies to covered entities and business associates. An addressable specification can be met by a documented, reasonable alternative.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Provisioning logs · Identity provider / directory
- Role assignment audit trail · Identity provider / directory
periodic reviewEvidence produced at each review
- Approval records · Identity provider / directory
governing documentDocuments that govern the control
- Access request workflow tool · Policy repository / GRC workspace
- Documented addressable-specification decision: whether it is reasonable and appropriate in your environment, and if not, why, with the equivalent alternative adopted where one is · Policy repository / GRC workspace
First move
Common gaps auditors find
- Manual provisioning with no audit trail
- Approvals via informal channels
- No reconciliation of requests to grants
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet164.308(a)(4)(ii)(A) Isolating Health Care Clearinghouse Functions (Required if applicable) · 164.308(a)(4)(ii)(C) Access Establishment and Modification (Addressable)