By: Hassan Waqar
A PROTOCOL for securely transmitting data via the internet. NETWORK LAYER application. Developed by NETSCAPE.
When a web browser accesses a site secured by an SSL certificate, the following events happen: “SSL Handshake”
Browser (client) asks the server (website) for its identity. Server provides its SSL Certificate. Browser examines validity of the certificate.
If trusted, the browser sends confirmation to server. The web server replies with a digitally-signed message that starts SSL-encrypted exchange of information (“session”).
Uses PUBLIC KEY and PRIVATE KEY to encrypt data. Server sends the public key. Browser (client) checks to ensure it trusts the server.
The private key is used to encrypt information passed to the browser, which can then be decrypted with the public key.
128-bit keys It allows 340,282,366,920,938,463,463,374,607,431,76 8,211,456 unique encryptions codes.
1. Authentication between client and server: cryptographic techniques. 2. Ensuring data integrity. 3. Securing data privacy.
1. Domain Validation (DV) For the domain to approve the CSR. Validate domain owner and what they intend to use the domain for.
2. Organization Validation (OV) “high assurance” certificates ensures the identity of the domain owner aids in identifying potential “phishing” activities.
3. Extended Validation (EV) display the green URL bar promise users the safest possible experience checks the identity and confirms the authenticity.
Admin issues a Certificate Signing Request. CA validates information and issues SSL Certificate Admin installs certificate on the server. Expires within 1 to 3 years.
SSL has more recently known as Transport Layer Security (TLS).
ure_socket_layer.html ure_socket_layer.html Layer Layer