Cybersecurity glossary
What is TLS 1.2?
Learn what TLS 1.2 is, how its handshake and cipher suites work, which insecure options to disable, and how it compares with TLS 1.3 for modern deployments.
Definition
TLS 1.2 is a Transport Layer Security protocol version standardized in RFC 5246 that authenticates endpoints, negotiates cryptographic parameters, and encrypts application data; it remains widely deployed but requires careful configuration to avoid obsolete cipher suites and lacking forward secrecy.
Why TLS 1.2 is still everywhere
Enterprise appliances, older clients, and long-lived backends made TLS 1.2 the compatibility baseline for a decade. It can be strong, but unlike TLS 1.3 it still allows insecure historical choices unless operators deliberately remove them.
What TLS 1.2 negotiates
Version and extensions
ClientHello/ServerHello agree on TLS 1.2 and features such as SNI and ALPN.
Cipher suite
Selects key exchange, authentication, bulk cipher, and MAC/AEAD behavior.
Certificates
Server (and optionally client) X.509 identities are validated.
Record protection
Application bytes are encrypted after keys are derived.
Simplified TLS 1.2 handshake
ClientHello
Client offers versions, cipher suites, and extensions.
ServerHello and certificate
Server chooses parameters and presents its certificate chain.
Key exchange
ECDHE shares (recommended) establish a shared secret.
Finished messages
Both sides confirm the handshake transcript under the new keys.
Encrypted application data
HTTP or other protocols ride inside TLS records.
TLS 1.2 configuration targets
Treat defaults as hostile until proven otherwise.
| Area | Prefer | Disable |
|---|---|---|
| Versions | TLS 1.2 (+1.3) | SSL, TLS 1.0/1.1 |
| Key exchange | ECDHE | RSA key transport, static ECDH |
| Bulk crypto | AES-GCM, ChaCha20-Poly1305 | RC4, 3DES, NULL |
| Certificates | Valid chain + SAN match | Expired, wrong-name, incomplete chain |
Operational checklist
- Enable TLS 1.3 alongside hardened TLS 1.2 when clients allow.
- Allow only forward-secret AEAD cipher suites.
- Turn off compression and obsolete renegotiation anti-patterns per current guidance.
- Serve full intermediate chains and monitor certificate expiry.
- Test with SSL Labs or equivalent scanners after every config change.
- Use HSTS on HTTPS sites to reduce downgrade and stripping risks.
- Separate old break-glass profiles from internet-facing baselines.
- Document exceptions for legacy clients with expiration dates.
Compatibility is not a blank check
Keeping TLS 1.2 for a stubborn scanner or embedded client is sometimes necessary. Keeping RSA-export nostalgia “just in case” is not. Scope exceptions narrowly and instrument who still negotiates weak suites.
The practical takeaway
TLS 1.2 remains a viable secure transport when stripped of legacy cipher suites and configured for ECDHE AEAD. Prefer adding TLS 1.3, and treat every remaining exception as tracked risk.
Related security terms
TLS 1.3
The newer TLS version with a simplified handshake and AEAD-only record protection.
Cipher Suite
Named algorithm sets TLS 1.2 negotiates during the handshake.
TLS Handshake
The negotiation sequence that establishes TLS 1.2 session keys.
Forward Secrecy
A property you must explicitly select via ECDHE/DHE suites in TLS 1.2.
SSL/TLS
The broader protocol family TLS 1.2 belongs to.
Frequently asked questions
What is TLS 1.2 in simple terms?
It is a widely used version of the protocol that secures HTTPS and other encrypted network services by authenticating servers and encrypting traffic.
Is TLS 1.2 still safe?
Yes when configured well: modern AEAD cipher suites, ECDHE forward secrecy, strong certificates, and disabled legacy options. Misconfigured TLS 1.2 can still be weak.
Should I disable TLS 1.0 and 1.1?
Yes on modern services. Keep TLS 1.2 and preferably TLS 1.3 only.
Does TLS 1.2 always provide forward secrecy?
No. Only suites that use ephemeral key exchange (ECDHE/DHE) provide it. RSA key-transport suites do not.
Why prefer TLS 1.3 if 1.2 is OK?
TLS 1.3 removes obsolete options by design, simplifies the handshake, and hardens defaults. It reduces configuration footguns.
What cipher suites should TLS 1.2 use?
Prefer ECDHE with AES-GCM or ChaCha20-Poly1305. Disable RC4, 3DES, export, NULL, and anonymous suites.
Is SSL 3.0 related to TLS 1.2?
SSL 3.0 is an obsolete predecessor. It must be disabled; do not confuse marketing “SSL” labels with protocol versions.
References
Explore authoritative guidance and frameworks related to tls 1.2.
Explore every security definition
Return to the glossary to search by term, alias, starting letter, or security category.