Administrative safeguards are the management side of the Security Rule: the policies, procedures and decisions that govern how security measures are selected, implemented and maintained, and how the workforce behaves. They make up more than half of the Security Rule’s implementation specifications, and they are where most OCR findings originate.
§164.308 contains nine standards. This guide takes each in turn and focuses on ownership and evidence — the two things that most often go missing. For the full list of Required and Addressable designations across the whole rule, see Security Rule requirements.
Key points
- Nine standards: eight in §164.308(a) plus business associate contracts in §164.308(b).
- Risk analysis and risk management drive every other decision.
- Contingency plan backup, disaster recovery and emergency mode specifications are all required.
- A named security official is required; the role can be combined with the privacy official in small organizations.
The nine standards and who usually owns them
| # | Standard | Citation | Typical owner |
|---|---|---|---|
| 1 | Security management process | §164.308(a)(1) | Security official with executive sponsor |
| 2 | Assigned security responsibility | §164.308(a)(2) | Leadership / board |
| 3 | Workforce security | §164.308(a)(3) | HR with IT |
| 4 | Information access management | §164.308(a)(4) | IT with system owners |
| 5 | Security awareness and training | §164.308(a)(5) | Security official with HR |
| 6 | Security incident procedures | §164.308(a)(6) | Security official / IT |
| 7 | Contingency plan | §164.308(a)(7) | IT with operations leadership |
| 8 | Evaluation | §164.308(a)(8) | Security official, often with an independent assessor |
| 9 | Business associate contracts and other arrangements | §164.308(b)(1) | Compliance / legal with procurement |
1. Security management process
This standard requires policies and procedures to prevent, detect, contain and correct security violations. All four specifications are required: risk analysis, risk management, a sanction policy and information system activity review.
- Risk analysis: an accurate and thorough assessment of risks to all ePHI — see the risk assessment checklist
- Risk management: security measures sufficient to reduce risks to a reasonable and appropriate level, tracked in a living plan
- Sanction policy: graduated consequences for workforce members who violate security policies, applied consistently and documented
- Activity review: regular review of audit logs, access reports and security incident tracking reports
2. Assigned security responsibility
Identify the security official responsible for developing and implementing security policies and procedures. The rule requires one accountable individual, not a committee. In smaller organizations the same person often serves as privacy official; in larger ones the roles are usually separate. Record the designation in writing and give the person enough authority and time to do the job.
3. Workforce security
Ensure that workforce members have appropriate access to ePHI and prevent those who should not have access from obtaining it. All three specifications are addressable.
- Authorization and/or supervision: who may work with ePHI, and supervision of those (such as maintenance staff) who work near it
- Workforce clearance procedure: role-appropriate background screening
- Termination procedures: same-day removal of access, return of devices and badges; a gap here is one of the most common findings
4. Information access management
Implement policies for authorizing access to ePHI consistent with the Privacy Rule. Health care clearinghouses that are part of a larger organization must isolate clearinghouse functions (required). Access authorization and access establishment and modification are addressable, but in practice nearly every organization needs both: a request-and-approval workflow, and periodic access reviews to catch privilege creep.
5. Security awareness and training
Implement a security awareness and training program for all workforce members, including management. The program itself is required; the four specifications in the table below are addressable.
Recommended practice: phishing simulations and role-specific modules for administrators, developers and billing staff. Our HIPAA compliance training service covers both Privacy Rule and Security Rule training.
| Specification | Practical example |
|---|---|
| Security reminders | Short periodic notices on current phishing themes or policy changes |
| Protection from malicious software | Training on recognizing and reporting malware; supporting anti-malware or EDR tools |
| Log-in monitoring | Procedures to monitor log-in attempts and report discrepancies |
| Password management | Procedures for creating, changing and safeguarding passwords, aligned with technical settings |
6. Security incident procedures
Implement policies to address security incidents. The single specification — response and reporting — is required: identify and respond to suspected or known incidents, mitigate harmful effects to the extent practicable, and document incidents and their outcomes.
A security incident is broader than a breach. Every incident must be handled; only some will turn out to be breaches of unsecured PHI requiring notification under §164.400–§164.414. The incident procedure should feed directly into a breach risk assessment workflow.
7. Contingency plan
Establish policies for responding to an emergency or other occurrence that damages systems containing ePHI — fire, flood, system failure, ransomware.
| Specification | R/A | What good looks like |
|---|---|---|
| Data backup plan | R | Retrievable exact copies of ePHI, with at least one copy protected from ransomware |
| Disaster recovery plan | R | Procedures to restore any loss of data, with defined recovery time targets |
| Emergency mode operation plan | R | How critical business processes continue and ePHI stays protected during an emergency |
| Testing and revision procedures | A | Periodic restore tests and tabletop exercises, with lessons learned |
| Applications and data criticality analysis | A | Ranking of systems by how critical they are to patient care and operations |
8. Evaluation
Perform periodic technical and nontechnical evaluations, initially based on the Security Rule standards and then in response to environmental or operational changes, to establish how well your policies and procedures meet the rule. The rule does not set a frequency; annual evaluation is common. An evaluation is your own assessment, not a government audit, and it is distinct from the risk analysis. A HIPAA gap analysis is one common way to perform it.
9. Business associate contracts and other arrangements
A covered entity may permit a business associate to create, receive, maintain or transmit ePHI only with satisfactory assurances, documented in a written contract or other arrangement meeting §164.314(a). Business associates must obtain the same assurances from subcontractors (§164.308(b)(2)). The written contract specification is required. Contract content is covered on our business associate agreement page.
Frequently asked questions
How many administrative safeguards are there?
Nine standards: eight in §164.308(a)(1)–(8) and the business associate contracts standard in §164.308(b)(1). Together they contain the largest number of Security Rule implementation specifications.
Can the privacy official and security official be the same person?
Yes. The rule requires each role to be designated, but does not require different people. Larger organizations usually separate them because the workloads differ.
Is an annual risk analysis required?
The rule does not specify a frequency. It requires the analysis to be accurate and thorough and the security program to be reviewed and updated as needed. Annual updates plus updates after major changes are a common and defensible approach.
What is the difference between evaluation and risk analysis?
Risk analysis identifies and rates risks to ePHI. Evaluation measures how well your policies and procedures meet the Security Rule’s requirements. Both are required and they inform each other.
Are background checks required?
Workforce clearance is addressable. You must assess whether screening is reasonable and appropriate for each role and document the decision. State laws and other regulations may also apply.
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
- HHS: Guidance on Risk Analysis Requirements under 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.