Encryption in Transit

Protection of data during transmission between systems through protocols such as TLS/SSL.

A

B

C

D

E

Encryption in transit protects data as it travels between systems, devices and networks by using cryptographic protocols such as TLS (Transport Layer Security) and its predecessor SSL. This prevents eavesdropping, man-in-the-middle attacks and data tampering during transmission, whether the data flows between a user's browser and a web server, between microservices within a data centre or between on-premises systems and cloud environments.

Implementing encryption in transit is a baseline security requirement under virtually all compliance frameworks, including ISO 27001, SOC 2, PCI DSS and the GDPR. Organisations should enforce minimum TLS versions (currently TLS 1.2 or higher), use strong cipher suites, implement certificate management and regularly test their configurations using tools like SSL Labs to ensure that data remains protected during every transmission.

F

G

H

I

J

K

L

M

N

O

P

Q

R

S

T

U

V

W

Z

Frequently asked questions

What is encryption in transit?
Encryption in transit protects data while it moves between systems, using protocols such as TLS (the successor to the deprecated SSL) so it cannot be read if intercepted.
What is the difference between encryption in transit and at rest?
Encryption in transit protects data while it is being transmitted; encryption at rest protects data while it is stored.
Why is encryption in transit required?
It is a baseline control in frameworks such as ISO 27001 and SOC 2 and helps meet the GDPR requirement to protect personal data.