The HIPAA Security Rule is a federal regulation. Covered entities and business associates must comply with it. NIST SP 800-53 is a catalog of security and privacy controls written for federal information systems. A private hospital is not legally required to implement it. Both appear in almost every healthcare security assessment, and reports regularly blur the line between them.
The distinction matters because it changes what a finding means. “Not compliant with the Security Rule” is a legal exposure. “Below the SP 800-53 moderate baseline” is a benchmark gap. This article sets out what each one is, how they fit together, and how to write about them so that a reader knows which kind of statement they are looking at.
The two documents at a glance
| HIPAA Security Rule | NIST SP 800-53 Rev. 5 | |
|---|---|---|
| What it is | Federal regulation at 45 CFR Part 164, Subpart C | A catalog of security and privacy controls, published by NIST |
| Who must follow it | Covered entities and business associates handling ePHI | Federal agencies and their systems; voluntary for everyone else |
| Scope | Electronic protected health information | Any information system |
| Structure | Standards with required or addressable implementation specifications, in administrative, physical, and technical safeguards | Twenty control families; baselines (low, moderate, high) selected by impact level |
| Specificity | Technology neutral; states outcomes, not products | Detailed control statements with enhancements |
| Enforced by | HHS Office for Civil Rights | Not enforced outside federal use; adopted by choice or by contract |
What the Security Rule actually requires
The Security Rule, published in 2003 and extended to business associates by the HITECH Act of 2009 and the 2013 Omnibus Final Rule, requires regulated entities to ensure the confidentiality, integrity, and availability of all ePHI they create, receive, maintain, or transmit; protect against reasonably anticipated threats and impermissible uses or disclosures; and ensure workforce compliance.
It does that through standards grouped as administrative safeguards (such as the security management process with its required risk analysis, assigned security responsibility, workforce security, incident procedures, and contingency planning), physical safeguards (facility access, workstation security, device and media controls), and technical safeguards (access control, audit controls, integrity, authentication, transmission security). Each standard has implementation specifications marked required or addressable. Addressable does not mean optional: the entity must implement the specification if it is reasonable and appropriate, or document why it is not and adopt an equivalent measure.
The Rule is deliberately flexible and technology neutral. It tells an entity to consider its size, complexity, infrastructure, the cost of measures, and the probability and criticality of risks when choosing safeguards. It does not say which product, which encryption algorithm, or how many characters in a password. That flexibility is why organizations reach for a control catalog.
Where NIST SP 800-53 comes in
SP 800-53 Rev. 5 answers the question the Security Rule leaves open: what does a reasonable and appropriate control look like in detail? Its control families cover the same ground as the Rule’s safeguards, from access control and audit and accountability to contingency planning, incident response, and system and communications protection, with specific statements and enhancements for each.
NIST wrote the bridge itself. SP 800-66 Rev. 2, Implementing the HIPAA Security Rule, is NIST’s practical guide for regulated entities, and it points to SP 800-53 controls and other NIST resources as ways to meet each standard. Using the catalog this way is what the Security Rule’s flexibility invites: the law sets the outcome, the catalog supplies candidate controls, and the entity’s risk analysis decides which ones are reasonable and appropriate.
A moderate-impact baseline is a common starting point for a hospital, because loss of EHR confidentiality, integrity, or availability could cause serious harm to patients and operations. Tailoring then removes or adjusts controls that do not fit.
How to write about them accurately
The case study linked below assessed a hospital’s electronic health record controls as though the hospital were a U.S. organization subject to HIPAA and HITECH. It applied a tailored SP 800-53 moderate baseline as the benchmark and was explicit on one point: the baseline is a security benchmark, not a claim that every private hospital is legally required to adopt SP 800-53. That one sentence keeps the report honest, and it is the sentence most reports leave out.
- Say “required by the Security Rule” only for a standard or a required implementation specification, and cite the section, such as 45 CFR 164.308(a)(1) for risk analysis.
- Say “addressable” when it is, and record the reasonable-and-appropriate decision rather than treating addressable as skipped.
- Say “below the SP 800-53 baseline we selected” for catalog gaps, and name the baseline and the tailoring.
- Keep the two kinds of finding in separate sections or separate columns, so that legal exposure and benchmark gaps are never summed into one number.
- Anchor every recommendation to the risk analysis. Under the Rule, the risk analysis is what justifies which safeguards are reasonable and appropriate, so a recommendation with no risk behind it has no legal basis either.
Where NIST guidance does carry legal weight
Two places. First, if a regulated entity adopts a NIST baseline in its own policy, the policy becomes part of what the Office for Civil Rights evaluates, because the Rule requires entities to implement and follow their documented policies. Second, HHS has proposed modifications to the Security Rule to strengthen ePHI cybersecurity; its summary page points readers to the Security Rule notice of proposed rulemaking. Until a final rule takes effect, the current Rule governs, and a report should say which version it assessed against.
See it applied
- EHR Security Controls Assessment: HIPAA and NIST AppliedMy case study: HIPAA, HITECH, NIST CSF 2.0, SP 800-53, and SP 800-66 applied to a hospital EHR environment, with the law-versus-benchmark distinction made explicit.
- PCI DSS Scoping: Which SAQ Do You Need?Another case where a contractual standard and a security benchmark get confused.
- Cybersecurity workAll nine case studies.
Frequently asked questions
- Is NIST SP 800-53 required for HIPAA compliance?
- No. The Security Rule is the legal requirement. SP 800-53 is a voluntary control catalog that many regulated entities use to decide what reasonable and appropriate safeguards look like, and NIST SP 800-66 Rev. 2 points to it for that purpose.
- What is the difference between required and addressable in the HIPAA Security Rule?
- Required implementation specifications must be implemented. Addressable specifications must be implemented if reasonable and appropriate; otherwise the entity must document why not and adopt an equivalent alternative. Addressable never means optional.
- Who enforces the HIPAA Security Rule?
- The HHS Office for Civil Rights. Since the HITECH Act, business associates are directly liable for Security Rule violations, not only covered entities.
- Which NIST document is written for HIPAA?
- NIST SP 800-66 Rev. 2, Implementing the HIPAA Security Rule: A Cybersecurity Resource Guide, published in 2024. It walks through the Security Rule standards and points to NIST resources, including SP 800-53 controls, for meeting them.
Sources
- HHS: Summary of the HIPAA Security RuleWho is covered, the general rules, the safeguards, and required versus addressable.
- 45 CFR Part 164, Subpart C: Security Standards for the Protection of ePHIThe regulation text, including sections 164.306 through 164.316.
- NIST SP 800-66 Rev. 2: Implementing the HIPAA Security RuleNIST’s resource guide for regulated entities.
- NIST SP 800-53 Rev. 5: Security and Privacy Controls for Information Systems and OrganizationsThe control catalog.