# Transport Layer Security \(TLS\)

A cryptographic protocol that authenticates endpoints and protects network data from eavesdropping and modification in transit.

- Type: framework
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/transport-layer-security/>)

## What it means

Transport Layer Security \(TLS\) establishes an authenticated, encrypted channel between network peers. A handshake negotiates parameters, validates certificates or other credentials, and derives temporary traffic keys. HTTPS is HTTP carried over TLS, not a separate replacement for HTTP semantics.

## Why it matters

TLS protects credentials, sessions, personal data, and application messages from network interception and tampering. Correct identity validation also reduces redirection to an impersonating endpoint.

## When to use it

Use current TLS for public and private network traffic that crosses a trust boundary, including web, API, database, and service connections. Add mutual TLS when both peers need certificate-based authentication and its lifecycle cost is justified.

## How it works

1. The client connects and offers supported protocol versions and cryptographic parameters.
2. The server presents its identity certificate and key agreement information.
3. The client validates the certificate chain, hostname, validity, and policy.
4. Both peers derive session keys and confirm the handshake transcript.
5. Application data travels with confidentiality and integrity protection.
6. Operators renew certificates, retire weak configurations, and monitor failures and expiry.

## A practical example

A browser connects to an HTTPS checkout page, validates the certificate for the requested hostname, negotiates TLS 1.3, and sends payment-session traffic through the encrypted channel before HTTP processing begins.

## Where it breaks

TLS protects data only between its endpoints and does not make application content safe or authorized. Compromised endpoints, trusted interception proxies, certificate mistakes, metadata exposure, and downgraded configurations remain risks.

## Common mistakes

- Disabling certificate or hostname validation to make a connection work.
- Calling HTTPS encryption at rest or proof that a site is trustworthy.
- Keeping obsolete protocol versions and weak cipher configuration enabled.
- Failing to automate certificate renewal and expiry monitoring.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/transport-layer-security/#visualization-transport-layer-security>)

## Sources

1. [The Transport Layer Security \(TLS\) Protocol Version 1.3 \(RFC 8446\)](<https://www.rfc-editor.org/rfc/rfc8446>) — RFC Editor · Internet Standard
2. [Transport Layer Security Cheat Sheet](<https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html>) — OWASP Foundation · Security practice guidance

## Related topics

- [HTTP](<https://wiki.soroush.uk/topic/http/>)
- [Encryption](<https://wiki.soroush.uk/topic/encryption/>)
- [Authentication](<https://wiki.soroush.uk/topic/authentication/>)
