SSL and WAF: Brief Info and Explanation
SSL
As already known (Secure Sockets Layer) is nothing but an encrypted cipher-based Pub-Pvt Key (Size of the key depends on chosen key length) pair wherein the Public Key is issued by a known Certificate Authority (CA) which in turn is again identified by another or same Intermediate Certificate Authority (ICA). This public key is then paired with a private key information to which is only known to the originator of the certificate request. (CSR)
This SSL acts as a layer of security for the HTTP based communication over the web making it HTTP(S). Wherein an end-client executes any transaction/sends any information in plain text and the data is processed by the server.
This plain text is encrypted by the public key in the communication sent from the end-client and the same is decrypted with the help of private key only available to the originator/responding host server. This way the SSL helps cipher and decipher the plain text data after transit and let it travel more safely while in transit.
However, SSL is not itself sufficient enough to safeguard the traffic between the client and the server communication. So there comes in aid, WAF i.e. Web Application Firewall
WAF
This is an application which again uses either own SSL server or Host Server's SSL certificate to decrypt the incoming request and check for possible threats from around the web as available in its registered and regularly updated threat record database. It then filters those requests and responds them from WAF end only.
Those requests which are found malicious are blocked and same is responded then and there from WAF only. And only those requests are forwarded further to actual HOST Server which are not malicious, which pass all the preliminary tests of the WAF layer.
So, WAF in addition to SSL helps you add value to the overall security layer provided to the data in transit.
However, same SSL need not be placed in both the communication channels. If you check the two images above carefully, you will be able to find that the communication with END CLIENT and WAF and then between WAF and HOST Server are two different communication channels.
And both the channels can run on different ports internally with different SSL for each communication. The mentioned heterogenous design of this communication is what makes it more difficult against man-in-the-middle attacks as well as request interception.
And the internal architecture after WAF can again be more complex and yest helpful to the end-client for data security. This can be your WEB->APP->DB layer.
Check your WAF and SSL settings for security logs
ReplyDelete