TL;DR
- HIPAA administrative safeguards are nine standards in 45 CFR 164.308 that govern risk analysis, workforce access, training, incident response, contingency planning, evaluation, and business associate oversight.
- Addressable” does not mean optional. Each addressable specification must be implemented, or the reason it is not reasonable and appropriate must be documented, with an equivalent measure adopted where possible.
- HHS has proposed Security Rule updates, but the current rule remains in effect, so evidence of today’s standards is still what regulators and auditors test.
Healthcare organizations now run patient data through cloud EHR platforms, telehealth tools, billing vendors, and remote clinical staff, so ePHI risk depends as much on governance as on technology. Firewalls and encryption protect little when nobody owns the risk analysis, former employees keep access, or a vendor handles records without a written agreement. HIPAA’s administrative safeguards address that governance layer. This article explains the nine standards, the evidence each one calls for, and where covered entities and business associates commonly fall short.
What Are HIPAA Administrative Safeguards?
HIPAA administrative safeguards are the policies, procedures, and management actions that govern how an organization selects, implements, and maintains security measures for ePHI and manages workforce conduct. They sit in the Security Rule at 45 CFR 164.308 and apply to covered entities and business associates. Ampcus Cyber’s guide to HIPAA covers the wider framework, and its explainer on ePHI clarifies what data is in scope.
Each standard may include implementation specifications that are either required or addressable. Required specifications must be implemented. For addressable ones, the entity assesses whether the measure is reasonable and appropriate, then implements it or documents why not and adopts an equivalent alternative. The HHS Summary of the HIPAA Security Rule explains this flexibility.
What Are the 9 HIPAA Administrative Safeguard Standards?
The nine standards are eight in 164.308(a) plus business associate contracts in 164.308(b). HHS also publishes a guidance paper on the administrative safeguards.
| # | Standard | What It Requires | Typical Evidence |
| 1 | Security Management Process (a)(1) | Risk analysis, risk management, sanction policy, activity review | Risk analysis, risk register, log review records |
| 2 | Assigned Security Responsibility (a)(2) | A designated security official | Appointment letter, role description |
| 3 | Workforce Security (a)(3) | Authorization, clearance, and termination procedures | Onboarding and offboarding records |
| 4 | Information Access Management (a)(4) | Access authorization and modification policies | Access requests, periodic reviews |
| 5 | Security Awareness and Training (a)(5) | Training for all workforce, including management | Training logs, reminders, password procedures |
| 6 | Security Incident Procedures (a)(6) | Identify, respond to, and document incidents | Incident plan, incident log |
| 7 | Contingency Plan (a)(7) | Backup, disaster recovery, emergency mode operation | Backup tests, recovery plan, criticality analysis |
| 8 | Evaluation (a)(8) | Periodic technical and nontechnical evaluation | Evaluation reports, change reviews |
| 9 | Business Associate Contracts (b)(1) | Satisfactory assurances in a written contract | Executed agreements, vendor inventory |
Two standards act as the program’s feedback loop. The security management process produces the risk picture, and the evaluation standard checks whether policies still fit after changes. Teams that treat the other seven as isolated checklists often pass individual items yet fail to show how decisions connect. Mapping every standard to a named owner, a review date, and a stored artifact makes the connection visible to an assessor.
How Does the Security Management Process Protect ePHI?
The security management process is the core standard, requiring policies to prevent, detect, contain, and correct security violations. It contains four required specifications: risk analysis, risk management, a sanction policy, and information system activity review.
The risk analysis assesses threats and vulnerabilities to the confidentiality, integrity, and availability of ePHI. Risk management then adopts measures that reduce those risks to a reasonable and appropriate level. The other standards depend on these outputs, so weak analysis weakens everything downstream.
Ampcus Cyber’s HIPAA risk analysis guide walks through the steps. The rule sets no fixed interval for the analysis, so organizations should repeat it when systems, vendors, or workflows change.
How Do Workforce, Access, and Training Standards Work Together?
Standards 2 to 5 control who can reach ePHI and what they know. The security official develops and implements the policies. Workforce security covers authorization, clearance, and termination. Access management covers granting and modifying rights. Training covers security reminders, malicious software protection, log-in monitoring, and password management.
As a hypothetical example, a clinic’s billing contractor changes roles but keeps access to the practice management system. Termination procedures, access modification, and activity review should each catch this, so a gap here usually points to a process failure rather than a missing tool.
What Do Incident, Contingency, and Evaluation Standards Require?
Security incident procedures require organizations to identify and respond to suspected or known incidents, reduce harm where practicable, and document outcomes. The contingency plan requires three mandatory elements: a data backup plan, a disaster recovery plan, and an emergency mode operation plan. Testing and criticality analysis are addressable. The evaluation standard requires periodic technical and nontechnical review, and re-evaluation after environmental or operational changes.
A plan that has never been tested rarely meets expectations in practice. Tabletop exercises and restore tests produce the evidence that these standards otherwise leave abstract. Incident records should show who detected the event, what was contained, and what changed afterward.
How Should Covered Entities Manage Business Associates?
A covered entity may let a business associate create, receive, maintain, or transmit ePHI only after obtaining satisfactory assurances, documented in a written contract or other arrangement. Many organizations stop at signing the agreement, but vendors change systems, subcontractors, and hosting regions over time.
Where Do Organizations Struggle With Administrative Safeguards?
Most gaps trace to documentation that does not match operations. Common examples include:
- Risk analyses that are outdated, scoped to one system, or not linked to a risk management plan.
- No named security official, or a named one without authority.
- Terminated users whose accounts stay active.
- Generic training with no tracking, and addressable items left undocumented.
- Backup plans that have never been restored under test.
- Business associate agreements on file with no vendor inventory behind them.
What Should Organizations Do Next?
Start by mapping existing evidence to all nine standards and flagging what is missing, outdated, or unowned:
- Refresh the enterprise-wide risk analysis and link it to a risk management plan.
- Confirm the security official, and document every addressable decision.
- Reconcile access, onboarding, and offboarding records.
- Test the incident plan and a data restore, then record results.
- Build a business associate inventory with agreement dates.
Also watch rule changes. HHS proposed Security Rule updates in a Federal Register notice, including removing the required versus addressable distinction, adding a written technology asset inventory and network map, and requiring verification of business associate safeguards. HHS states the current rule remains in effect during rulemaking, so verify status before relying on proposed text.
Ampcus Cyber supports this work through HIPAA compliance services, covering gap assessments, risk analysis, remediation guidance, and audit readiness.
Conclusion
The nine administrative safeguards turn HIPAA’s expectations into ownership, process, and evidence. A current risk analysis, controlled access, tested response and recovery plans, and managed vendors show regulators that ePHI protection is a working program. Organizations that map each standard to a named owner and dated evidence reduce audit friction and recover faster from incidents.
| Book a HIPAA administrative safeguards gap assessment with Ampcus Cyber to test your risk analysis, access controls, incident and contingency plans, and business associate oversight against 45 CFR 164.308. |
People Also Ask
What are administrative safeguards in HIPAA?
Administrative safeguards are the policies, procedures, and management actions in 45 CFR 164.308 that govern how an organization manages ePHI security and workforce conduct. They include nine standards covering risk analysis, access, training, incidents, contingency planning, evaluation, and business associates.
How often should a HIPAA security risk analysis be done?
The Security Rule requires an accurate and thorough risk analysis but sets no fixed interval. It requires periodic evaluation and re-evaluation after environmental or operational changes, so most organizations review at least annually and after major system or vendor changes.
What does a HIPAA security officer do?
The security official, required by 164.308(a)(2), is the person designated to develop and implement the organization’s security policies and procedures. The role needs documented authority and clear reporting lines to leadership.
Is HIPAA security awareness training required?
Yes. Standard (a)(5) requires a security awareness and training program for all workforce members, including management. The rule does not set a fixed frequency, but addressable items such as security reminders must be periodic and documented.
Do you need a business associate agreement under HIPAA?
Yes. A covered entity may let a business associate handle ePHI only after obtaining satisfactory assurances, documented in a written contract or other arrangement under 164.308(b) and 164.314(a).
Who enforces the HIPAA Security Rule?
The HHS Office for Civil Rights enforces the Security Rule. Organizations should keep dated evidence for each standard so they can respond to an investigation or audit.
Enjoyed reading this blog? Stay updated with our latest exclusive content by following us on Twitter and LinkedIn.










