Secure Sockets Layer (SSL)

SSL is the original protocol for encrypting web connections, now retired as insecure and replaced by TLS, though "SSL" is still used as a name for TLS.

Secure Sockets Layer (SSL) is the original protocol for encrypting and authenticating connections between a client, such as a web browser, and a server. Its versions had serious flaws and have been formally deprecated; Transport Layer Security (TLS) replaced it and is what secures HTTPS, email and most other encrypted connections today. The name survives in everyday use: an “SSL certificate,” “SSL VPN” or “SSL offload” almost always means TLS. For buyers, SSL matters in two ways: making sure the old protocol is actually switched off, and managing the certificates still sold under its name.

At a glance

  • SSL 2.0 and 3.0 are insecure and retired; TLS is the replacement, with TLS 1.2 and 1.3 the versions in current use.
  • “SSL certificate” usually means a certificate used with TLS; the certificate itself doesn’t depend on the protocol version.
  • Certificates prove a server’s identity; the protocol uses them to set up encrypted, tamper-evident connections.
  • Common problems are old protocol versions left enabled and expired or untracked certificates.
  • Security and compliance frameworks generally expect strong, current encryption in transit; check the specific requirements that apply to you.

What problem it solves

Data sent over a network can be read or altered by anyone positioned along the path, from a shared Wi-Fi network to a compromised router. Without encryption, passwords, payment details and business data travel in readable form, and a user has no way to confirm they are talking to the real site rather than an impostor running a man-in-the-middle attack.

SSL addressed this for the early web by encrypting traffic and letting browsers verify a server’s identity through certificates. As attacks against SSL’s design were found, TLS took over the same job with stronger cryptography. The practical problem for organizations today is less “should we encrypt?” than keeping that encryption current: old SSL or early TLS versions left switched on for compatibility, weak cipher settings, and certificates that expire without warning and take services offline.

How it works

Handshake. When a client connects, it and the server agree on a protocol version and cipher suite. The server presents its certificate, the client checks it, and the two sides set up shared session keys. TLS 1.3 streamlines this and drops older, weaker options.

Certificates. A certificate binds a domain name, and sometimes an organization’s identity, to a public key, and is signed by a certificate authority (CA) that browsers and operating systems trust. This system is called public key infrastructure (PKI). Validation levels are domain-validated (DV), organization-validated (OV) and extended validation (EV). One certificate can cover several hostnames, or all first-level subdomains with a wildcard.

Encrypted session. Once the handshake completes, data is encrypted and integrity-checked in both directions.

Why SSL was retired. Over time researchers found practical attacks on SSL 2.0 and 3.0, such as the POODLE attack on SSL 3.0, and the standards body behind them formally deprecated both. TLS 1.0 and 1.1 have since been deprecated as well. Mainstream browsers and current server software disable these versions by default, but older appliances, embedded devices and legacy applications may still offer them.

Where encryption terminates. Content delivery networks, load balancers and web application firewalls often end the encrypted connection to inspect or speed up traffic, then re-encrypt it to the origin server. Security tools on outbound traffic may also decrypt it under policy; see TLS inspection.

When it matters for buyers

  • Security scans and penetration tests. Findings of SSL 3.0 or TLS 1.0 enabled usually mean an older system or default setting needs updating.
  • Audits and compliance. Payment card rules, healthcare rules and customer security questionnaires address encryption in transit. PCI DSS, for example, no longer treats SSL or early TLS as strong cryptography; HIPAA treats encryption in transit as a safeguard to assess. Exact obligations depend on the framework version and your circumstances, so confirm them with your assessor or counsel.
  • Certificate outages. An expired certificate can take a website, API or VPN offline instantly; shorter certificate lifetimes increase renewal volume. See certificate lifecycle management.
  • Buying certificates. Many sites need only DV certificates, which many CAs issue automatically and some at no cost; OV or EV may be required by specific customers or policies.
  • CDN, WAF and load balancer projects. Decide where encryption ends, how traffic is protected to the origin, and who holds the private keys, sometimes in a hardware security module (HSM).

Questions to ask vendors

  • Which protocol versions and cipher suites does your service or appliance support, and can we disable SSL and TLS 1.0 and 1.1?
  • Do you support TLS 1.3?
  • If you terminate encryption, do you re-encrypt to our origin, and do you validate our origin certificate?
  • Who manages certificates on your platform, and do you support automated issuance and renewal?
  • Can we bring our own certificates and keep private keys in our own key management system or HSM?
  • What reporting do you provide on protocol versions in use, certificate expiry and handshake errors?

Edge services such as web application and API protection and content delivery networks commonly handle encryption and certificates at scale for public sites.

How it differs from TLS

SSL and TLS do the same job: set up an encrypted, authenticated connection using certificates. TLS is the successor, created from SSL 3.0 and since revised several times to remove weak cryptography and simplify the handshake. Every SSL version is now considered insecure, while TLS 1.2 and 1.3 are the versions in current use. Because the older name stuck, “SSL” in product names, certificate listings and vendor documents almost always refers to TLS. When a vendor or auditor says “SSL,” ask which protocol versions they actually mean.

Problems this helps with

  • A security scan flagged old SSL or TLS versions on our servers
  • An expired SSL certificate took down a customer-facing site
  • Old devices or partners that still only connect with outdated SSL settings
  • Not sure what kind of SSL certificate we actually need

Frequently Asked Questions

Is SSL the same as TLS?
No. TLS is the successor to SSL. The SSL versions are considered insecure and are disabled by default in current mainstream browsers and most servers, but the name stuck: an "SSL certificate" or "SSL VPN" today normally uses TLS.
Do I need an EV certificate?
Usually not. Domain-validated (DV) certificates provide the same encryption and suit many sites. Organization-validated (OV) and extended-validation (EV) certificates add vetted company details, which some customers or policies ask for, but current browsers no longer display them prominently.
What is SNI and why does it matter?
Server Name Indication (SNI) lets a client send the hostname it wants at the start of the TLS handshake, so one server or IP address can present the right certificate for many sites. It is supported by modern clients; very old ones may fail on shared hosting.
Should we decrypt at the CDN and send plain traffic to our servers?
Generally not for anything sensitive. If a CDN, load balancer or web application firewall terminates TLS, re-encrypting traffic from it to your origin servers keeps data encrypted along the whole path. Many providers support this and can validate your origin's certificate.
Which protocol versions should we allow?
Current guidance is to disable SSL 2.0 and 3.0 and TLS 1.0 and 1.1, and allow TLS 1.2 and 1.3 with modern cipher suites. Check what any older clients, devices or partner systems need before switching off old versions, and test the change.
How do we avoid outages from expired certificates?
Keep an inventory of every certificate and what uses it, automate issuance and renewal where you can, for example with the ACME protocol, and alert well before expiry. Public certificate lifetimes are getting shorter, which makes manual renewal harder to sustain.

Get a Straight Answer in 30 Minutes

30 minutes. No pitch. Just an honest conversation about where you are, what you need, and whether working together makes sense.

By submitting, you agree to our Terms of Use and Privacy Policy.

We use your details to set up and prepare for the call, and send the newsletter only if you ask for it. We may follow up about your request; you can opt out at any time.