Data in transit, also called data in motion, is information being sent between systems, devices, or locations through a communication channel. File transfers, email, instant messages, and collaboration tools all involve data in transit. Unlike stored data, it moves outside the systems involved in the communication and may be exposed to interception. section 14.3.1
Organizations must protect data as it moves, not just while it is stored. Network attacks can intercept traffic, alter messages, disrupt services, or impersonate trusted users and systems. These attacks threaten confidentiality, integrity, or availability. Because communication passes through multiple devices, protocols, and transmission media, each stage can introduce a weakness. section 12.1 section 14.0
Encryption protocols such as TLS and VPNs help shield data in transit from interception. These protections work alongside other data security measures: encryption at rest cannot prevent interception during transmission, and data loss prevention (DLP) can monitor or block unauthorized movement of sensitive information. section 14.3.1 section 14.0
|
State
|
Main risk
|
Protection
|
Example
|
|
Data at Rest
|
Unauthorized
access to stored data
|
Encryption
and access controls
|
Encrypting a
database using a strong encryption algorithm to protect customer records
|
|
Data in Transit
|
Interception
or alteration during transmission
|
Secure
Communication Protocols (SSL, TLS, VPN)
|
When a user
logs into their bank account from a web browser, the username and password
are encrypted using TLS when it is sent from their browser to the bank
servers
|
|
Data in Use
|
Exposure
during processing or in-memory attacks
|
Using PETs
such as confidential computing or homomorphic encryption
|
A payment
processor uses confidential computing to process customers’ credit card
information inside a hardware-protected secure enclave, reducing the risk of
data exposure during processing
|
Compare the risks, protections, and examples for data at rest, data in transit, and data in use. section 14.3.1


