Skip to content

HIPAA Security Rule

The HIPAA Security Rule sets administrative and technical safeguards for electronic protected health information (ePHI).

About this standard

The HIPAA Security Rule (45 CFR Part 164, Subpart C) sets safeguards for electronic protected health information (ePHI). 'Required' specifications must be implemented; 'addressable' ones must be implemented when reasonable, or the alternative documented. In January 2025 HHS proposed a major update to the Security Rule, including required MFA, encryption, and asset inventories. It has not been finalized (HHS now projects final action in 2027), so Trimtab maps to the Security Rule currently in force.

Official sources:

Trimtab checks 11 of this standard's requirements with technical evidence. Requirements about policies, training, and physical security need their own evidence and are not listed here.

Each requirement starts with a plain-English summary, followed by the official text.

Administrative Safeguards (164.308)

164.308(a)(1)(ii)(B)

Risk management

Find your security weak spots and fix them, starting with the ones most likely to cause harm.

Required. Implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level.

Proven by: PAT-001, PAT-003, PAT-004, M365-011, EXO-007, EXO-008, EXO-010, INT-003

164.308(a)(5)(ii)(B)

Protection from malicious software

Have antivirus in place and a way to notice and report malware.

Addressable. Procedures for guarding against, detecting, and reporting malicious software.

Proven by: AV-001, AV-002, AV-005, EXO-009, EXO-011, EXO-012, EXO-013, EXO-014, EXO-015, EXO-020

164.308(a)(5)(ii)(C)

Log-in monitoring

Watch for failed or suspicious sign-ins and act on them.

Addressable. Procedures for monitoring log-in attempts and reporting discrepancies.

Proven by: ACC-004, AUD-001, M365-014

164.308(a)(5)(ii)(D)

Password management

Set rules for strong passwords and protect them.

Addressable. Procedures for creating, changing, and safeguarding passwords.

Proven by: ACC-005, ACC-006, ACC-007, M365-025

Technical Safeguards (164.312)

164.312(a)(1)

Access control

Only people and programs that have been given permission should be able to reach patient data.

Standard. Implement technical policies and procedures for electronic information systems that maintain ePHI to allow access only to those persons or software programs that have been granted access rights.

Proven by: ACC-001, ACC-002, ACC-009, M365-005, M365-006, M365-008, M365-009, M365-010, M365-013, M365-015, M365-019, SPO-002, SPO-003, EXO-016, M365-021, M365-026, SPO-004, EXO-018, INT-006

164.312(a)(2)(iii)

Automatic logoff

Lock or sign out unattended sessions automatically after a set time.

Addressable. Implement electronic procedures that terminate an electronic session after a predetermined time of inactivity.

Proven by: SES-001, M365-012, M365-024

164.312(a)(2)(iv)

Encryption and decryption

Encrypt patient data so it is unreadable if a device or file falls into the wrong hands.

Addressable. Implement a mechanism to encrypt and decrypt ePHI.

Proven by: ENC-001, INT-004, INT-005

164.312(b)

Audit controls

Keep records of who accessed and changed systems holding patient data, and review them.

Standard. Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use ePHI.

Proven by: AUD-001, AUD-002, AUD-003, EXO-001, EXO-002

164.312(d)

Person or entity authentication

Make sure people are who they say they are before they get in, and protect the credentials that prove it.

Standard. Implement procedures to verify that a person or entity seeking access to ePHI is the one claimed.

Proven by: SES-003, HRD-009, M365-001, M365-002, M365-003, M365-004, EXO-005, EXO-006, M365-016, SPO-001, M365-020, M365-023

164.312(e)(1)

Transmission security

Protect patient data while it travels across a network. Encrypt it, and don't let it leave in ways you can't control, like automatic forwarding to outside email or unprotected remote connections.

Standard. Implement technical security measures to guard against unauthorized access to ePHI that is being transmitted over an electronic communications network.

Proven by: FW-001, EXO-003, EXO-004

164.312(e)(2)(ii)

Encryption in transit

Patient information sent over a network should be encrypted with modern protocols, not outdated ones.

Addressable. Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate.

Proven by: HRD-010