TLS

The encryption that protects data travelling over a network, the S in HTTPS.

In more detail

TLS stands for Transport Layer Security; SSL is the name of its older, retired predecessor. It encrypts the connection, and the server proves who it is with a certificate that the client checks against trusted certificate authorities. As a result, passwords, cookies and tokens cannot be read or changed on the way.

Examples

In the APIs course: The course repeats that credentials must only travel over protected transport, which in practice means HTTPS.
EFS mounts and HTTPS load balancer listeners use TLS for encryption in transit.
In the browser: TLS stands for Transport Layer Security. After the TCP connection opens, the browser and server run a TLS handshake: the server proves who it is with a certificate and both sides agree on session keys. Everything sent afterwards, including cookies and page content, is encrypted.
TLS is terminated at the Ingress controller with certificates from cert-manager.
ssl.create_default_context(cafile="ca.pem") checks both the chain and the host name
TLS stands for Transport Layer Security; SSL is its obsolete predecessor. It encrypts application bytes in transit, detects tampering and authenticates the server with a certificate. It protects only the connection between the two endpoints that negotiated it: it does not make a compromised server safe or hide metadata such as the destination address.
enc=y int=y auth=y app=no lists what TLS promises and what it does not.
Cookies with the Secure attribute are only sent over TLS connections.
A new python.org Python on macOS cannot verify certificates until Install Certificates.command has run.
Old TLS versions where modern ones are normal can indicate a downgrade attack.

Related terms

Taught in

References

Certification courses