Skip to content

HIPAA guide

The HIPAA Security Rule, clause by clause

Every standard and implementation specification in 45 CFR 164.308, 164.310, 164.312, 164.314 and 164.316, with its citation and whether it's required or addressable. Follow the links for what each one means, the evidence OCR asks for, and the cases where it was missing.

How the Security Rule is built

The Security Rule, 45 CFR Part 164 Subpart C, protects electronic protected health information through standards grouped into administrative, physical and technical safeguards, plus organizational requirements and documentation rules. Most standards have implementation specifications that say how to meet them. Each specification is either required or addressable.

Across the three safeguard sections there are 18 standards and 36 implementation specifications: 14 required and 22 addressable. Documentation adds three more required specifications under 164.316.

What addressable means

Not optional. Under 164.306(d)(3) you assess whether an addressable specification is a reasonable and appropriate safeguard in your environment. If it is, you implement it. If it isn't, you document why, and implement an equivalent alternative measure if that's reasonable and appropriate. HHS said in its 2025 proposal that compliance with addressable specifications is not, and should not be, optional, and the proposal would remove the distinction altogether.

Required means do it. Addressable means do it, or write down a very good reason and do something just as good.Your engineer

Every standard and specification

Linked entries have their own page with the text, what it means, the evidence OCR asks for and the cases where it was missing. The rest are summarized here and will get pages of their own.

HIPAA Security Rule standards and implementation specifications with their required or addressable status
CitationTypeName
Administrative safeguards, 164.308
164.308(a)(1)(i)StandardSecurity management process
164.308(a)(1)(ii)(A)RequiredRisk analysis
164.308(a)(1)(ii)(B)RequiredRisk management
164.308(a)(1)(ii)(C)RequiredSanction policy
164.308(a)(1)(ii)(D)RequiredInformation system activity review
164.308(a)(2)StandardAssigned security responsibility
164.308(a)(3)(i)StandardWorkforce security
164.308(a)(3)(ii)(A)AddressableAuthorization and/or supervision
164.308(a)(3)(ii)(B)AddressableWorkforce clearance procedure
164.308(a)(3)(ii)(C)AddressableTermination procedures
164.308(a)(4)(i)StandardInformation access management
164.308(a)(4)(ii)(A)RequiredIsolating health care clearinghouse functions
164.308(a)(4)(ii)(B)AddressableAccess authorization
164.308(a)(4)(ii)(C)AddressableAccess establishment and modification
164.308(a)(5)(i)StandardSecurity awareness and training
164.308(a)(5)(ii)(A)AddressableSecurity reminders
164.308(a)(5)(ii)(B)AddressableProtection from malicious software
164.308(a)(5)(ii)(C)AddressableLog-in monitoring
164.308(a)(5)(ii)(D)AddressablePassword management
164.308(a)(6)(i)StandardSecurity incident procedures
164.308(a)(6)(ii)RequiredResponse and reporting
164.308(a)(7)(i)StandardContingency plan
164.308(a)(7)(ii)(A)RequiredData backup plan
164.308(a)(7)(ii)(B)RequiredDisaster recovery plan
164.308(a)(7)(ii)(C)RequiredEmergency mode operation plan
164.308(a)(7)(ii)(D)AddressableTesting and revision procedures
164.308(a)(7)(ii)(E)AddressableApplications and data criticality analysis
164.308(a)(8)StandardEvaluation
164.308(b)(1)StandardBusiness associate contracts and other arrangements
164.308(b)(3)RequiredWritten contract or other arrangement
Physical safeguards, 164.310
164.310(a)(1)StandardFacility access controls
164.310(a)(2)(i)AddressableContingency operations
164.310(a)(2)(ii)AddressableFacility security plan
164.310(a)(2)(iii)AddressableAccess control and validation procedures
164.310(a)(2)(iv)AddressableMaintenance records
164.310(b)StandardWorkstation use
164.310(c)StandardWorkstation security
164.310(d)(1)StandardDevice and media controls
164.310(d)(2)(i)RequiredDisposal
164.310(d)(2)(ii)RequiredMedia re-use
164.310(d)(2)(iii)AddressableAccountability
164.310(d)(2)(iv)AddressableData backup and storage
Technical safeguards, 164.312
164.312(a)(1)StandardAccess control
164.312(a)(2)(i)RequiredUnique user identification
164.312(a)(2)(ii)RequiredEmergency access procedure
164.312(a)(2)(iii)AddressableAutomatic logoff
164.312(a)(2)(iv)AddressableEncryption and decryption
164.312(b)StandardAudit controls
164.312(c)(1)StandardIntegrity
164.312(c)(2)AddressableMechanism to authenticate ePHI
164.312(d)StandardPerson or entity authentication
164.312(e)(1)StandardTransmission security
164.312(e)(2)(i)AddressableIntegrity controls
164.312(e)(2)(ii)AddressableEncryption
Organizational requirements and documentation, 164.314 and 164.316
164.314(a)StandardBusiness associate contracts or other arrangements
164.314(b)StandardRequirements for group health plans
164.316(a)StandardPolicies and procedures
164.316(b)(1)StandardDocumentation
164.316(b)(2)(i)RequiredTime limit: retain six years
164.316(b)(2)(ii)RequiredAvailability
164.316(b)(2)(iii)RequiredUpdates

How to use this

Start with the required specifications under 164.308(a)(1): risk analysis, risk management, sanctions and activity review. They're the ones OCR asks about first and the ones most settlements cite. Then the technical safeguards, because they decide whether a lost laptop is a breach. Then the rest, in the order your risk analysis tells you.

With AccuSights: the platform's assessment walks every standard and specification above, tags each as required or addressable, asks the plain-English question, names the evidence that proves it, and lets your named engineer answer "how far do we take this one?"

Quick questions

How many standards are in the HIPAA Security Rule?
Eighteen across the administrative, physical and technical safeguards: nine administrative, four physical and five technical. Organizational requirements (164.314) and documentation (164.316) add further standards that are usually counted separately.
How many implementation specifications are required versus addressable?
Of the 36 implementation specifications in the three safeguard sections, 14 are required and 22 are addressable. The documentation standard adds three required specifications: the six-year time limit, availability and updates.
What is the difference between required and addressable?
A required specification must be implemented as written. An addressable one must be implemented if reasonable and appropriate; if not, you document why and implement an equivalent alternative where reasonable. Neither is optional, and the proposed 2025 update would make all of them required.
Which Security Rule requirements does OCR enforce most?
The risk analysis, by a wide margin, followed by risk management, information system activity review, access controls including termination of access, and unique user identification. Those were the findings in most 2025 and 2026 settlements.

Sources

Rules, figures and enforcement examples on this page were checked against these in October 2026. Regulations and prices change, so confirm before you rely on them.

  1. 45 CFR 164.306, security standards: general rules (eCFR)
  2. 45 CFR 164.308, administrative safeguards (eCFR)
  3. 45 CFR 164.310, physical safeguards (eCFR)
  4. 45 CFR 164.312, technical safeguards (eCFR)
  5. 45 CFR 164.316, policies, procedures and documentation (eCFR)
  6. HHS: HIPAA Security Rule NPRM fact sheet
  7. NIST SP 800-66 Rev. 2: Implementing the HIPAA Security Rule

Written by the AccuSights compliance team and updated October 2026. Figures are quoted from the sources named here and were current when checked. This page is general information, not legal advice.

Next step

Want all of it assessed, in order?

Every standard, with the evidence that proves it and an engineer to answer the hard ones. One fixed fee.

The regulator has the final say. We help interpret, scope and get you ready; we do not certify.

3-min test