User Specific Configuration; Handle Object Policy - ESET NOD32 ANTIVIRUS - FOR LINUX-BSD FILE SERVER Installation Manual

5.1. User Specific Configuration

User Specific Configuration mechanism is implemented in the product in order to provide user with enhanced
configuration functionality. It allows to define NOD32 anti-virus scanner parameters selectively for user accessing file
system objects.
Please note that the detailed description of this functionality can be found in nod32.cfg(5) manual page and
manual pages referenced there. Thus in this section we will only provide short example of user specific configuration
definition.
Let's say we use nod32dac module for the scanning purpose. This module is subjected to the configuration section
[dac] found within main NOD32 configuration file. The example of the section can be as follows.
[dac]
agent_enabled = yes
event_mask = 5
ctl_incl = "/home"
action_on_processed = accept
In order to provide individual parameters setting one has to define 'user_config' parameter with the path to the
special configuration file where the individual setting will be stored. In the next example we create reference to the
special configuration file 'nod32dac_spec.cfg' located within default configuration file directory.
[dac]
agent_enabled = yes
event_mask = 5
ctl_incl = "/home"
action_on_processed = accept
user_config = "nod32smtp_spec.cfg"
Note that the 'user_config' parameter accepts also absolute path to the specific configuration file.
Once special configuration file referenced from within [dac] section we have to create this file and provide the file
with an appropriate individual settings.
In the next example we create individual parameter setting of parameter 'action_on_processed' for user
'username' .
[username]
action_on_processed = reject
Note that the section header name of the special section contains identification of the user for which we have created
the individual setting. The section body then contains individual parameters specified for this identification. Thus with
this special configuration all users attempting to access file-system will be processed, i.e. all file system objects accessed
by the users will be scanned for infiltrations, with exception to the user 'username' that will be rejected, i.e. the access
of the file system will be blocked for this user.

5.2. Handle Object Policy

The Handle Object Policy (see figure 5-1) is a mechanism that provides handling of the scanned objects depending
on their scanning status. The mechanism is based on so-called action configuration options ('action_on_processed' ,
'action_on_infected' , 'action_on_uncleanable' , 'action_on_notscanned') combined with Anti-Virus
0
enabling
NOD32 for Linux/BSD File Server