Working with SSL

SSL (Secure Sockets Layer) is the standard security technology for establishing an encrypted link between a web server and a browser. This link ensures that all data passed between server and browser remain private and integral. SSL is an industry standard to protect the online transactions.

Secure Sockets Layer (SSL) is the most widely deployed cryptographic protocol to provide security over internet communications. SSL provides a secure channel between two machines or devices operating over the internet or on an internal network. One common example is when SSL is used to secure communication between server and browser is, the website's address will change from HTTP to HTTPS, the S stands for Secure.

Need of SSL: As it supports the following security principles

• Encryption: Protect data transmissions, for ex: browser to server, server to server, application to server etc..
• Authentication: Ensures that the server you are connected is the correct server
• Data Integrity: Ensures that the data that is requested or submitted is what is actually delivered

And, can be used for:

• Internet based traffic such as networks, file sharing, extranets and database connections
• The transfer of files over HTTPS and FTP(s) services
• Webmil servers like outlook, exchange and office communications etc.
• System logins to applications and control panels, namely parallels, cPanel and others
• Hosting control panel logins
• Online credit card and other payment type transactions

Advantages of using SSL:

• Trust: If user gets a green address bar in the browser, they consider the site as trusted site
• Verification: One of the best thing about installing SSL certificate on your server is that it guarantees the visitors you really are who you say you are
• Integrity of Data: With SSL, you can guarantee integrity of data

Advantages of using SSL:

• Cost of Certificte: As it is not recommended to use free SSL certificates, depending on the type of certificate, price changes
• Mixed Modes: if the SSL setup is not correct, then you still have some files served via HTTP instead of HTTPS where visitors are going to get a warning message in their browser letting them know some of the data is not protected. This can be confusing to the users
• Proxy Caching: Anther possible problem is if you have a complex proxy caching system setup on your web server. Encrypted content is not going to be able to be cached. To get around this, you need to add a server to handle the encryption before it bets to the caching server. This will require additional cost
• Mobile: SSL was first implemented for web based applications. while the ability to go beyond HTTPS has come a long way in the last few years, it can sometimes be a pain to setup and might require changes to in-house software.