# 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.

Checklist · Healthcare · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## 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

1. **Confirm in writing who the security official is, and give that person ownership of the risk analysis and the risk management plan.** (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.
2. **Set the scope to all ePHI the organization creates, receives, maintains or transmits, including copies held by cloud providers, vendors and other business associates.** (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].
3. **Build or refresh an inventory of the systems and devices that touch ePHI and a map of how ePHI flows between them.** (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].
4. **List the reasonably anticipated threats to that ePHI and the vulnerabilities in the systems that hold it, including phishing, ransomware and insider threat.** (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].
5. **For each threat and vulnerability pair, rate the likelihood and the impact, set a risk level, and record the results in a risk register.** (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].
6. **Record, for every addressable implementation specification, whether it is reasonable and appropriate, and what was done instead where it is not.** (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].
7. **Write a risk management plan that assigns each significant risk an owner, a measure and a date, and weigh the factors the rule lists when choosing measures.** (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].
8. **Make sure audit logs, access reports and security incident tracking reports are reviewed on a set schedule, and feed what they show back into the risk register.** (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.
9. **Check that each business associate handling ePHI is covered by a contract giving satisfactory assurances, and add vendor risk to the analysis.** (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].
10. **Present the results and the open risks to senior leadership and record their decisions on residual risk.** (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].
11. **Set triggers for revisiting the analysis (new systems, mergers, major incidents, new threats) and a fixed review cycle; we suggest at least once a year.** (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].
12. **Keep the risk analysis, the risk management plan and the decisions behind them in written or electronic form for six years.** (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].
13. **Run a gap check against the January 2025 proposal, without treating it as law, so the program is not caught out if a final rule follows.** (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.

## Sources

1. Electronic Code of Federal Regulations. 45 CFR 164.308, Administrative safeguards. <https://www.ecfr.gov/current/title-45/section-164.308> Checked November 14, 2026.
2. Electronic Code of Federal Regulations. 45 CFR 164.306, Security standards: General rules. <https://www.ecfr.gov/current/title-45/section-164.306> Checked November 14, 2026.
3. Electronic Code of Federal Regulations. 45 CFR 164.316, Policies and procedures and documentation requirements. <https://www.ecfr.gov/current/title-45/section-164.316> Checked November 14, 2026.
4. National Institute of Standards and Technology. SP 800-66 Rev. 2, Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide (February 2024). <https://csrc.nist.gov/pubs/sp/800/66/r2/final> Checked November 14, 2026.
5. Department of Health and Human Services, Federal Register (via GovInfo). HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (proposed rule, 90 FR 898, January 6, 2025). <https://www.govinfo.gov/content/pkg/FR-2025-01-06/html/2024-30983.htm> Checked November 14, 2026.
6. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). FY 2026 IPPS/LTCH PPS final rule (90 FR 36536, August 4, 2025), section on the Security Risk Analysis measure. <https://www.govinfo.gov/content/pkg/FR-2025-08-04/html/2025-14681.htm> Checked November 14, 2026.
7. Office of the Federal Register. Federal Register documents with RIN 0945-AA22 (search checked November 14, 2026). <https://www.federalregister.gov/api/v1/documents.json?conditions%5Bregulation_id_number%5D=0945-AA22> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-hipaa-security-risk-analysis>
Publisher: Moraph Insights
