03/26/2020 1,354 People found this article helpful 459,701 Views
This article describes the method to block Gmail.com and Facebook.com using CFS 3.0.
CFS examines the Server Extensions field in the Client Hello message and/or the CN in the Server Hello message to block HTTPS sites. HTTP sites are blocked by examining the Host field of the GET request. The following sections describe the methods involved in blocking both HTTP and HTTPS gmail.com and facebook.com.
Enabling HTTPS Content Filter Globally
Blocking using Forbidden Domains in CFS via Users and Zone Screens
Configuring Custom CFS Policies to inherit the Allow/Forbidden Custom List.
What has been entered under the Forbidden Domains is automatically applicable to the Default policy. To enforce the same on custom CFS policies their Custom List Settings needs to be manually set to Global.
Blocking using Allow/Forbidden Custom List in CFS via App Rules
Match Objects
To create a custom list of allowed or forbidden domains, select CFS Allow/Forbidden List under Match Object Type. You could also load the allow/block list from a file containing the name of the domains. Each entry in the file should be separated by a line. The maximum size of the file is 8192 bytes.
Unlike CFS via Users and Zones, Custom List Objects (as above) cannot be used individually in an App Rule. It can only be used with a CFS Category List Object (see below):
App Rules
Log Messages
When SonicWall CFS blocks HTTPS websites users will not see a blocked page only a connection-reset page.
However the following messages will appear in the logs: