A stolen laptop from a parked car. That's what triggered a $1.5 million settlement between HHS and Concentra Health Services in 2014. The laptop wasn't encrypted. The ePHI on it belonged to thousands of patients. And Concentra had known about its encryption gaps for years — and failed to act. The whole case came down to one question the Office for Civil Rights keeps asking: what safeguards does the HIPAA Security Rule require, and did this organization actually implement them?

If you work at a covered entity or business associate, you need to know the answer to that question cold. Not in abstract, textbook terms — in operational, "this is what we actually do on Monday morning" terms. Because OCR doesn't care about your intentions. They care about your implementation.

Let me walk you through the three categories of safeguards, what they demand in practice, and where I've seen organizations consistently fall short.

The Three Categories: Administrative, Physical, and Technical

The HIPAA Security Rule, codified at 45 CFR Part 164, Subpart C, requires covered entities and business associates to protect the confidentiality, integrity, and availability of electronic protected health information (ePHI). It does this through three categories of safeguards.

These aren't suggestions. They're regulatory requirements, each with specific standards and implementation specifications. Some specifications are "required" — non-negotiable. Others are "addressable," meaning you must implement them or document why an equivalent alternative is reasonable. "Addressable" does not mean "optional." I've seen that misunderstanding cost organizations millions.

Administrative Safeguards: Where Most Breaches Actually Start

Administrative safeguards account for more than half of the Security Rule's requirements. They're the policies, procedures, and workforce management practices that form the backbone of your compliance program. And in my experience, they're where the biggest gaps live.

Risk Analysis — The Standard OCR Checks First

Every single OCR investigation I've followed starts with the same question: did you conduct a thorough, organization-wide risk analysis? The standard at §164.308(a)(1) requires you to identify threats and vulnerabilities to ePHI, assess the likelihood and impact of each, and implement measures to reduce risks to a reasonable level.

This isn't a one-time checkbox. It's an ongoing process. When Premera Blue Cross settled with OCR for $6.85 million in 2020, a key finding was that the company had failed to conduct an adequate risk analysis — even after a breach affecting over 10.4 million people. You can review OCR's enforcement actions directly on the HHS breach settlements page.

Workforce Training and Management

Your staff are your largest attack surface. The Security Rule requires security awareness training for all workforce members at §164.308(a)(5). That includes training on password management, malicious software recognition, login monitoring, and phishing awareness.

I've audited pharmacies where technicians shared a single login across an entire shift. I've seen home health agencies where remote workers accessed ePHI on personal devices with zero encryption. These aren't edge cases — they're patterns. If your organization has staff working remotely, our Working from Home & PHI training addresses exactly the safeguard gaps that remote environments create.

Other Critical Administrative Standards

  • Security Officer Designation: You must assign a specific person responsible for developing and implementing your security policies. Not a committee. A person.
  • Access Management: Policies governing who gets access to ePHI, how access is granted, and how it's revoked when someone leaves or changes roles.
  • Contingency Planning: Data backup plans, disaster recovery plans, and emergency mode operation plans. If a ransomware attack hits your EHR tonight, what's your documented plan?
  • Business Associate Agreements: Every vendor that touches your ePHI must have a signed BAA in place. No exceptions.

Physical Safeguards: Locking Down the Real World

Physical safeguards at §164.310 protect the actual buildings, equipment, and devices that store or access ePHI. They're deceptively simple in concept but consistently neglected in practice.

Facility Access Controls

You need documented policies that limit physical access to your systems and the facilities that house them. This means controlling who enters your server room, your medical records area, and any space where ePHI is accessible on screens or paper.

For large hospital systems, this might involve badge readers and surveillance cameras. For a small dental office, it might mean a locked door and a visitor log. The scale varies. The requirement doesn't.

Workstation and Device Security

The Security Rule requires policies governing workstation use and physical safeguards for all workstations that access ePHI. It also requires policies for the receipt, movement, and disposal of hardware and electronic media containing ePHI.

Here's a scenario I see constantly: a pharmacy upgrades its point-of-sale system and tosses the old hard drives in a dumpster without wiping them. That's a violation waiting to become a breach report. If you're in pharmacy, our HIPAA & HITECH for Pharmacy Professionals course covers these physical safeguard requirements in pharmacy-specific detail.

Technical Safeguards: The Controls Inside Your Systems

Technical safeguards at §164.312 are the technology-based protections built into your information systems. These are the controls that most IT teams focus on — but often without aligning them to the actual regulatory requirements.

Access Controls

Every person who accesses ePHI must have a unique user ID. You must implement procedures for emergency access. And you need automatic logoff and encryption mechanisms. The unique user ID requirement is non-negotiable — shared logins make audit trails meaningless.

Audit Controls

Your systems must record and examine activity in information systems that contain or use ePHI. This means audit logs. Not just having them — reviewing them. I've investigated environments where logs existed but nobody had looked at them in three years. That's functionally the same as not having them.

Integrity and Transmission Security

You must implement mechanisms to authenticate ePHI — confirming it hasn't been altered or destroyed improperly. For data in transit, you need safeguards against unauthorized access. In practical terms: encrypt data at rest and in transit. Use TLS for email containing PHI. Validate your backup integrity regularly.

What About AI Tools and Emerging Technology?

Here's a safeguard gap that didn't exist five years ago but is now one of the fastest-growing risk areas I encounter: staff feeding PHI into AI tools like chatbots, transcription services, and generative AI platforms. None of the three safeguard categories explicitly mention AI — but every one of them applies to it.

If a nurse pastes a patient's medication list into an AI tool to draft a care summary, that's a potential ePHI disclosure to an unauthorized third party. Your administrative safeguards should address AI use in your policies. Your technical safeguards should restrict which applications can access your systems. And your workforce training should make the risks crystal clear.

We built our Using AI Tools & PHI course specifically for this problem. It's the fastest-growing compliance gap I'm seeing in 2026, and most organizations haven't addressed it yet.

Quick Answer: What Safeguards Does the HIPAA Security Rule Require?

The HIPAA Security Rule requires three categories of safeguards to protect ePHI: administrative safeguards (risk analysis, workforce training, access management, contingency planning), physical safeguards (facility access controls, workstation security, device and media controls), and technical safeguards (access controls, audit controls, integrity controls, transmission security). Each category contains required and addressable implementation specifications that covered entities and business associates must implement or formally document alternatives for.

The $2.1 Million Question: Are You Actually Implementing These?

In 2019, Sentara Hospitals paid $2.175 million to settle with OCR after mailing PHI to wrong addresses and then failing to properly report the breach. But the investigation also uncovered broader compliance failures — including gaps in the exact safeguards we've been discussing.

That's the pattern in almost every OCR enforcement action. The investigation starts with one incident and uncovers systemic safeguard failures. The breach itself might cost you a notification expense. The missing safeguards cost you millions.

Three Steps You Can Take This Week

  • Pull your most recent risk analysis. If it's more than 12 months old — or if it doesn't exist — you have your top priority.
  • Audit your access logs. Pick one system that stores ePHI and review who accessed it in the last 30 days. Look for terminated employees, shared accounts, and unusual access patterns.
  • Check your training records. Can you prove that every workforce member received security awareness training this year? If not, start there. Browse our full HIPAA training catalog to find role-specific courses that fit your organization.

The HIPAA Security Rule's safeguard requirements aren't ambiguous. They're detailed, they're enforceable, and OCR has a long track record of penalizing organizations that ignore them. The gap between knowing what safeguards the Security Rule requires and actually implementing them across your workforce — that's where the risk lives. Close it before OCR does it for you.