164.312(e)(2)(i) Integrity Controls for Transmission (Addressable)
Implement security measures to ensure electronically transmitted ePHI is not improperly modified without detection until disposed of. NIST recommends authenticated TLS, signed messages, and integrity validation on receip
4
artefacts
2
held by a system
0
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Message signing configuration · Cloud console / configuration management
- Integrity validation logs · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- TLS with strong cipher suites · Policy repository / GRC workspace
- Tamper alert procedure · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- Unauthenticated TLS endpoints
- Messages not signed
- No receipt-side verification
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)(1) Transmission Security (Standard) · 164.312(e)(2)(ii) Encryption of Transmissions (Addressable)