What is the HIPAA Security Rule?

The HIPAA Security Rule requires covered entities and business associates to ensure the confidentiality, integrity, and availability of the electronic protected health information they create, receive, maintain, or transmit. It does this through administrative, physical, and technical safeguards set out in 45 CFR Part 164, Subpart C.

The Security Rule applies only to electronic PHI. Its general requirements in 45 CFR 164.306 are to protect ePHI against reasonably anticipated threats and impermissible uses or disclosures, and to make sure the workforce complies. The standards themselves sit in three sections: administrative safeguards (164.308), physical safeguards (164.310), and technical safeguards (164.312).

Flexible, but not optional

The rule does not prescribe products. An organization picks its own measures after weighing its size and complexity, its technical infrastructure, the cost of each measure, and the probability and criticality of risks to ePHI. Implementation specifications are labeled Required or Addressable. Required ones must be implemented. For an addressable one, the organization assesses whether it is reasonable and appropriate in its environment. If it is, it implements it. If not, it documents why and puts an equivalent alternative in place where that is reasonable. Either way, the decision is written down.

What engineering teams build against

  • Risk analysis and risk management (Required): an accurate, thorough assessment of risks to ePHI, and measures that reduce them.
  • Unique user identification and an emergency access procedure (both Required).
  • Automatic logoff and encryption of stored data (both Addressable).
  • Audit controls that record and examine activity in systems holding ePHI.
  • Person or entity authentication, so the system verifies who is asking.
  • Transmission security, with integrity controls and encryption in transit (both Addressable).
  • A data backup plan (Required).

The rule also requires ongoing maintenance: security measures are reviewed and updated as needed, and the documentation with them. NIST SP 800-66 Revision 2, published in February 2024, is a practical resource guide that maps these standards to concrete activities for organizations of any size.

Example

A telehealth startup stores visit recordings in cloud object storage. Its risk analysis flags the bucket as holding ePHI. Encryption at rest is addressable, so the team either turns it on or writes down why it is not reasonable and what equivalent control replaces it. In practice the first option is cheaper to defend in an audit. The team also adds access logging on the bucket to meet the audit controls standard and records both decisions in its risk management plan.