DESCRIPTION: CFS: Does CFS support HTTPS site blocking?
Does CFS support HTTPS site blocking?
Until SonicOS Enhanced 184.108.40.206, HTTPS Filtering is IP-based. Therefore, IP addresses must be used rather than domain names in the Allowed or Forbidden lists. You can use the nslookup command in a DOS cmd window to convert a domain name to its IP address(es). There may be more than one IP address associated with a domain, and if so, all must be added to the Allowed or Forbidden list.
With the release SonicOS Enhanced 220.127.116.11 HTTPS sites were blocked using HTTPS Content Filtering which is both IP as well as hostname based. SonicWall CFS obtains hostnames (example, google.com) using the following methods:
Examine SSL Client Hello messages and, if it supports SSL server name extension, it will have hostname included in the SSL Client Hello. This hostname is used to get rating information.
Another method is to examine Server Hello messages to get certificate Common Names (CN) from the certificate and use the same to get rating information.
Note: Unlike HTTP content filtering, HTTPS sites are silently blocked without displaying a CFS block page.