Hands-on tutorial
Tutorials · Compliance
HIPAA Security Rule for Networks: Protecting ePHI in Clinics and Hospitals
What the US HIPAA Security Rule means for healthcare networks: risk analysis, access control, audit controls, integrity, transmission security, medical device segmentation and contingency planning.
Quick answer
The HIPAA Security Rule (45 CFR Part 164, Subpart C) requires covered entities and their business associates in the United States to protect electronic protected health information (ePHI) with administrative, physical and technical safeguards.
Network teams implement most technical safeguards: access control, audit controls, integrity controls, authentication and transmission security, on top of a documented risk analysis.
This guide explains network controls that commonly support compliance. It is not legal advice; confirm your obligations with your legal or compliance adviser.
Key terms
- ePHI
- Electronic protected health information: health information that identifies a patient, held or sent electronically.
- Business associate
- A vendor that handles ePHI for a covered entity and must sign a business associate agreement (BAA).
- Addressable
- An implementation specification you must implement if reasonable, or document an equivalent alternative.
Before you start
- An inventory of systems handling ePHI: EHR, PACS, lab and pharmacy systems, medical devices
- The organisation's HIPAA risk analysis
- Network diagrams of clinical and public areas
Step by step
Start with the risk analysis
The Security Rule requires an accurate and thorough risk analysis (§164.308(a)(1)). List threats to ePHI on the network and the controls that address them.
Segment clinical systems
Separate clinical systems, medical devices, staff, guest Wi-Fi and building systems into zones. Medical devices that cannot be patched need strict isolation.
Control access
Unique user IDs, role-based access, automatic logoff and MFA for remote and administrative access (§164.312(a)). Use 802.1X/NAC so devices land in the right VLAN.
Audit controls
Record and examine activity on systems that contain ePHI (§164.312(b)): central logging from gateways, firewalls, Wi-Fi and authentication, with alerts.
Protect integrity and transmission
Encrypt ePHI in transit with TLS, VPNs and WPA2/WPA3-Enterprise (§164.312(e)), and protect it from improper change.
Plan for contingencies
Back up data and configurations, keep redundant core and power for clinical networks, and test disaster recovery (§164.308(a)(7)).
Manage vendors
Ensure vendors with access to ePHI sign BAAs and use controlled, recorded remote access.
Pro tips
- Record why addressable specifications were implemented or how alternatives meet them.
- Keep guest Wi-Fi completely isolated from clinical networks.
- Review audit logs regularly, not only after incidents.
HIPAA Security Rule safeguards and network controls
| Security Rule safeguard | Network control |
|---|---|
| Access control §164.312(a) | Unique IDs, MFA, NAC, segmentation |
| Audit controls §164.312(b) | Central logs, SIEM, alerts |
| Integrity §164.312(c) | Signed firmware, configuration control |
| Person or entity authentication §164.312(d) | 802.1X, MFA |
| Transmission security §164.312(e) | TLS, VPN, WPA3-Enterprise |
| Contingency plan §164.308(a)(7) | Backups, redundancy, DR tests |
Standards and references
FAQ
Frequently asked questions
Does HIPAA require encryption?
Encryption is an 'addressable' specification, but in practice encryption in transit and at rest is expected unless you document an equivalent protection.
Is a cloud network platform a business associate?
If it creates, receives, maintains or transmits ePHI for you, yes. Network management platforms usually handle device data, not ePHI; check what data flows through them.
Does HIPAA apply outside the US?
HIPAA applies to US covered entities and their business associates. Other countries have their own health data rules.
Keep learning
Related guides
Hospital network design
Read more →What is NAC?
Read more →Wi-Fi 7 access point NW-AP725-2.5G
Read more →NavNAC
Read more →Hospital case study
Read more →GDPR for Network Teams: Practical Security Controls and Checklist
What the EU General Data Protection Regulation expects from your network: security of processing, access control, logging, encryption, guest Wi-Fi data, CCTV, retention and breach readiness, with a checklist you can apply.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.