Skip to content

Encryption in transit and at rest

What TLS does and does not promise, what handshakes cost, which at-rest layer stops which attacker, and why an AES-GCM key has a usage limit.

25 min6 steps

By the end you can
  • Explain what TLS guarantees, what it does not, and why internal traffic needs it too
  • Estimate handshake load and the effect of session resumption
  • Choose between disk, database and application-level encryption for a given threat
  • Explain why authenticated encryption keys have usage limits and nonces must never repeat

What TLS promises

TLS 1.3 gives confidentiality, integrity, server authentication and, via ephemeral keys, forward secrecy. It ends at your server (logs, database see plaintext). HSTS stops http:// downgrade.

ClientServerClientHello + key shareServerHello + certificate + signatureFinished: encrypted from here
Protects the wire, not either endpoint.

Your login page is served over TLS 1.3 with a valid certificate. Which of these does TLS protect against?

Answer this step to continue.