User-Defined Lists

You can create black or white lists for Dr.Web ICAPD. User-defined black lists, as well as content-specific black lists, block access to certain hosts. User-defined white lists can be of the following types:

•Trusted white list - WhiteHosts. All content from the specified hosts is passed without scanning for viruses.

•Permissive white list - WhiteDWS. Users can access the specified hosts regardless whether or not they match a category of a content-specific black list; however, access to the hosts is forbidden if they are specified in a user-defined black list.

Note the following features of user-defined lists:

•if a host is included in a trusted white list (of the WhiteHosts type), access to it is controlled as usual: the host is checked whether it is included in a content-specific list in compliance with the rules and then - whether it is included in a user-defined black list.

•if a host is included in a user-defined black list (of the BlackHosts), access to this host is blocked unconditionally; that is, you cannot create a redefining rule that allows access to such a resource. Moreover, user-defined black lists (of the BlackHosts type) take precedence over user-defined permissive white lists (of the WhiteDWS type), that is, if a host is added both to a user-defined white list and to a user-defined black list, access to this host is blocked.

To create and manage user-defined lists, you can either use the Web Interface of Dr.Web for Unix Internet gateways or edit the drweb-icapd.ini configuration file.

To create a user-defined black/white list

•Create a text file containing names or IP addresses of the hosts access to which must be blocked or allowed. Each host must be specified on a separate line.

•Configure required reaction of Dr.Web ICAPD on attempt to access these hosts:

oTo add hosts to a user-defined black list, specify the path to the text file, where the hosts are listed, as a value of the BlackHosts parameter in the Dr.Web ICAPD configuration file. You can specify several file paths, separated by commas.

Example:

BlackHosts = /home/user/host_list_1, /home/user/host_list_2

In the given example, all hosts included in the host_list_1 and host_list_2 files, are added to a user-defined black list; thus, access to them is blocked.

oTo add hosts to a permissive white list, specify the path to the text file, where the hosts are listed, as a value of the WhiteDWSFiles parameter in the Dr.Web ICAPD configuration file. However, if the same host is added in both permissive white list and user-defined black list, access to this host is blocked.

Example:

WhiteDWSFiles = /home/user/host_list_1, /home/user/host_list_3

In the given example, users can access only hosts included in the host_list_3 file, even though host_list_1 is specified in the WhiteDWSFiles parameter. However, if the same host is included in both permissive white list and content-specific black list, access to the host is allowed.

oTo add the specified hosts to a trusted white list, to transmit the content from the hosts without scanning, specify the path to the text file as a value of the WhiteHosts parameter in the Dr.Web ICAPD configuration file.

Example:

WhiteHosts = /home/user/host_list_1, /home/user/host_list_2, /home/user/host_list_3

In the given example, content received from the hosts listed in files host_list_1, host_list_2 and host_list_3 is not scanned for viruses.

Please note that the WhiteHosts parameter only disables anti-virus scanning of files received from the specified hosts, but does not manage access to them. Thus, in the example given above (according to the BlackHosts and WhiteDWSFiles values), access will be allowed only to the hosts specified in the host_list_3 list, and content received from these hosts will not be scanned for viruses.