Two lab technicians in safety glasses testing medical-device equipment, one at a computer and one adjusting an instrument rack

Medical & regulated devices

NIST SP 800-66r2: implementing the HIPAA Security Rule, explained

Last updated:

NIST SP 800-66, Revision 2, "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide," is NIST's guidance document for complying with the HIPAA Security Rule's safeguards over electronic protected health information (ePHI). Published February 2024 by NIST's Applied Cybersecurity Division and developed with the HHS Office for Civil Rights, its own Abstract states it "provides practical guidance and resources that can be used by regulated entities of all sizes to safeguard ePHI and better understand the security concepts discussed in the HIPAA Security Rule." It is explicitly not a substitute for the Security Rule itself, and using it "does not ensure or guarantee that an organization will be compliant with the Security Rule" — it supersedes SP 800-66 Revision 1 from October 2008.

Key takeaways

  • When the maker handles protected health information on behalf of a covered entity.
  • The five technical safeguard standards in §164.312 describe functions the hospital's systems must provide, and a connected device that stores or sends ePHI is one of those systems.
  • Two lookups produce the risk level.
  • Synthetic example.

Who does this cover, and why is it voluntary?

The guide applies its analysis to "regulated entities" — the Security Rule's own term covering Covered Healthcare Providers, Health Plans, Healthcare Clearinghouses, and Business Associates (including a business associate's subcontractors that handle protected health information). The underlying Security Rule itself is binding federal law on every regulated entity. NIST SP 800-66r2 itself is not: per its Authority section, the guide "may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States" (attribution to NIST is only "appreciated," not required). The guide repeatedly underscores that "the HHS Office for Civil Rights (OCR) does not prescribe any particular risk assessment or risk management methodology" — the Security Rule is, in its own words, "flexible, scalable, and technology-neutral," so an organization can follow this guide's recommended approach in whole, in part, or substitute a different one entirely.

When does HIPAA reach a device or software maker?

When the maker handles protected health information on behalf of a covered entity. The definition in 45 CFR 160.103 makes a person a business associate if, on behalf of a covered entity, it "creates, receives, maintains, or transmits protected health information" for a regulated function, and it extends the term to "a subcontractor that creates, receives, maintains, or transmits protected health information on behalf of the business associate." The test is the activity, not the product category. Typical cases for a device or health-IT supplier:

  • a cloud service that stores or relays device data containing patient identifiers for the hospital;
  • remote servicing or support sessions that can read ePHI on the device;
  • a data-analysis or monitoring service run for the provider.

A maker that only sells a device the hospital operates on its own network, with no vendor access to ePHI, does not meet the "on behalf of" part of that definition through the sale alone. Its product still sits inside the hospital's risk analysis, though. SP 800-66r2's key activities for business associate contracts (Table 16) tell covered entities to identify every vendor that provides a service on their behalf, explicitly including "Hardware/software maintenance" and cloud service providers. Where a business associate agreement exists, §164.314(a) requires it to oblige the vendor to comply with the Security Rule, flow the same terms down to subcontractors, and "report to the covered entity any security incident of which it becomes aware."

Six safeguard sections, and the required-vs-addressable split

The Security Rule organizes its requirements into six sections: Security Standards: General Rules, Administrative Safeguards (§164.308), Physical Safeguards (§164.310), Technical Safeguards (§164.312), Organizational Requirements (§164.314), and Policies and Procedures and Documentation Requirements (§164.316). Within those sections, each standard may carry one or more "implementation specifications," each marked required or addressable:

Type What a regulated entity must do
Required Comply with it directly — "similar to a standard in that a regulated entity must comply with it"
Addressable Assess whether it is "a reasonable and appropriate safeguard" in the entity's own environment; if yes, implement it; if not, document why and implement an equivalent alternative that is reasonable and appropriate

Addressable never means optional: every standard itself must still be met, and "regulated entities are required to document these assessments and all decisions." Required implementation specifications include, for example, Risk Analysis and Risk Management under the Security Management Process standard, the Response and Reporting piece of Security Incident Procedures, Unique User Identification and the Emergency Access Procedure under Access Control, and Audit Controls in full — while addressable items include things like automatic logoff, encryption of ePHI at rest, and the Facility Security Plan.

Which technical safeguards land on the device itself?

