HIPAA Security Rule access control and audit evidence
The HIPAA Security Rule allows access to ePHI only for people and software that have been granted access rights (45 CFR 164.312(a)), and requires unique user IDs, audit controls, and procedures to authorize, review and end workforce access (164.308(a)(3) and (a)(4)). Teams evidence this with authorization and termination records and activity reviews; Autharva supports it by mapping what each workforce member, vendor login and service account can reach.
Who it applies to: Covered entities (health plans, health care clearinghouses and health care providers that transmit health information electronically in HIPAA standard transactions) and their business associates that create, receive, maintain or transmit ePHI.
What the rule asks for
- 45 CFR 164.308(a)(3)Workforce security. Ensure workforce members have appropriate access to ePHI and prevent others from obtaining it, including procedures to terminate access when employment or another arrangement ends (addressable).
- 45 CFR 164.308(a)(4)Information access management. Implement policies for authorizing access to ePHI, and for establishing, documenting, reviewing and modifying each user's right of access (addressable).
- 45 CFR 164.308(a)(1)(ii)(D)Information system activity review. Regularly review records of system activity, such as audit logs and access reports (required).
- 45 CFR 164.312(a)(1)-(2)(i)Access control and unique user ID. Allow access to ePHI systems only to persons or software programs granted access rights, and assign a unique name or number to identify and track each user (required).
- 45 CFR 164.312(b)Audit controls. Implement hardware, software or procedural mechanisms that record and examine activity in systems that contain or use ePHI.
- 45 CFR 164.312(d)Person or entity authentication. Implement procedures to verify that a person or entity seeking access to ePHI is the one claimed.
Dates that matter
- HHS publishes a proposed rule to strengthen the Security Rule, including MFA and a technology asset inventory. It is proposed, not final, and the current rule remains in force.
Where access evidence usually falls short
- Termination is completed in the identity provider, but accounts in EHR modules, clearinghouse portals and vendor tools stay active.
- Shared and service accounts lack a unique, traceable owner, which weakens unique user identification.
- Access is authorized at hire but rarely reviewed or modified as clinicians and contractors change roles.
- Vendor and remote-access accounts are not tied to a responsible person inside the organization.
- Addressable specifications are skipped without a documented assessment or equivalent alternative.
How Autharva helps
- Maps every vendor login, portal account and OAuth grant to what it can reach in ePHI, with an owner.
- Closes access for departed clinicians, travelers and contractors in every app, not only the identity provider, with the owner's approval.
- Gives every AI agent a named sponsor, a scope, a record and a way to stop it, and flags any agent acting outside its scope or with no owner.
- Produces continuous evidence for access control and audit safeguards under 45 CFR 164.312.
- Runs as a container in your data center or VPC, starts read-only, and keeps patient data inside your network.
Autharva produces evidence that supports these controls. It does not by itself make an organization compliant; your auditor or examiner decides.
Evidence your examiner or auditor will ask for
- Access authorization records for workforce members with ePHI access
- Termination records showing access removed across ePHI systems
- Unique user ID listings, with shared and service accounts attributed to an owner
- Records of periodic access review and modification
- Information system activity review logs and audit control configuration
- Documented assessment for each addressable specification and any alternative adopted
Questions.
Is the 2025 proposed Security Rule in effect?+
No. HHS published the proposed rule on January 6, 2025. As of November 2026 no final rule has been published, and the current 45 CFR 164.308 and 164.312 text remains in force.
What does addressable mean for termination and access review?+
Under 45 CFR 164.306(d)(3), the entity must assess whether an addressable specification is reasonable and appropriate. If it is, implement it; if not, document why and implement an equivalent alternative if reasonable.
Do AI agents and service accounts fall under access control?+
Section 164.312(a)(1) covers access by persons or software programs. A service account or AI agent that reaches ePHI needs granted access rights like any user.
Does Autharva make us HIPAA compliant?+
No. Autharva produces evidence for access control and audit safeguards. Administrative and physical safeguards, training and contingency planning remain your responsibility.
Sources
- eCFR, 45 CFR 164.308 Administrative safeguards, current as of 2026-11-09
- eCFR, 45 CFR 164.312 Technical safeguards, current as of 2026-11-09
- eCFR, 45 CFR 164.306 Security standards: General rules, current as of 2026-11-09
- Federal Register, HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (proposed rule, 90 FR 898), 2025-01-06
Summaries are in our own words for orientation, not legal advice. Read the official text and check with your counsel.
Have a requirement we haven't covered?
Describe your environment, a system you're unsure about, or an audit finding. An Autharva SME reads every message and replies by email.
- Answered by a person, not a script.
- Please don't include passwords, customer data or account numbers.
What can your identities really reach?
Find out before an attacker or an examiner does.