Operation Principles |
SpIDer Guard for NSS operates as a daemon (usually it is started by configuration daemon Dr.Web ConfigD on system startup). This monitor controls only the volumes which are specified in the settings (NssVolumesMountDir and ProtectedVolumes parameters). The monitor does not detect automatically, when a new NSS file system volume is mounted or unmounted. When a new or modified file is found on a volume, the monitor instructs Dr.Web Scanning Engine core component to scan the file. Another feature of this monitor is that it manages its own, separate, quarantine for threats detected on NSS volumes. The monitor operation scheme is shown in the picture below. Picture 38. Component operation scheme
If required, you can disable SpIDer Guard for NSS monitoring of certain files or directories. It can be useful when, for example, files in some directory are frequently modified, which results in constant repeated scanning of these files and, thus, can increase system load. If it is known with certainty that frequent modification of files in a directory is not caused by a virus but is due to operation of a trusted program, you can add the path to this directory or these files to the list of exclusions. In this case, the NSS volume monitor SpIDer Guard for NSS stops responding to modification of these objects. |