The five technical safeguard standards in §164.312 describe functions the hospital's systems must provide, and a connected device that stores or sends ePHI is one of those systems. The labels below are from the current eCFR text; the right column is the evidence a hospital's risk analysis usually asks the maker for.

§164.312 standard / implementation specification Required or addressable Evidence from the device maker
(a)(2)(i) Unique user identification Required Per-user accounts; no shared or hard-coded logins
(a)(2)(ii) Emergency access procedure Required Documented break-glass access that is logged
(a)(2)(iii) Automatic logoff Addressable Configurable session timeout
(a)(2)(iv) Encryption and decryption Addressable Storage encryption for ePHI on the device; key handling description
(b) Audit controls Standard (no separate specifications) Logs of logins, configuration changes and data exports, exportable to the hospital's log system
(c)(2) Mechanism to authenticate ePHI Addressable Integrity checks on stored records
(d) Person or entity authentication Standard (no separate specifications) Authentication of users and of connecting systems
(e)(2)(i) Integrity controls / (e)(2)(ii) Encryption in transit Addressable Current TLS configuration; certificate handling

A manufacturer disclosure statement (MDS2) is the common format for handing this evidence to hospitals, and the HSCC Joint Security Plan covers the maker's own process.

The seven-step risk assessment process

Section 3.2 lays out a risk assessment methodology, built on NIST IR 8286A and SP 800-30, that the guide is explicit a regulated entity "may choose to use" rather than must: (1) Prepare for the assessment — map where ePHI is created, received, stored, processed and transmitted, including third parties, cloud providers and remote/teleworker access; (2) Identify reasonably anticipated threats — natural, human and environmental sources, explicitly including "phishing, ransomware, or insider threat"; (3) Identify potential vulnerabilities and predisposing conditions; (4) Determine the likelihood a threat will exploit a given vulnerability, using a qualitative Very Low–to–Very High scale; (5) Determine the impact on confidentiality, integrity or availability if that exploit succeeds; (6) Determine the level of risk by combining likelihood and impact in a risk-level matrix; and (7) Document the risk assessment results — the guide recommends a risk register. Section 4 then walks through risk management: deciding which risk levels are within organizational risk tolerance, and documenting the security measures chosen to bring unacceptable risk down to that level.

Smaller regulated entities, per the guide, "may find the HHS Security Risk Assessment (SRA) Tool helpful in getting started" — though it cautions that a questionnaire-style tool "cannot identify technical vulnerabilities," so it needs to be paired with a technical method such as vulnerability scanning. The SRA Tool page on HealthIT.gov hosts the current download.

How do the likelihood and risk matrices combine?

Two lookups produce the risk level. Step 4 combines the likelihood that a threat event occurs with the likelihood that it results in adverse impact (Table 3 in the SP 800-66r2 PDF). Step 6 then combines that overall likelihood with the impact (Table 7). The values below are Table 7, the detailed risk-level matrix:

Overall likelihood ↓ / Impact → Very Low Low Moderate High Very High
Very High Very Low Low Moderate High Very High
High Very Low Low Moderate High Very High
Moderate Very Low Low Moderate Moderate High
Low Very Low Low Low Low Moderate
Very Low Very Low Very Low Very Low Low Low

In Table 3, a "High" chance that the threat occurs combined with a "High" chance it causes harm gives an overall "High"; the same "High" occurrence with only a "Low" chance of harm gives "Moderate." The guide says entities may use a different likelihood scale or risk matrix that fits their organization.

Worked example: an infusion-pump gateway with a known CVE

Synthetic example. The hospital, vendor and device are invented to show the arithmetic; they describe no real product.

  1. PrepareA hospital's ePHI inventory includes a gateway that collects infusion-pump logs with patient identifiers and forwards them to the electronic health record.
  2. ThreatExternal attackers reaching the gateway over the network.
  3. VulnerabilityThe vendor's SBOM shows a TLS library version with a published CVE in the National Vulnerability Database, and the CVE is in the CISA Known Exploited Vulnerabilities catalog.
  4. LikelihoodOccurrence "High" (active exploitation is documented). The gateway sits on a flat network, so the chance of adverse impact is "High." Table 3 gives an overall "High."
  5. Impact"High": confidentiality of many patients' records, and availability of infusion data to clinicians.
  6. Risk levelTable 7, High × High = "High."
  7. Document and treatThe risk register records the pair, the ratings and the owner. The hospital moves the gateway to a segmented clinical VLAN while the vendor ships a fixed firmware. With segmentation the chance of adverse impact drops to "Low": Table 3 gives "Moderate" overall, and Table 7 gives Moderate × High = "Moderate," which the hospital's risk tolerance (Section 4.2) may accept until the patch is installed.

