Encryption in Transit
Encryption in transit protects data while it moves between systems, such as from a browser to a website, between email servers or from an office to the cloud, usually with TLS, so it can't be read or altered on the way.
Also called: data in transit encryption, data in motion encryption, transport encryption
What is encryption in transit?
Data is "in transit" when it's travelling across a network: the internet, office Wi-Fi or a link between data centers. Without encryption, anyone positioned along the way could read or change it, see packet sniffing and man-in-the-middle attacks. Encryption in transit wraps the data so only the intended endpoints can read it.
How it's done
- [TLS](/glossary/tls/) is the standard for most traffic: websites (HTTPS), APIs, apps and email between servers. NIST's TLS guidelines set out how to configure it.
- [VPNs](/glossary/vpn/) encrypt everything between a device or office and the company network.
- SSH and SFTP for administering servers and transferring files.
- Email: STARTTLS encrypts mail between servers when both support it; CISA's BOD 18-01 requires it for federal agencies.
Gaps to check
- Old protocols still in use, such as FTP, Telnet or plain HTTP on internal systems.
- Email to partners whose servers don't support TLS; use a secure portal for sensitive files.
- Outdated TLS versions on websites, mail servers and appliances.
- Traffic inside the network or between cloud services that's assumed to be safe; zero trust says encrypt it too.
Pair encryption in transit with encryption at rest so data is protected wherever it is.
Related terms
Sources
Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.
