User manual

Reference: Configuration options
43
All processes for executable files located under the path C:\Program Files1 are
excluded from the Guard scan.
Examples for files to be excluded:
– *.mdb
All files with the extension 'mdb’ are excluded from the Guard scan
– *.xls*
All files with a file extension beginning 'xls’ are excluded from the Guard scan, e.g.
files with the extensions .xls and .xlsx.
– C:\Directory\*.log
All log files with the extension 'log’, located under the path C:\Directory, are
excluded from the Guard scan.
– \\Computer name\Shared1\
All files are excluded from the Guard scan accessed via a connection '\\Computer
name1\Shared1'. This is generally a connected network drive which accesses another
computer with a shared folder via the computer name ‘Computer name1’ and the
shared name 'Shared1’.
– \\1.0.0.0\Shared1\*.mdb
All files with the extension ‘mdb’ are excluded from the Guard scan accessed via a
connection '\\1.0.0.0\Shared1'. This is generally a connected network drive which
accesses another computer with a shared folder via the IP address '1.0.0.0' and the
shared name 'Shared1’.
10.2.4 Products
Products to be skipped by Guard
In this display box, you can select products which are excluded by the Guard scan. All
applications, services or databases of the selected product are excluded from the
monitoring by Guard.
10.2.5 Heuristics
This configuration section contains the settings for the heuristic of the scan engine.
AntiVir products contain very powerful heuristics that can proactively uncover unknown
malware, i.e. before a special virus signature to combat the damaging element has been
created and before a virus guard update has been sent. Virus detection involves an
extensive analysis and investigation of the affected codes for functions typical of
malware. If the code being scanned exhibits these characteristic features, it is reported as
being suspicious. This does not necessarily mean that the code is in fact malware. False
positives do sometimes occur. The decision on how to handle affected code is to be made
by the user, e.g. based on his or her knowledge of whether the source of the code is
trustworthy or not.