What did HHS propose in 2025, and what applies today?

HHS published a notice of proposed rulemaking, "HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information," in the Federal Register on 6 January 2025, with comments closing on 7 March 2025. Among its proposals:

  • remove the distinction between "addressable" and "required" implementation specifications, so all would be required;
  • a written technology asset inventory and network map, reviewed at least once every 12 months and when the environment changes;
  • vulnerability scanning at least once every six months;
  • written verification, at least once every 12 months, that business associates have deployed the required technical safeguards.

As of 11 November 2026 the Federal Register lists the document as a proposed rule, and the eCFR text of Subpart C still carries the Required and Addressable labels. SP 800-66r2 was written against the rule in force. Device makers should still expect hospital questionnaires to follow the proposal's direction: asset inventories that list devices, regular scanning, and proof of safeguards from vendors.

What are the common pitfalls?

  • Leaving devices out of the inventory. Step 1 explicitly includes medical and IoT devices that "store, process, or transmit ePHI."
  • Reading "addressable" as optional. The entity must assess it and then implement it, or document why not and adopt an equivalent measure.
  • A questionnaire with no technical findings. The guide warns that a questionnaire tool "cannot identify technical vulnerabilities"; firmware component data and CVE matches fill that gap.
  • No business associate agreement for remote service. Vendor support access to ePHI can make the vendor a business associate, which needs a written agreement.
  • Risk ratings without a written scale. Use the guide's tables or your own, but write the definitions down.

A workable starting point

  1. Build the ePHI inventory before anything else— the guide treats mapping where ePHI is created, stored, processed and transmitted (including medical IoT and third parties) as the prerequisite for every later risk assessment step, not an optional nicety.
  2. Separate "required" from "addressable" explicitly in your documentation, and for every addressable item, keep a written reasonable-and-appropriate assessment on file — not just the control decision itself.
  3. Use Appendix D's crosswalk if you already run NIST CSF or SP 800-53 controls— the guide maps every Security Rule standard and implementation specification to Cybersecurity Framework Subcategories and SP 800-53r5 controls, so an existing control catalog doesn't need to be rebuilt from scratch for HIPAA.
  4. Treat connected medical devices as part of the ePHI boundary, not outside it— the guide specifically calls out "the myriad of medical devices (e.g., Internet of Things [IoT] used in healthcare) that can store, process, or transmit ePHI" as in-scope for both the risk assessment and the Workstation Use/Security standards.
  5. Remember this guide doesn't establish compliance on its ownFor binding requirements, device makers and health IT operators still need the Security Rule text itself (45 CFR Part 160 and Part 164, Subparts A and C) and HHS OCR's own guidance — this publication is a reading aid, not a substitute.

SoftWSP's device and firmware security assessments can supply the vulnerability evidence a HIPAA risk analysis needs for connected medical devices and the health IT systems they plug into: see Device & Firmware Security. The platform extracts a CycloneDX 1.6 SBOM from a firmware image, matches it against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report that an engineer reviews. The likelihood, impact and risk-level ratings in the hospital's analysis stay with the hospital. For the device-maker side of US medical device rules, see the FDA premarket cybersecurity guide and our medical devices page.

This guide quotes NIST SP 800-66r2's own published text (Abstract, Authority, Sections 1-5); it is not a substitute for the HIPAA Security Rule itself, HHS OCR guidance, or compliance/legal advice, and does not establish or guarantee Security Rule compliance.

Put this guide to work

Frequently asked questions

What is NIST SP 800-66r2, and what does it explicitly NOT do?

