Skip to main content

Encryption in Transit - Protecting Data on the Wire

About 2 min read

Encryption in Transit is a technique that encrypts data flowing over a network to prevent eavesdropping and tampering. TLS (Transport Layer Security) is the representative protocol, used to protect network communication such as HTTPS communication, sending and receiving email, and VPN tunnels. TLS 1.3 was standardized as RFC 8446 in August 2018, reducing the number of handshake round trips and removing legacy cipher suites. As of October 2026, RFC 8446 has been obsoleted by RFC 9846, which also specifies TLS 1.3.

Real-World Use Cases

For example, a system might protect external communication with HTTPS while leaving internal communication between microservices in plaintext. In that state, anyone who gets inside the same network can read the internal traffic as it is, and one countermeasure is to use a service mesh (such as Istio) to apply mTLS to service-to-service communication as well, automating authentication and encryption at the platform layer instead of leaving it to each application.

Encryption-in-Transit Flow

Client: initiate TLS handshake
Server: present certificate, exchange keys
Generate a shared key (session key)
Establish encrypted communication (data exchange)

The Difference from Encryption at Rest

Whereas encryption at rest protects data stored on disks and databases, encryption in transit protects data while it moves from sender to receiver. The two cover different stages and complement each other. For example, even if your database is encrypted, if communication with the application server is in plaintext, the data could be intercepted through a man-in-the-middle attack.

Major Protocols and Implementations

TLS 1.3 reduces the number of handshake round trips. SSH encrypts server-management communication, and IPsec provides network-layer encryption over VPN tunnels. In cloud environments, some designs also apply mTLS (mutual TLS authentication) to inter-service communication. On public Wi-Fi, combining encryption in transit with a VPN encrypts even unencrypted communication on the stretch between the device and the VPN server.

Operational Tips

TLS certificates have an expiry date, and if one is not renewed, browsers display a warning that makes the service hard for users to open. Let's Encrypt's auto-renewal and certificate-management tools are ways to prevent expiration. In addition, TLS 1.0/1.1 lack support for recommended cryptographic algorithms and mechanisms, and the IETF formally deprecated them in RFC 8996 (March 2021). With encryption in transit, credentials such as a strong random password travel across the network encrypted.

Was this article helpful?

Related Terms