Quote:
Originally Posted by Hank
But, I can't see why we're challenging that the Webwise system won't be able to detect calls between my PC and the web to start a session with a secure site. AFAIK the set up of the secure connection cannot OC begin until a connection has been at least made with the site to set it up because the site server and my PC have to exchange some data to set it up and that cannot be done in any "scambled" method which means it is all visible to the phorming system. So I don't see why a Webwise system could not warn about the connection to a suspected phishing site then ignore your data stream from then on, if you continue to browse the site.
|
You're correct that some data needs to be sent "unscrambled" to set the connection up. However this isn't enough information to decide if the connection should be flagged as a phishing attempt. Webwise will only see the ip address, port and possibly the domain name of the site you are visiting. There are types of attack where this data will be for a completely legit site so will appear OK.
The URL is not sent until the encrypted connection has been set up.