Transport Layer Security
What is Transport Layer Security?
A cryptographic protocol that secures communications over computer networks, widely used to protect web traffic, email, and other data transmissions.
Frameworks that govern transport layer security
What the standards actually require on transport layer security
Requirements naming transport layer security across 4 standards, quoted from the control text.
350.0-G-3 sec.5.5: applying security at the transport layer (e.g. for the Space Packet Protocol) where appropriate.
CCSDS350-5.5 · Transport Layer Security →Communications between authenticators and a RADIUS server are encapsulated with an additional layer of encryption using RADIUS over Internet Protocol Security or RADIUS over Transport Layer Security.
ISM-1454 · Encapsulating RADIUS communications with IPsec or TLS →HL7 FHIR Transport Security. TRANSPORT LAYER SECURITY (TLS) - all FHIR APIs MUST use TLS 1.2+ for production + TLS 1.3 recommended; certificate validation + trust chain + certificate pinning where appropriate + HSTS + secure session establishment + cipher suit...
HL7-FHIR-Transport-TLS-Communication · HL7 FHIR Transport Security - TLS 1.2+, Communication Security, Time Keeping, Server CapabilityStatement →To prepare for the transition to new public-key algorithms, agencies support Transport Layer Security version 1.3 or a successor version as soon as practicable and no later than 2 January 2030, under requirements issued by 1 December 2025 by the Director of NS...
us-executive-order-14144-strengthening-and-promoting-innovation-in-the-nations-cybersecurity::4(f)(ii) · Sec. 4(f)(ii) Support TLS 1.3 or a successor by 2 January 2030 →Questions people ask about transport layer security
What is Transport Layer Security?
Why is Transport Layer Security important for compliance?
Which compliance frameworks address Transport Layer Security?
Where can I learn more about Transport Layer Security?
See how Transport Layer Security applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.