Knowledge Base

Tips on configuring Custom CFS Allow/Forbidden Lists


This article covers a few tips and tricks to get the most out of using a custom CFS allowed and/or forbidden list.


Custom List of the SonicWall CFS allows an administrator to enter specific domain names to be allowed or blocked. Custom List also allows you to enter keywords which are useful to block access to any web site whose URL contains any listed keyword. Keyword Blocking will also prevent the uploading of any form requests that contain a listed keyword, such as a web site search.

Listed here are some tips when configuring the Custom List
tab of the Content Filtering window.
  • SonicWall CFS matches the suffix of a domain with what is entered under Allowed or Forbidden Domains. For example, if google.com is entered under Forbidden Domains, then access to mail.google.com or docs.google.com is blocked. Conversely, entering mail.google.com in the Custom List will NOT match google.com.
  • Keeping with the above criteria, it is NOT required to enter wildcard characters, such as *, before a domain. For example, *.google.com is NOT required to be entered to block sites ending with google.com. Entering google.com will suffice.
  • Adding Http or Https before a domain name is NOT required and may not result in a match.
  • Check for redundancy. For example, if you already have an entry to block access to "yahoo.com", you do not need a second entry to block access to mail.yahoo.com.
  • SonicWall CFS inspects packets which have HTTP headers and matches what is in the Host field of such a HTTP header. Generally, HTTP Host field contains the domain name ending with a top-level domain (TLD). For example, example.com, example.org etc. In cases where the HTTP server is being accessed on a non-standard port - standard being TCP port 80 - the HTTP Host field will have the port number along with the domain name. For example, website.com:8080. As earlier mentioned, the SonicWall CFS matches content by suffix due to which entering website.com in the Allowed/Forbidden Domains will NOT match with the HTTP Host field of website.com:8080. In such cases, website.com:8080 must be entered in the Allowed/Forbidden Domains.
  • Keyword Blocking functions slightly different from Allowed/Forbidden Domains in that it inspects both the HTTP Host field as well as the HTTP URI field of the HTTP header. For example, the keyword "resource" will block access to http://en.wikipedia.org/wiki/ResourceKeyword Blocking can be used to block specific contents within a website (HTTP). A more practical example would be to block composing mail from within Webmail by adding "compose" in Keyword Blocking. The maximum characters allowed within Keyword Blocking is 15. Another limitation would be that HTTPS Content Filtering is not applicable to Keyword Blocking. Therefore, the methods listed above are applicable to HTTP traffic only.
  • Speaking of blocking HTTPS content, SonicWall CFS endeavours to block HTTPS websites using HTTPS Content Filtering. This feature of CFS inspects what is visible in the SSL handshake process. Specifically, the Server Name extension in the Client Hello or Server Hello messages and the certificate name in the Certificate message during the handshake process. HTTPS Content Filtering was introduced in SonicOS Enhanced
  • HTTPS Content Filtering may block HTTPS content (inspecting only what is visible in the handshake process) but sometimes it doesn't work because most of the website details are encrypted. To achieve this goal, you may need the DPI-SSL: https://www.sonicwall.com/en-us/support/knowledge-base/170505782716496