Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
TLS (Transport Layer Security) is the cryptographic protocol that encrypts data travelling across networks and verifies the identity of servers, protecting web, email, and API traffic.

What Is TLS (Transport Layer Security)?
TLS, or Transport Layer Security, is the protocol that protects data as it travels across a network. It provides three guarantees: confidentiality, so eavesdroppers cannot read the traffic; integrity, so data cannot be altered in transit without detection; and authentication, so the client can confirm it is talking to the genuine server. Every HTTPS website, most email transfer between servers, VPNs, and countless APIs rely on it.
TLS is the successor to SSL (Secure Sockets Layer), developed by Netscape in the 1990s. People still say “SSL certificate” out of habit, but every version of SSL is now obsolete and insecure. What runs today is TLS.
| Version | Released | Status |
|---|---|---|
| SSL 2.0 and 3.0 | 1995, 1996 | Prohibited; SSL 3.0 broken by the POODLE attack in 2014 |
| TLS 1.0 and 1.1 | 1999, 2006 | Formally deprecated in 2021 (RFC 8996) |
| TLS 1.2 | 2008 | Still widely used and secure when configured well |
| TLS 1.3 | 2018 | Current version, faster and simpler, recommended |
Before any application data is sent, client and server perform a handshake. In TLS 1.3 it works roughly like this:
TLS 1.3 completes this in a single round trip, compared with two in TLS 1.2, which makes connections noticeably faster.
TLS 1.3 removed many features that had caused vulnerabilities over the years. Static RSA key exchange is gone, so every connection uses ephemeral Diffie-Hellman keys and benefits from forward secrecy: even if a server’s private key is stolen later, past sessions cannot be decrypted. Weak algorithms such as RC4, SHA-1, CBC-mode ciphers, and compression were dropped, and more of the handshake is encrypted. The result is a protocol that is much harder to misconfigure.
Most real-world TLS problems come from implementation flaws or poor configuration rather than the protocol design:
Free tools such as the Qualys SSL Labs server test give a quick view of how a public site is configured. The NCSC also publishes guidance on using TLS to protect data.
Large quantum computers could one day break the key exchange algorithms TLS relies on today. Attackers may already be recording encrypted traffic to decrypt later, a threat known as “harvest now, decrypt later”. Major browsers and content delivery networks have therefore begun using hybrid post-quantum key exchange, combining classical X25519 with the ML-KEM algorithm standardised by NIST in 2024.
At Privia Security, our Infrastructure Security Testing Services review TLS configurations across your external and internal services, identifying weak protocols, ciphers, and certificate issues.
TLS is the successor to SSL. All versions of SSL are obsolete and insecure, and modern systems use TLS 1.2 or 1.3. The term “SSL certificate” has stuck as everyday shorthand, but the certificates themselves work with TLS. When someone talks about SSL today, they almost always mean TLS in practice.
HTTPS means the connection between your browser and the site is encrypted and that the site holds a valid certificate for its domain. It does not mean the site is trustworthy. Phishing sites routinely use free certificates, so the padlock shows that nobody can eavesdrop, not that the people running the site are honest.
Not yet for most organisations. TLS 1.2 remains secure when configured with modern cipher suites, and many clients and partners still depend on it. The recommended approach is to support both TLS 1.3 and 1.2, disable everything older, and plan to retire 1.2 once your users and integrations fully support TLS 1.3.
In standard TLS, only the server proves its identity with a certificate. In mutual TLS, the client also presents a certificate, so both sides authenticate each other. It is widely used for service-to-service communication in microservice architectures, for API security between organisations, and in Zero Trust designs that require strong device identity.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is a Cloud-Native Application Protection Platform?
Read MoreWe use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.