Data in Transit
What is Data in Transit?
Data that is actively moving from one location to another, such as across the internet or through a private network. Protecting data in transit typically requires encryption protocols such as TLS/SSL.
Terms that appear alongside data in transit
Each of these is named in at least one of the same controls as data in transit. The number is how many controls name both.
- encryption 19 shared controls
- tls 9 shared controls
- integrity 8 shared controls
- data in transit encryption 7 shared controls
- data at rest 6 shared controls
- confidentiality 6 shared controls
- fips 5 shared controls
- nist 4 shared controls
Frameworks that govern data in transit
What the standards actually require on data in transit
Requirements naming data in transit across 6 standards, quoted from the control text.
An ASD-Approved Cryptographic Protocol (AACP) or high assurance cryptographic protocol is used to protect data when communicated over network infrastructure.
ISM-0469 · Encrypting data in transit →Personal data exchanged between the device and associated services (typically cloud services the manufacturer controls) are kept confidential using best practice cryptography that suits the technology, the environment, the risk and how the device is used.
etsi-en-303-645::Provision 5.8-1 · Personal data in transit to associated services protected →Agencies must encrypt all agency data while it travels between the agency and the mobile device (see Chapter 17, Cryptography).
new-zealand-information-security-manual-nzism::21.4.13.C.01 · 21.4.13.C.01 Encrypt agency data in transit to BYOD →The plan must require that all IAC data in transit is authorised, validated and protected according to its classification; that the risk to moving data that starts in, ends in or crosses Baseline Profile zones is identified;
api-1164::PR.DS-2 · PR.DS-2 Data in transit protected within zones and across internal, intermediate and external conduits →For selected data categories, all data in transit is protected, for example with encrypted protocols, data masking or a virtual private network where needed.
australian-energy-sector-cyber-security-framework-aescsf::ARCHITECTURE-5c · ARCHITECTURE-5c: All data in transit protected for selected categories →Enforce TLS 1.2 or higher for all data in transit and disable legacy protocols across Azure services.
DP-3 · Encrypt sensitive data in transit →Questions people ask about data in transit
What is Data in Transit?
Why is Data in Transit important for compliance?
Which compliance frameworks address Data in Transit?
Where can I learn more about Data in Transit?
See how Data in Transit applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.