164.312(e)(1) Transmission Security (Standard)
Implement technical security measures to guard against unauthorized access to ePHI transmitted over an electronic communications network. NIST recommends encrypted transport, secure email, and validated VPN.
4
artefacts
2
held by a system
1
at each review
easy
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- TLS configuration scans · Vulnerability scanner / patch tooling
- VPN configuration evidence · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Secure email gateway records · Document repository
governing documentDocuments that govern the control
- Transport encryption standard · Policy repository / GRC workspace
First move
Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.
Common gaps auditors find
- Legacy TLS versions enabled
- FTP and SMTP used in clear
- Inter-site links not encrypted
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(d) Person or Entity Authentication (Standard) · 164.312(e)(2)(i) Integrity Controls for Transmission (Addressable)