Skip to main content
Practitioner template

HIPAA Security Risk Assessment Template

A HIPAA security risk analysis worksheet that follows the elements HHS says every risk analysis must cover, from scope and ePHI inventory to likelihood, impact, risk level and the risk management plan, with a free editable Word file.

By Reviewed 20 November 2026For MSPs and MSSPs running risk analyses for healthcare clients, vCISOs acting as security official, Small and mid-sized practices and business associates

What a HIPAA security risk assessment is

The HIPAA Security Rule requires covered entities and business associates to “conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information” they hold. That is the risk analysis implementation specification in 45 CFR 164.308(a)(1)(ii)(A), and it is marked Required. Most people call the result a security risk assessment (SRA). It feeds the risk management specification next to it, which requires security measures that reduce risks and vulnerabilities to a reasonable and appropriate level.

This template follows the elements in the HHS Office for Civil Rights Guidance on Risk Analysis. HHS is clear that there are numerous methods and no single method that guarantees compliance, so the template gives you a structure and leaves the scoring method to you. It is not legal advice.

If you only want the file, download the HIPAA security risk assessment template in Word. The guidance below explains each section.

Who needs one

Any covered entity or business associate that creates, receives, maintains or transmits ePHI. For an MSP that manages a clinic’s systems, that usually means two assessments: the client’s, which you may run for them, and your own, because as a business associate you hold or can reach their ePHI.

What HHS says a risk analysis must incorporate

The HHS guidance lists the elements below. The template has a section for each.

  1. Scope of the analysis. All ePHI the organisation creates, receives, maintains or transmits, in every form of electronic media, and every location and system that touches it.
  2. Data collection. Identify where ePHI is stored, received, maintained or transmitted, using interviews, documentation reviews and past projects, and document what you find.
  3. Threats and vulnerabilities. Identify and document reasonably anticipated threats to ePHI and the vulnerabilities that, if exploited, would create a risk of inappropriate access or disclosure.
  4. Current security measures. Assess and document the measures in place, whether the measures the rule requires are in place, and whether they are configured and used properly.
  5. Likelihood of threat occurrence. Estimate the probability of each threat and vulnerability combination, as 164.306(b)(2)(iv) requires you to consider.
  6. Potential impact. Assess the magnitude of impact on confidentiality, integrity and availability if a threat exploits a vulnerability, using qualitative, quantitative or combined methods.
  7. Level of risk. Assign a risk level to every threat and vulnerability combination, for example from the likelihood and impact values, and document the corrective actions.
  8. Finalise documentation. The rule requires the risk analysis to be documented but does not require a specific format (164.316(b)(1)).
  9. Periodic review and updates. The risk analysis should be ongoing. The Security Rule does not specify how frequently to perform it; review it when the environment or operations change, such as new systems, new locations or a security incident.

Section by section

1. Scope of the analysis

Name the organisation, the assessor, the date and every location, system, service and supplier in scope, including remote and home working, mobile devices and cloud services. Record anything excluded and why.

2. Where ePHI is created, received, maintained or transmitted

An inventory table: system or data store, type of ePHI, where it is hosted, who can access it, how it moves in and out, and the business associate involved if any. This is the step most assessments skip and most problems trace back to.

3. Threats and vulnerabilities

For each system, list reasonably anticipated threats (for example ransomware, phishing, lost or stolen devices, insider misuse, supplier compromise, power or hardware failure, fire or flood) and the vulnerabilities that would let them cause harm (for example unpatched systems, shared accounts, no multi-factor authentication, unencrypted laptops, untested backups).

4. Current security measures

Record the safeguards in place for each threat and vulnerability pair and whether they work as intended. The HIPAA compliance checklist lists every administrative, physical and technical specification to check against, marked required or addressable.

5. Likelihood, impact and risk level

Score likelihood and impact on a simple scale and combine them into a risk level. The template uses a 1 to 5 scale for each, multiplied, with bands you can adjust. Write down your method so the next assessment uses the same one. NIST SP 800-30 Rev. 1 describes the approach in detail.

6. Risk management plan

For each risk above your tolerance, record the treatment, owner, target date and the residual risk once the action is complete. This is the bridge to the risk management specification (164.308(a)(1)(ii)(B)). Many teams keep these actions in a risk register.

7. Review and updates

Record when the assessment was approved, by whom, what triggers the next review and where previous versions are kept. Documentation required by the Security Rule must be retained for six years from creation or last effective date, whichever is later (164.316(b)(2)(i)).

Download the Word template

The HIPAA security risk assessment template has the seven sections above, an ePHI inventory table, a threat and vulnerability table with likelihood, impact and risk level columns, a risk management plan table and an approval block. Replace every bracketed prompt and keep previous versions.

Free editable Word file. Opens in Microsoft Word, Google Docs and LibreOffice.

Common mistakes

  • Running a compliance gap check instead of a risk analysis. A checklist of safeguards is useful, but the rule asks for an assessment of risks to your ePHI.
  • Incomplete scope. Missing remote workers, mobile devices, cloud apps or a supplier’s systems leaves the analysis inaccurate.
  • No risk management plan. Identifying risks without owners and dates does not meet the risk management specification.
  • Assuming a fixed annual cycle is all that is needed. HHS expects the analysis to be updated when the environment or operations change.
  • Treating a tool’s output as the whole answer. The HHS/ONC tool itself reminds users that its survey alone may not identify all risks.

Free tools from HHS and NIST

The HHS/ONC Security Risk Assessment Tool is a free desktop application and workbook designed for small and medium providers. It stores answers locally and HHS does not collect them. NIST SP 800-66 Rev. 2 explains how to carry out the risk analysis and risk management steps of the Security Rule. This Word template suits teams who want an editable document they can brand, version and hand to a client.

Where GetCybr fits

GetCybr includes HIPAA in its framework catalogue and a risk register, so an MSP or vCISO can run the risk analysis for each healthcare client, link each risk to its Security Rule controls and evidence, and track treatment actions to completion. You can start with this Word template and move into the platform when you are managing several clients’ assessments at once.

Run the workflow across every client

GetCybr gives MSPs one workspace for assessments, evidence, roadmaps and client reporting.

Become a partner