NIST Special Publication 800-66, Revision 2, "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide," is a NIST guidance document, authored by Jeffrey A. Marron of NIST's Applied Cybersecurity Division and published February 2024 (DOI 10.6028/NIST.SP.800-66r2), developed in collaboration with the Department of Health and Human Services (HHS) Office for Civil Rights (OCR). Per its own Abstract, it "provides practical guidance and resources that can be used by regulated entities of all sizes to safeguard ePHI and better understand the security concepts discussed in the HIPAA Security Rule." Its own stated purpose is explicit about its limits: "This publication is intended to aid understanding of the HIPAA Security Rule and does not supplement, replace, modify, or supersede the Security Rule itself," and its Disclaimer adds, "The use of this publication or any other NIST publication does not ensure or guarantee that an organization will be compliant with the Security Rule." It supersedes NIST SP 800-66 Revision 1 (October 2008).

Who is a "regulated entity" under the Security Rule, and is following this NIST guide mandatory?

The guide defines "regulated entity" as both covered entities and business associates (including business associates' subcontractors with access to protected health information), and lists the Security Rule's own four regulated-entity categories: Covered Healthcare Providers, Health Plans, Healthcare Clearinghouses, and Business Associates. The underlying HIPAA Security Rule itself is federal law and mandatory for all regulated entities. NIST SP 800-66r2 is not: per its Authority section, it "may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States" (attribution to NIST is merely "appreciated"). The guide also notes a flexibility baked into the Security Rule itself — "the HHS Office for Civil Rights (OCR) does not prescribe any particular risk assessment or risk management methodology" — so entities may use SP 800-66r2's recommended approach in whole, in part, or substitute a different methodology entirely.

What's the difference between a "required" and an "addressable" implementation specification under the Security Rule, per this guide?

The Security Rule groups its requirements into six sections — Security Standards: General Rules, Administrative Safeguards, Physical Safeguards, Technical Safeguards, Organizational Requirements, and Policies/Procedures/Documentation Requirements — each built from standards, many of which carry "implementation specifications," either required or addressable. Per the guide's own summary: "A required implementation specification is similar to a standard in that a regulated entity must comply with it, " while for an addressable one, "a regulated entity must (i) assess whether each implementation specification is a reasonable and appropriate safeguard in its environment... and (ii) as applicable... implement the implementation specification if reasonable and appropriate; or, if not, (1) document why it would not be reasonable and appropriate... and (2) implement an equivalent alternative measure that is reasonable and appropriate." Addressable never means optional — regulated entities must still comply with the parent standard itself, and the guide stresses that "regulated entities are required to document these assessments and all decisions."

What risk assessment process does SP 800-66r2 recommend for ePHI?

Section 3.2 lays out a seven-step process, built on NIST IR 8286A and SP 800-30, that regulated entities "may choose to use" (the guide is explicit this is not the only acceptable methodology): (1) Prepare for the assessment — map where ePHI is created, received, stored, processed and transmitted, including third parties and remote/teleworker access; (2) Identify reasonably anticipated threats, covering natural, human and environmental sources; (3) Identify potential vulnerabilities and predisposing conditions; (4) Determine the likelihood that a threat will exploit a vulnerability, using a qualitative scale (Very Low to Very High); (5) Determine the impact of a successful exploit on confidentiality, integrity or availability; (6) Determine the level of risk by combining likelihood and impact in a risk-level matrix; and (7) Document the risk assessment results, ideally in a risk register. The guide notes small regulated entities "may find the HHS Security Risk Assessment (SRA) Tool helpful in getting started," while cautioning that a questionnaire tool "cannot identify technical vulnerabilities" on its own.

Sources

  1. NIST SP 800-66r2: Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule — A Cybersecurity Resource Guide (Jeffrey A. Marron, February 2024; full text — Abstract, Executive Summary, Sections 1-5, Appendices A-G)
  2. NIST: official DOI / publication landing page for SP 800-66r2 (canonical citation, publication history, supersession of SP 800-66r1)
  3. NIST CSRC: SP 800-66 Rev. 2 publication page
  4. eCFR: 45 CFR Part 164, Subpart C — Security Standards for the Protection of Electronic Protected Health Information (§164.312 technical safeguards, §164.314 business associate contracts)
  5. eCFR: 45 CFR 160.103 — Definitions (business associate)
  6. Federal Register: HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule, 90 FR 898 (6 January 2025)
  7. HealthIT.gov: Security Risk Assessment (SRA) Tool
  8. NIST National Vulnerability Database (NVD)
Was this guide helpful?

In this cluster