EmailCall us at 02269718986

SSL

Also known as: Secure Sockets Layer, SSL/TLS, TLS

What is SSL?

SSL (Secure Sockets Layer) is a security protocol that provides privacy, authentication, and data integrity for internet communications. It was originally developed by Netscape in 1995 and later evolved into TLS (Transport Layer Security), which is now the standard. SSL ensures that data transmitted between a user's browser and a server remains encrypted and secure, preventing unauthorized access or tampering.

How SSL Works

SSL operates through a process called the SSL handshake, which establishes a secure connection between the client (web browser) and the server. Here's a simplified breakdown:

1. Client Hello: The browser sends a 'Hello' message to the server, including supported SSL/TLS versions and cipher suites. 2. Server Hello: The server responds with its chosen SSL/TLS version, a session-specific key, and its digital certificate. 3. Certificate Verification: The browser checks the server's certificate against a list of trusted Certificate Authorities (CAs). 4. Key Exchange: The browser and server exchange keys to create a shared secret for encryption. 5. Encrypted Communication: All subsequent data is encrypted using the shared secret.

!SSL Handshake Diagram

Example of SSL in Action

When a user visits https://example.com, the browser initiates an SSL handshake with the server. The server provides its SSL certificate, which includes a public key. The browser verifies the certificate's validity and generates a symmetric session key. This key is encrypted using the server's public key and sent back. The server decrypts it with its private key, and both parties use the session key to encrypt all further communication. For instance, if the server uses an RSA key with 2048-bit encryption, the session key is securely exchanged and used for data transmission.

When You Use SSL / When You Don't

Use SSL when:

  • Handling sensitive user data (e.g., login credentials, payment information).
  • Ensuring trust and credibility for your website.
  • Complying with security standards like PCI DSS.
Avoid SSL when:
  • The website does not handle sensitive data.
  • Performance is a critical concern (though modern implementations minimize overhead).
  • You're using a local development environment without public exposure.

Related Concepts

Internal Links

Related terms

TLSHTTPSCertificate AuthorityEncryptionPublic KeyPrivate KeyHandshakeData IntegrityAuthenticationWeb SecurityTransport Layer SecuritySecure Communication