Support for wildcard characters in the whitelist/blacklist feature of Web Reputation Service

Support
Solution ID Last Updated
1060771 Date : 2013/01/16 Time:7:20 AM , (PST)


Product/Version Platform
Deep Security - 7.5, 8.0;OfficeScan - 10.0, OfficeScan - 10.5, OfficeScan - 10.6;Worry-Free Business Security Standard/Advanced - 6.0, Worry-Free Business Security Standard/Advanced - 7.0, Worry-Free Business Security Standard/Advanced - 8.0;
VMware - ESX 4.1, ESX 5.0, ESXi 4.1, ESXi 5.0, vCenter 5.0, Windows - 2003 Enterprise, Windows - 2003 Enterprise 64-bit, Windows - 2003 Small Business Server, Windows - 2003 Small Business Server R2, Windows - 2003 Standard, Windows - 2003 Standard 64-bit, Windows - 2008 Enterprise, Windows - 2008 Enterprise 64-bit, Windows - 2008 Essential Business Server, Windows - 2008 Server R2, Windows - 2008 Small Business Server, Windows - 2008 Standard, Windows - 2008 Standard 64-bit, Windows - 7 64-bit, Windows - Vista 32-bit, Windows - Vista 64-bit, Windows - XP Home, Windows - XP Professional, Windows - XP Professional 64-bit

Problem Description

Find out if the whitelist and blacklist of Deep Security, OfficeScan and Worry-Free Business Security Standard/Advanced recognize wildcard characters when used in IP addresses.

Solution

Yes, wildcards are supported and may be used when adding IP addresses to the whitelist or blacklist.
For example, the entry "http://61.220*" will give the following result:
<TmpeURLf> Scan URL: "http://61.220.XXX.XX/" - UrlFilterEngine.cpp(228)
<TmpeURLf> Whitelist matched - UrlFilterEngine.cpp(277)
Rate this Solution
Did this article help you?

Please provide your comments to help us improve this solution.

 
  *This form is an automated system. General questions, technical, sales and product-related issues submitted through this form will not be answered.
 
 

Connect with us on