When you prepare your web server to use HTTPS you will be asked a few questions about your website and your company including your web site's domain name and your company's name and location. Your web server then creates two cryptographic keys: a private key and a public key. Your private key must remain private or the HTTPS connection could be made vulnerable. The public key does not need to be secret and is placed into a Certificate Signing Request or CSR, a piece of encrypted text that you will submit to a certificate authority. The certificate authority will validate your details and issue the SSL certificate which you can then install to the web server with the private key to enable HTTPS. For more information, see SSL For Newbs.
You can enable or disable HTTPS scanning from SafeSquid HTTPS inspection section.
How does HTTPS inspection work with SafeSquid? 1. When user/client request a secure webpage say https://www.xyz.com (a HTTPS site) from the browser, SafeSquid will get CONNECT request from the client browser. 2. SafeSquid will check configuration ...
Overview Over the couple of years, the internet is changing its dimensions in terms of security. The web is shifting towards HTTPS, to deliver secure services to users. “The main motivation for HTTPS is authentication of the visited website and ...
Access the SafeSquid interface Go to Configure Page Open Real time content security side menu Open HTTPS Inspection section Enable HTTPS Inspection Note: In newer versions of SafeSquid which are released after June-2017, setup tab is removed. You ...
Business challenge The HTTPS inspection Bypass option enables you to define specific websites that are not subject to decryption as they flow through the proxy. Some websites may include personal identification information that should not be decrypt. ...
Importance of Certificates/ Why HTTPS-aware applications, like Internet Browsers, use SSL/TLS protocols to prevent communication with malicious web services. The SSL / TLS protocols enable applications to verify the identity of the remote web ...