Checklist: a HIPAA Security Rule risk analysis and risk management cycle under the rule as it stands
Thirteen steps for covered entities and business associates to meet 45 CFR 164.308(a)(1) today, each tied to the rule text, with a closing step on what the January 2025 proposal would add if it is ever finalized.
Scope of this checklist
Security officers, privacy officers and IT leaders at HIPAA covered entities and business associates. The security management process standard at 45 CFR 164.308(a)(1) has two required implementation specifications at its center: an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of electronic protected health information (ePHI), and security measures sufficient to reduce those risks and vulnerabilities to a reasonable and appropriate level [1]. The eCFR shows no substantive change to section 164.308 since 2016 [1].
Rule, method and proposal
The rule says what the analysis must achieve but not how to run it; CMS made the same point in its FY 2026 hospital payment rule [6]. Where a step below follows the rule, it names the section. Where it follows NIST Special Publication 800-66 Revision 2 (February 2024), a resource guide rather than a regulation [4], or is our own suggestion, it says so. The owner named under each step is a typical assignment, not one the rule sets, unless the step says the rule names it. The last step covers the Notice of Proposed Rulemaking published on January 6, 2025 [5]. As checked on November 14, 2026, it is still a proposal: a Federal Register search by its regulation identifier, RIN 0945-AA22, returns no final rule [7]. This checklist explains the rule; it is not legal advice, and counsel should confirm how it applies to a given organization.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
Chief executive or board-delegated executive
Required by section 164.308(a)(2): the covered entity or business associate must identify the security official responsible for developing and implementing the policies and procedures the Security Rule requires [1]. Tying the analysis to that role is our suggestion.
Security official with the privacy officer
Section 164.306(a)(1) applies the rule’s protections to all ePHI the organization creates, receives, maintains or transmits [2], and section 164.308(a)(1)(ii)(A) requires the risk analysis to cover ePHI held by the organization [1]. NIST’s guide suggests first establishing where ePHI enters, moves, is stored and leaves, including transfers to third parties such as cloud service providers [4].
IT asset management and enterprise architecture
Good practice, not a stated requirement in the current rule; it is how NIST’s guide prepares for the assessment [4]. The January 2025 proposal would make it a requirement: a written inventory giving each technology asset’s identification, version, accountable person and location, plus a network map, both reviewed at least every 12 months [5].
Security operations and system owners
Section 164.306(a)(2) requires protection against reasonably anticipated threats or hazards to the security or integrity of ePHI, and section 164.308(a)(1)(ii)(A) requires an assessment of potential risks and vulnerabilities [1] [2]. NIST names phishing, ransomware and insider threat among the threats to consider [4].
Security official, with risk management
The rule does not prescribe a method [6], so the rating approach is a choice. NIST’s guide describes determining likelihood, impact and risk level for each threat and vulnerability pair and documenting the results, for example in a risk register [4]. Good practice that would become explicit under the proposal, which lists these determinations as minimum contents of a written assessment [5].
Security official
Required by section 164.306(d)(3): an addressable specification must be assessed, then implemented if reasonable and appropriate; if not, the organization must document why and implement an equivalent alternative measure if that is reasonable and appropriate [2].
Security official with system owners and finance
Section 164.308(a)(1)(ii)(B) requires security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level [1]. Section 164.306(b)(2) lists what to take into account: size, complexity and capabilities; technical infrastructure; costs; and the probability and criticality of potential risks [2]. A written plan is our suggestion today and would be required under the proposal [5].
Security operations
Information system activity review is a required implementation specification in the same security management process standard, section 164.308(a)(1)(ii)(D) [1]. Feeding findings into the risk register is our suggestion.
Privacy officer, procurement and legal
Section 164.308(b)(1) lets a covered entity permit a business associate to handle ePHI only with satisfactory assurances under section 164.314(a) [1]. Including vendor risk in the analysis is our suggestion; the proposal would require an assessment of business associate risk based on written verification from each one [5].
Security official to the executive team
Good practice, not a stated requirement: NIST suggests sharing risk assessment results with organizational leadership, whose review supports ongoing risk management [4].
Security official
Section 164.306(e) requires security measures to be reviewed and modified as needed, section 164.308(a)(8) requires periodic technical and nontechnical evaluation in response to environmental or operational changes, and section 164.316(b)(2)(iii) requires documentation to be reviewed periodically [1] [2] [3]. The current rule sets no fixed interval; the proposal would set at least every 12 months [5].
Compliance and records management
Required by section 164.316(b): an assessment the rule requires to be documented must be kept in writing, which may be electronic, for 6 years from creation or from when it was last in effect, whichever is later [3].
Security official with counsel
Proposed only, as checked on November 14, 2026 [7]. Beyond the inventory, network map and written analysis above, the proposal would require a written risk management plan that prioritizes risks by level and is reviewed at least every 12 months, and patching within 15 calendar days for critical risks and 30 for high risks where a patch is available; it proposed the standard compliance date of 180 days after a final rule takes effect [5]. Any final rule could differ from the proposal.
Spotted an error? Tell us and we will check it and correct the checklist where needed.