What this checklist covers
This checklist covers the HIPAA Security Rule: the part of HIPAA that sets out how covered entities and business associates protect electronic protected health information (ePHI). It lists every standard and implementation specification in 45 CFR 164.308 (administrative), 164.310 (physical), 164.312 (technical), the business associate contract requirements in 164.308(b) and 164.314, and the documentation rules in 164.316, using the wording and the required or addressable label from the regulation text on eCFR, read on 20 November 2026.
It does not cover the Privacy Rule or the Breach Notification Rule, which have their own requirements. It is a working list for planning and evidence, not legal advice, and it does not replace the risk analysis the Security Rule requires.
If you only want the file, download the HIPAA compliance checklist in Word. It opens in Microsoft Word, Google Docs and LibreOffice.
Who it applies to
The Security Rule applies to covered entities (health plans, healthcare clearinghouses and healthcare providers that carry out standard electronic transactions) and to their business associates. An MSP that hosts, manages or can access a client’s ePHI is usually a business associate and has its own obligations under the rule, not just contractual ones. The checklist works for both sides: use it for a client’s programme and for your own.
There is no official HIPAA certification. Checklists, assessments and third-party reports can show how a programme is working, but compliance is judged against the regulation itself.
Required versus addressable
Every implementation specification in the Security Rule is marked “Required” or “Addressable” (164.306(d)). Addressable is not the same as optional:
- Required: implement it.
- Addressable: assess whether it is a reasonable and appropriate safeguard in your environment. If it is, implement it. If it is not, document why and implement an equivalent alternative measure if that is reasonable and appropriate.
Some standards, such as assigned security responsibility and audit controls, have no separate implementation specifications. The standard itself must be met (164.306(c)). They appear in the tables as “Standard”.
When choosing security measures, the rule lets you take into account your size, complexity and capabilities, your technical infrastructure, the cost of the measures and the probability and criticality of potential risks to ePHI (164.306(b)). That is why the same checklist item can look different at a three-person clinic and at a hospital group.
Administrative safeguards (45 CFR 164.308)
| Specification | Reference | Status |
|---|---|---|
| Risk analysis | 164.308(a)(1)(ii)(A) | Required |
| Risk management | 164.308(a)(1)(ii)(B) | Required |
| Sanction policy | 164.308(a)(1)(ii)(C) | Required |
| Information system activity review | 164.308(a)(1)(ii)(D) | Required |
| Assigned security responsibility (named security official) | 164.308(a)(2) | Standard |
| Authorization and/or supervision | 164.308(a)(3)(ii)(A) | Addressable |
| Workforce clearance procedure | 164.308(a)(3)(ii)(B) | Addressable |
| Termination procedures | 164.308(a)(3)(ii)(C) | Addressable |
| Isolating health care clearinghouse functions | 164.308(a)(4)(ii)(A) | Required |
| Access authorization | 164.308(a)(4)(ii)(B) | Addressable |
| Access establishment and modification | 164.308(a)(4)(ii)(C) | Addressable |
| Security reminders | 164.308(a)(5)(ii)(A) | Addressable |
| Protection from malicious software | 164.308(a)(5)(ii)(B) | Addressable |
| Log-in monitoring | 164.308(a)(5)(ii)(C) | Addressable |
| Password management | 164.308(a)(5)(ii)(D) | Addressable |
| Response and reporting (security incidents) | 164.308(a)(6)(ii) | Required |
| Data backup plan | 164.308(a)(7)(ii)(A) | Required |
| Disaster recovery plan | 164.308(a)(7)(ii)(B) | Required |
| Emergency mode operation plan | 164.308(a)(7)(ii)(C) | Required |
| Testing and revision procedures | 164.308(a)(7)(ii)(D) | Addressable |
| Applications and data criticality analysis | 164.308(a)(7)(ii)(E) | Addressable |
| Evaluation (periodic technical and nontechnical) | 164.308(a)(8) | Standard |
The security awareness and training standard (164.308(a)(5)) applies to all members of the workforce, including management. The isolating clearinghouse specification only applies where a healthcare clearinghouse is part of a larger organisation.
Physical safeguards (45 CFR 164.310)
| Specification | Reference | Status |
|---|---|---|
| Contingency operations | 164.310(a)(2)(i) | Addressable |
| Facility security plan | 164.310(a)(2)(ii) | Addressable |
| Access control and validation procedures | 164.310(a)(2)(iii) | Addressable |
| Maintenance records | 164.310(a)(2)(iv) | Addressable |
| Workstation use | 164.310(b) | Standard |
| Workstation security | 164.310(c) | Standard |
| Disposal | 164.310(d)(2)(i) | Required |
| Media re-use | 164.310(d)(2)(ii) | Required |
| Accountability (record of hardware and media movements) | 164.310(d)(2)(iii) | Addressable |
| Data backup and storage (before moving equipment) | 164.310(d)(2)(iv) | Addressable |
For a business with no premises of its own, the facility items still apply to wherever its systems are housed, which often means confirming what a hosting or cloud provider does and recording it.
Technical safeguards (45 CFR 164.312)
| Specification | Reference | Status |
|---|---|---|
| Unique user identification | 164.312(a)(2)(i) | Required |
| Emergency access procedure | 164.312(a)(2)(ii) | Required |
| Automatic logoff | 164.312(a)(2)(iii) | Addressable |
| Encryption and decryption (data at rest) | 164.312(a)(2)(iv) | Addressable |
| Audit controls | 164.312(b) | Standard |
| Mechanism to authenticate ePHI (integrity) | 164.312(c)(2) | Addressable |
| Person or entity authentication | 164.312(d) | Standard |
| Integrity controls (in transmission) | 164.312(e)(2)(i) | Addressable |
| Encryption (in transmission) | 164.312(e)(2)(ii) | Addressable |
Encryption being addressable does not mean it can be skipped without thought. If you decide not to encrypt, the rule expects a documented reason and an equivalent alternative where reasonable and appropriate.
Business associate contracts (45 CFR 164.308(b) and 164.314)
| Specification | Reference | Status |
|---|---|---|
| Written contract or other arrangement | 164.308(b)(3) | Required |
| Business associate contract terms | 164.314(a)(2)(i) | Required |
A covered entity may let a business associate handle ePHI only with satisfactory assurances, documented in a written contract or other arrangement that meets 164.314(a). A business associate needs the same assurances from any subcontractor that handles ePHI on its behalf. For an MSP, that means a business associate agreement with each healthcare client and with any of your own suppliers that can reach client ePHI.
Policies, procedures and documentation (45 CFR 164.316)
| Specification | Reference | Status |
|---|---|---|
| Policies and procedures | 164.316(a) | Standard |
| Time limit (retain for 6 years) | 164.316(b)(2)(i) | Required |
| Availability | 164.316(b)(2)(ii) | Required |
| Updates | 164.316(b)(2)(iii) | Required |
Policies and any action, activity or assessment the rule requires to be documented must be kept in written form, which may be electronic. Keep that documentation for six years from the date it was created or last in effect, whichever is later, make it available to the people who implement the procedures, and review it periodically.
How to use the checklist
- Start with the risk analysis. The rest of the checklist is easier to answer once you know where ePHI lives and which risks matter. The HIPAA security risk assessment template walks through it.
- Answer each row with evidence. For every specification record what is in place, the evidence (policy, configuration, log, contract), the owner and the date checked.
- Decide each addressable item deliberately. Record whether you implemented it, implemented an alternative, or decided it is not reasonable and appropriate, and why.
- Turn gaps into a plan. Each gap becomes a risk management action with an owner and a date, and the results feed the periodic evaluation (164.308(a)(8)).
- Keep it current. Review when systems, suppliers or services change, not only on a fixed date.
Download the Word template
The HIPAA compliance checklist has one table per safeguard family with the reference, the required or addressable label, and columns for status, evidence, owner and date. It ends with an addressable-decisions log and a sign-off block. Replace every bracketed prompt and delete rows that do not apply, recording why.
Free editable Word file. Opens in Microsoft Word, Google Docs and LibreOffice.
Common mistakes
- Treating addressable as optional. The rule requires an assessment and, where you do not implement, a documented reason and an equivalent alternative where reasonable and appropriate.
- Ticking boxes without a risk analysis. The checklist shows what the rule asks for. The risk analysis shows which risks your safeguards need to address.
- Forgetting business associate agreements with your own suppliers. Subcontractors that can reach ePHI need written assurances too.
- Undated, unowned evidence. A checklist with no evidence, owner or date is hard to rely on later.
- Losing old versions. Documentation must be kept for six years, so keep superseded versions of policies and assessments, not just the latest.
How this relates to NIST guidance
NIST SP 800-66 Rev. 2 is a resource guide for implementing the Security Rule. It maps each standard to practical activities and to the NIST Cybersecurity Framework, and it is useful when a client asks what “reasonable and appropriate” might look like in practice. NIST SP 800-30 Rev. 1 describes risk assessment methods that many teams use for the HIPAA risk analysis. The free HHS/ONC Security Risk Assessment Tool is aimed at small and medium providers. None of these replaces the regulation, which is the text this checklist follows.
Where GetCybr fits
GetCybr includes HIPAA in its framework catalogue, so an MSP or vCISO can track each Security Rule control, its evidence and its owner for every healthcare client in one place, alongside other frameworks such as NIST CSF and SOC 2. You can start with this Word checklist and move into the platform when spreadsheets and documents per client become hard to keep current.