• Glossary
  • What is SSL (secure sockets layer)?

Security glossary

What is SSL (secure sockets layer)?

SSL (secure sockets layer) is a security protocol that encrypts and authenticates communication between a client and a server. It was the predecessor of transport layer security (TLS), and all SSL versions are now deprecated, though the name remains in common use for TLS.

Let's simplify your DDI
Abstract isometric UI showing network ranges, usage bars, region names (EMEA/APAC), and a purple "Deploy" button
Key takeawaysKey takeaways are generated with AI assistance. Because automated summaries can occasionally contain errors or miss important context, always refer to the full blog post for complete information.

SSL (Secure Sockets Layer) is a deprecated security protocol that once encrypted and authenticated communication between clients and servers through a handshake process involving digital certificates and shared encryption keys. All SSL versions have known design weaknesses and have been prohibited by the IETF, replaced by the standardized TLS (Transport Layer Security) protocol that is used for secure connections today. Organizations must disable all SSL versions on servers, load balancers, and appliances while implementing regular protocol scans and certificate management practices to eliminate security gaps and ensure only secure TLS negotiation occurs.

  • The IETF formally prohibited SSL version 2 in RFC 6176 and SSL version 3 in RFC 7568 after attacks such as POODLE demonstrated the protocol could not be made safe.
  • Certificate inventory, renewal tracking, and careful decryption policies are essential operational practices for monitoring encrypted TLS traffic and preventing outages caused by expired or mismatched certificates.
  • Regular protocol scans using TLS testing tools against all listeners including load balancers and management interfaces are required to verify that servers negotiate only TLS and not legacy SSL versions.

SSL at a glance

AttributeValue
Full nameSecure sockets layer
CategorySecurity protocol (deprecated)
Primary useEncrypting and authenticating traffic between a client and a server
Related termsTLS, Certificate authority, Public key infrastructure, HTTPS

How SSL works

SSL protects data in transit by negotiating shared encryption keys between a client and a server, after the server proves its identity with a digital certificate. The same handshake model carried over into TLS.

  1. Client hello: The client opens the connection and sends the protocol version it supports and a list of cipher suites it can use.
  2. Server hello and certificate: The server selects a version and cipher suite and sends its digital certificate, which contains its public key and is signed by a certificate authority.
  3. Certificate validation: The client checks that the certificate is signed by a trusted authority, has not expired and matches the server name it intended to reach.
  4. Key exchange: The client and server use public key cryptography to agree on a shared secret, from which session keys are derived.
  5. Encrypted session: Both sides switch to symmetric encryption with the session keys and exchange application data protected for confidentiality and integrity.

The steps above describe the general handshake pattern. SSL itself has known design weaknesses in every version, which is why the IETF replaced it with TLS. Current software should negotiate TLS only, even where configuration menus and certificate products still say SSL.

Why SSL matters in enterprise networks

The term SSL persists in product names, certificate marketing and configuration screens, even though the protocol is obsolete. The IETF prohibited use of SSL version 2 in RFC 6176 and SSL version 3 in RFC 7568, after attacks such as POODLE showed SSL 3.0 could not be made safe. Teams that read SSL as meaning secure can leave outdated protocol versions enabled on servers, load balancers and appliances.

The practical risk is a gap between what administrators believe is deployed and what is actually negotiated. A server that still accepts SSL 3.0 can be forced into a downgrade, exposing session data to attack. Regular scans of endpoints for supported protocol versions and cipher suites, along with disabling all SSL versions, close this gap.

Encrypted traffic also affects monitoring. Security tools that inspect encrypted sessions must work with TLS, and decryption policies need careful scope, certificate handling and privacy review. Expired or mismatched certificates cause outages and user warnings, so certificate inventory and renewal tracking are part of operating any encrypted service.

SSL vs TLS

SSL is the older, deprecated family of protocols, while TLS is its standardized successor and the protocol actually used for secure connections today. What is TLS?

AttributeSSLTLS
StatusAll versions deprecatedCurrent; TLS 1.2 and 1.3 are widely deployed
StandardizationDeveloped before IETF took over the protocolSpecified by the IETF, starting with TLS 1.0
Known weaknessesSSL 3.0 is vulnerable to attacks such as POODLEOlder TLS versions have weaknesses, but current versions address them
Use in namingPersists as a generic label in products and certificatesTechnically accurate name for the protocol in use

Common misconceptions about SSL

Certificates sold as SSL certificates are X.509 certificates that work with TLS. Buying one does not mean the server negotiates SSL, and the name does not indicate the protocol version in use.

Some teams keep SSL 3.0 enabled for legacy clients because the connection still works. The IETF prohibited it in RFC 7568, and it is open to attacks such as POODLE.

Administrators sometimes fear that turning off SSL options will stop encrypted traffic. Modern clients use TLS, so disabling SSL versions affects only very old clients.

Firewall features named SSL decryption usually inspect TLS traffic by acting as a proxy with a trusted intermediate certificate. They do not exploit protocol flaws, and they need careful policy and certificate distribution.

See how unified DDI simplifies network operations

Manage DNS, DHCP and IP addresses from one platform with automation, visibility and control built in.

Talk to us

SSL FAQ

Related terms

Article

Transport layer security (TLS)

A cryptographic protocol to provide communications security over a computer network.

Learn more
Article

TCP

A protocol that provides reliable, ordered, and error-checked delivery of bytes between applications running on hosts communicating via an IP network; part of the TCP/IP suite.

Learn more
Article

DNSSEC (Domain Name Service Security Extension)

A mechanism that uses cryptography to provide authentication and integrity for DNS queries.

Learn more
Article

DMZ (Demilitarized zone)

A subnetwork that contains and exposes an organization’s external-facing services to an untrusted, usually larger, network such as the internet.

Learn more
Article

Transaction Signature (TSIG)

A protocol that enables DNS to authenticate updates to a DNS database; most commonly used to update dynamic DNS or a secondary DNS server.

Learn more
Article

DNS – Domain Name System

A hierarchical naming system that enables communication across devices in a network.

Learn more
Browse the full glossary