HIPAA · Control requirements

HIPAA Control Requirements

Practical answers for the IT and security teams who build and run HIPAA safeguards: what the Security Rule requires, what OCR expects to see, and the evidence that proves it.
HIPAA controls

Scope and risk

1. How do we map where PHI lives and flows?

Identify every place PHI is created, received, stored, or sent: EHR and practice management systems, billing, email, file shares, cloud services, laptops, mobile devices, medical devices, and vendors. Draw how it moves between them and outside your organization. This map is the foundation of your risk analysis, and PHI you don’t know about is PHI you can’t protect.

2. How do we build an asset inventory and network map?

List the systems, devices, and software that handle ePHI, with an owner and location for each, and maintain a network diagram showing how they connect and where ePHI crosses boundaries. Pull the inventory from your management tools rather than memory. The proposed Security Rule update would make both explicitly required and reviewed at least every 12 months, so building them now puts you ahead.

3. What is the difference between required and addressable safeguards?

Under the current Security Rule, required safeguards must be implemented. Addressable ones must be implemented if reasonable and appropriate, or replaced with an equivalent measure, with the decision documented. Addressable never means optional. The proposed update would make nearly all safeguards required, so treat addressable items such as encryption as expected, not optional.

4. What does a risk management plan need to include?

For each risk your analysis finds, record the safeguard you will use to reduce it, an owner, a target date, and the status. Prioritize the highest risks first and document any risks you accept, with a reason. OCR expects to see that risks were actually reduced, not just identified, so update the plan as work is completed.
HIPAA controls

Administrative safeguards

5. How are remote workers, contractors, and onboarding and offboarding addressed?

Grant workforce members, including remote staff and contractors, only the access to ePHI their job requires, with authorization recorded before access is given. Remote work needs managed devices, encrypted connections, and rules for working outside the office. When people leave or change roles, remove access promptly, ideally the same day, and recover devices. Keep dated records; OCR asks for them.

6. What security awareness training must the workforce complete?

Everyone who works with PHI, including clinicians, front-office staff, and contractors, needs security awareness training at hire and regularly after, typically annually, covering phishing, passwords and MFA, device security, PHI handling, and reporting incidents. Send periodic security reminders. Keep completion records, because missing training evidence is a common investigation finding.

7. What is a sanctions policy, and do we need one?

Yes. HIPAA requires a policy for disciplining workforce members who violate your security and privacy policies, applied consistently and documented. It shows that rules are enforced, not just written. Combine it with clear acceptable use rules, including for AI tools, so staff know what is expected.

8. How should we document security incident procedures?

Define how staff report suspected incidents, who investigates, how incidents are contained and documented, and how you decide whether an incident is a reportable breach. Test the process with a tabletop exercise at least annually and record the results. Log every incident to closure; OCR expects to see incidents identified, responded to, and documented.

9. What does a HIPAA contingency plan need to include?

Your contingency plan covers data backups, disaster recovery, and emergency-mode operations, so you can keep caring for patients and protecting ePHI during an outage or ransomware attack. Identify your critical systems, test restores, and test the plan. The proposed update would require restoring critical systems within 72 hours, so plan and test against that target now.

10. What is the periodic evaluation requirement?

HIPAA requires you to evaluate periodically, and after significant changes, whether your safeguards still meet the Security Rule. In practice, combine it with your annual risk analysis update and a review of policies, training, and business associates. Document the evaluation and the actions that come from it. The proposed update would add an explicit annual compliance audit.
HIPAA controls

Physical safeguards

11. What facility access controls do we need?

Limit physical access to areas and equipment holding ePHI, such as server rooms, network closets, and records areas, to authorized people. Use locks or badge access, log visitors and maintenance, and record repairs to physical security. For cloud-hosted systems, rely on your provider’s BAA and data center controls, but still secure your offices and clinics.

12. How should we secure workstations, laptops, and mobile devices?

Position screens away from public view in clinical and front-desk areas, lock screens automatically, and encrypt laptops and mobile devices that store or access ePHI. Manage devices centrally so you can enforce settings and wipe lost devices. Lost or stolen unencrypted devices remain a leading cause of reported breaches, and encryption usually turns them into non-reportable events.

13. How do we handle disposal and reuse of devices and media?

Before disposing of or reusing computers, drives, copiers, phones, and removable media, remove ePHI using approved wiping or destruction methods, and keep certificates or logs of disposal. Track the movement of hardware that holds ePHI. Many breaches come from devices that were discarded, sold, or returned to a leasing company without being wiped.
HIPAA controls

Technical safeguards

14. What access controls does the Security Rule require?

Give every user a unique login, never shared accounts, and limit access to ePHI by role. Have an emergency access procedure so clinicians can reach records during an outage, and log off or lock inactive sessions automatically. Review who has access regularly, commonly quarterly, and remove access that is no longer needed, keeping records of each review.

15. Is multi-factor authentication required?

The current rule requires you to verify that users are who they claim to be, without naming a method. In practice, multi-factor authentication is expected for email, remote access, EHR systems, and administrator accounts, because stolen passwords drive many healthcare breaches. The proposed update would make MFA required for access to ePHI, so implement it now.

16. How should we manage privileged and service accounts?

Limit administrator access to the few people who need it, use separate admin accounts with multi-factor authentication, and log their activity. Give service and integration accounts an owner, minimum permissions, and credentials stored securely and rotated. Review both types in your access reviews; compromised admin accounts are how ransomware spreads.

17. What audit controls and log reviews do we need?

Record activity in systems that contain or use ePHI, such as logins, record access, changes, and exports, and protect the logs from tampering. Review them regularly for inappropriate access, such as staff viewing records without a reason, and investigate alerts. Logging that nobody reviews does not satisfy OCR.

18. How do we protect the integrity of ePHI?

Put measures in place to prevent ePHI from being improperly changed or destroyed, and to detect it if it is. Examples include access restrictions, change logging, checksums or database integrity checks, endpoint protection, and immutable backups that ransomware cannot encrypt. Document how each system protects integrity.

19. What encryption is expected for ePHI?

Encrypt ePHI in transit, including email, file transfers, APIs, and remote access, and at rest on servers, databases, laptops, mobile devices, and backups. Under the current rule encryption is addressable, but OCR treats unencrypted ePHI as a major risk, and encrypted data meeting HHS guidance is generally exempt from breach notification. The proposed update would make encryption required.

20. What vulnerability scanning and penetration testing should we complete?

Scan systems that handle ePHI for vulnerabilities regularly, patch based on risk, and track fixes. The current rule doesn’t name a frequency, but OCR expects vulnerabilities to be found and fixed as part of risk management. The proposed update would require scanning at least every six months and penetration testing at least every 12 months, and we recommend meeting that pace now.
Next step

Tell us where you stand

Tell us what you’re trying to accomplish. We’ll reply with clear next steps.