164.312(e)(2)(ii) Encryption of Transmissions (Addressable)
Implement a mechanism to encrypt ePHI whenever deemed appropriate. NIST recommends defaulting to encryption for all ePHI transmissions, with documented exception only where infeasible.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Cloud provider TLS attestations · Cloud console / configuration management
governing documentDocuments that govern the control
- Encryption-in-transit standard · Policy repository / GRC workspace
- Coverage report for all ePHI flows · Document repository
- Exception register with compensating controls · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Internal network treated as trusted and unencrypted
- Fax or unsecure messaging in use without compensating control
- No periodic scan of cipher quality
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet164.312(e)(2)(i) Integrity Controls for Transmission (Addressable) · 164.314(a)(1) Business Associate Contracts or Other Arrangements (Standard)