The HIPAA Security Rule (45 CFR Part 164, Subpart C) sets national standards for protecting electronic protected health information (ePHI). It applies to covered entities and, since the HITECH Act and the 2013 Omnibus Rule, directly to business associates as well.
This page is a reference map: it lists every standard in §164.308, §164.310, §164.312, §164.314 and §164.316 with its implementation specifications and whether each is Required (R) or Addressable (A) under the rule currently in force. For in-depth discussion of each category, see our pages on administrative safeguards, physical safeguards and technical safeguards.
Key points
- Five sections carry the operative standards: §164.308, .310, .312, .314 and .316.
- Where a standard has no listed specifications, the standard itself is required.
- Addressable specifications require a documented, risk-based decision — not a skip.
- The January 2025 NPRM is a proposal only; verify its current status before relying on it.
How the Security Rule is organized
§164.306 sets the general rules: ensure the confidentiality, integrity and availability of ePHI; protect against reasonably anticipated threats and impermissible uses or disclosures; and ensure workforce compliance. It also establishes flexibility of approach — you may use any security measures that reasonably and appropriately implement the standards, taking into account your size, complexity, capabilities, technical infrastructure, costs and the probability and criticality of risks (§164.306(b)).
The operative requirements then sit in five sections: administrative safeguards (§164.308), physical safeguards (§164.310), technical safeguards (§164.312), organizational requirements (§164.314) and policies, procedures and documentation (§164.316).
Required vs. addressable: the decision process
Under §164.306(d), a required specification must be implemented. An addressable specification triggers an assessment. The steps below reflect the rule text.
- 1
Assess
Determine whether the specification is a reasonable and appropriate safeguard in your environment, considering its likely contribution to protecting ePHI.
- 2
Implement if reasonable
If it is reasonable and appropriate, implement it.
- 3
Otherwise, document and choose
If not, document why, and implement an equivalent alternative measure if that is reasonable and appropriate.
- 4
Tie it to the risk analysis
The rationale should trace back to findings in your risk analysis and be retained for six years under §164.316.
Administrative safeguards — §164.308
| Standard | Implementation specification | R/A |
|---|---|---|
| Security management process §164.308(a)(1) | Risk analysis | R |
| Risk management | R | |
| Sanction policy | R | |
| Information system activity review | R | |
| Assigned security responsibility §164.308(a)(2) | (standard only) | R |
| Workforce security §164.308(a)(3) | Authorization and/or supervision | A |
| Workforce clearance procedure | A | |
| Termination procedures | A | |
| Information access management §164.308(a)(4) | Isolating health care clearinghouse functions | R |
| Access authorization | A | |
| Access establishment and modification | A | |
| Security awareness and training §164.308(a)(5) | Security reminders | A |
| Protection from malicious software | A | |
| Log-in monitoring | A | |
| Password management | A | |
| Security incident procedures §164.308(a)(6) | Response and reporting | R |
| Contingency plan §164.308(a)(7) | Data backup plan | R |
| Disaster recovery plan | R | |
| Emergency mode operation plan | R | |
| Testing and revision procedures | A | |
| Applications and data criticality analysis | A | |
| Evaluation §164.308(a)(8) | (standard only) | R |
| Business associate contracts and other arrangements §164.308(b)(1) | Written contract or other arrangement | R |
Physical safeguards — §164.310
| Standard | Implementation specification | R/A |
|---|---|---|
| Facility access controls §164.310(a)(1) | Contingency operations | A |
| Facility security plan | A | |
| Access control and validation procedures | A | |
| Maintenance records | A | |
| Workstation use §164.310(b) | (standard only) | R |
| Workstation security §164.310(c) | (standard only) | R |
| Device and media controls §164.310(d)(1) | Disposal | R |
| Media re-use | R | |
| Accountability | A | |
| Data backup and storage | A |
Technical safeguards — §164.312
| Standard | Implementation specification | R/A |
|---|---|---|
| Access control §164.312(a)(1) | Unique user identification | R |
| Emergency access procedure | R | |
| Automatic logoff | A | |
| Encryption and decryption | A | |
| Audit controls §164.312(b) | (standard only) | R |
| Integrity §164.312(c)(1) | Mechanism to authenticate electronic PHI | A |
| Person or entity authentication §164.312(d) | (standard only) | R |
| Transmission security §164.312(e)(1) | Integrity controls | A |
| Encryption | A |
Organizational requirements — §164.314
§164.314(a) specifies what a BAA must require of the business associate regarding ePHI: comply with the Security Rule, ensure subcontractors agree to the same, and report security incidents, including breaches of unsecured PHI. Group health plans must amend plan documents so the plan sponsor safeguards ePHI it receives. Details are on our business associate agreement page.
| Standard | Implementation specification | R/A |
|---|---|---|
| Business associate contracts or other arrangements §164.314(a)(1) | Business associate contracts / other arrangements / subcontractor contracts | R |
| Requirements for group health plans §164.314(b)(1) | Plan document amendments | R |
Policies, procedures and documentation — §164.316
Policies may be changed at any time as long as the changes are documented and implemented in line with the rule. If you need a starting set, our HIPAA policies and procedures service builds documents around your actual controls rather than generic templates.
| Standard | Implementation specification | R/A |
|---|---|---|
| Policies and procedures §164.316(a) | (standard only) | R |
| Documentation §164.316(b)(1) | Time limit — retain six years from creation or last effective date, whichever is later | R |
| Availability — make documentation available to those responsible for implementing it | R | |
| Updates — review periodically and update in response to environmental or operational changes | R |
The January 2025 proposed rule (NPRM)
On January 6, 2025, HHS published a notice of proposed rulemaking in the Federal Register to modify the Security Rule. Among other things, the proposal would remove the distinction between required and addressable specifications, and would add more prescriptive expectations such as written technology asset inventories and network maps, encryption of ePHI with limited exceptions, multi-factor authentication, regular vulnerability scanning and penetration testing, and periodic compliance audits.
These are proposals, not law. Until a final rule is published and takes effect, the requirements in the tables above are the ones in force. Rulemaking can change significantly or stall between proposal and final rule, so verify the current status on HHS’s website or the Federal Register before relying on any proposed provision.
Frequently asked questions
How many standards are in the HIPAA Security Rule?
Counting the administrative, physical and technical safeguards plus the organizational and documentation sections, there are 22 standards across §164.308–§164.316. Administrative safeguards have 9 standards, physical 4, technical 5, organizational 2 and documentation 2.
Is encryption required under HIPAA?
Under the current rule, encryption at rest and in transit is addressable. You must assess it and either implement it, implement an equivalent alternative, or document why neither is reasonable. Encrypted data meeting HHS guidance is also not “unsecured PHI” for breach notification purposes.
Does the Security Rule apply to paper records?
No. The Security Rule covers electronic PHI. Paper and oral PHI are protected by the Privacy Rule’s safeguards requirement at §164.530(c).
Has the 2025 Security Rule proposal become final?
Check HHS and the Federal Register for current status. This page treats it as a proposal; nothing in it should be read as a current legal requirement unless and until a final rule takes effect.
Do small practices have to meet every standard?
Yes. Every standard applies regardless of size. The flexibility of approach in §164.306(b) lets a small practice choose simpler measures, but not skip standards.
Authoritative sources
- eCFR: 45 CFR Part 164 (Security and Privacy)
- HHS: The HIPAA Security Rule
- NIST SP 800-66 Rev. 2: Implementing the HIPAA Security Rule
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.