The table describes all available values and default values of all the settings that you can specify for the File Threat Protection task.
|
|
|
|
Setting
|
Description
|
Values
|
ScanArchived
|
Enables scanning of archives (including SFX self-extracting archives).
The application scans the following archives: .zip; .7z*; .7-z; .rar; .iso; .cab; .jar; .bz; .bz2; .tbz; .tbz2; .gz; .tgz; .arj. The list of supported archive formats depends on the application databases being used.
We do not recommend enabling this setting because scanning archives impacts performance due to the fact that access to the archive file is blocked while the file is being unpacked to a temporary directory and scanned.
|
Yes —Scan archives. If the FirstAction=Recommended value is specified, then, depending on the archive type, the application deletes either the infected object or the entire archive that contains the threat.
No (default value) — Do not scan archives.
|
ScanSfxArchived
|
Enables scanning of self-extracting archives only (archives that contain an executable extraction module).
|
Yes — Scan self-extracting archives.
No (default value) — Do not scan self-extracting archives.
|
ScanMailBases
|
Enables scanning email databases of Microsoft Outlook®, Outlook Express, The Bat, and other mail clients.
|
Yes — Scan files of email databases.
No (default value) — Do not scan files of email databases.
|
ScanPlainMail
|
Enables scanning of plain text email messages.
|
Yes — Scan plain text email messages.
No (default value) — Do not scan plain text email messages.
|
SkipPlainTextFiles
|
Temporary exclusion of files in text format from scans.
If the value of this setting is SkipPlainTextFiles=Yes , the application does not scan text files if they are reused by the same process for 10 minutes after the most recent scan. This setting makes it possible to optimize scans of application logs.
|
Yes – Do not scan text files if they are reused by the same process for 10 minutes after the most recent scan.
No (default value) – scan files in plain text format.
|
SizeLimit
|
Maximum size of an object to be scanned (in megabytes). If the object to be scanned is larger than the specified value, the application skips this object.
|
0 – 999999
0 — The application scans objects of any size.
Default value: 0.
|
TimeLimit
|
Maximum object scan duration (in seconds).
The application stops scanning the object if it takes longer than the time specified by this setting.
|
0 – 9999
0 — The object scan time is unlimited.
Default value: 60.
|
FirstAction
|
Selection of the first action to be performed by the application on the infected objects.
|
Disinfect — The application tries to disinfect an object and save a copy of it to Backup. If disinfection fails (for example, if the type of object or the type of threat in the object cannot be disinfected), then the application leaves the object unchanged. If the first action is Disinfect , it is recommended to specify a second action using the SecondAction setting.
Remove — The application removes the infected object after creating a backup copy of it.
Recommended (perform recommended action) — The application automatically selects and performs an action on the object based on information about the threat detected in the object. For example, Kaspersky Endpoint Security immediately removes Trojans since they do not incorporate themselves into other files and therefore they do not need to be disinfected.
Block – The application blocks access to an infected object. Information about the infected object is logged.
Default value: Recommended .
|
SecondAction
|
Selection of the second action to be performed by the application on the infected objects. The application performs the second action if the first action fails.
|
The possible values of the SecondAction setting are the same as those of the FirstAction setting.
If Block or Remove is selected as the first action, the second action does not need to be specified. It is recommended to specify two actions in all other cases. If you have not specified a second action, the application applies Block as the second action.
Default value: Block .
|
UseExcludeMasks
|
Enables scan exclusions for the objects specified by the ExcludeMasks.item_# setting.
|
Yes — Exclude objects specified by the ExcludeMasks.item_# setting from scans.
No (default value) — Do not exclude objects specified by the ExcludeMasks.item_# setting from scans.
|
ExcludeMasks.item_#
|
Excludes objects from being scanned by name or mask.
You can use this setting to exclude an individual file from the specified scan scope by name or exclude several files at once using masks in the shell format.
|
The default value is not defined.
Example:
UseExcludeMasks=Yes
ExcludeMasks.item_0000=eicar1.*
ExcludeMasks.item_0001=eicar2.*
|
|
UseExcludeThreats
|
Enables scan exclusions for objects containing the threats specified by the ExcludeThreats.item_# setting.
|
Yes — Exclude objects containing the threats specified by the ExcludeThreats.item_# setting from scans.
No (default value) — Do not exclude objects containing the threats specified by the ExcludeThreats.item_# setting from scans.
|
ExcludeThreats.item_#
|
Excludes objects from scans by the name of the threats detected in them. Before specifying a value for this setting, make sure that the UseExcludeThreats setting is enabled.
In order to exclude an object from scans, specify the full name of the threat detected in this object – the string containing the application's decision that the object is infected.
For example, you may be using a utility to collect information about your network. To keep the application from blocking it, add the full name of the threat contained in it to the list of threats excluded from scans.
You can find the full name of the threat detected in an object in the application log or on the website https://threats.kaspersky.com.
|
The setting value is case-sensitive.
The default value is not defined.
Example:
UseExcludeThreats=Yes
ExcludeThreats.item_0000=EICAR-Test-*
ExcludeThreats.item_0001=?rojan.Linux
|
|
ReportCleanObjects
|
Enables logging of information about scanned objects that the application reports as not being infected.
You can enable this setting, for example, to make sure that a particular object was scanned by the application.
|
Yes — Log information about non-infected objects.
No (default value) — Do not log information about non-infected objects.
|
ReportPackedObjects
|
Enables logging of information about scanned objects that are part of compound objects.
You can enable this setting, for example, to make sure that an object within an archive has been scanned by the application.
|
Yes — Log information about scanned objects within archives.
No (default value) — Do not log information about scanned objects within archives.
|
ReportUnprocessedObjects
|
Enables logging of information about objects that have not been processed for some reason.
|
Yes — Log information about unprocessed objects.
No (default value) — Do not log information about unprocessed objects.
|
UseAnalyzer
|
Enables heuristic analysis.
Heuristic analysis helps the application to detect threats even before they become known to virus analysts.
|
Yes (default value) — Enable Heuristic Analyzer.
No — Disable Heuristic Analyzer.
|
HeuristicLevel
|
Specifies the heuristic analysis level.
The heuristic analysis level sets the balance between the thoroughness of searches for threats, the load on the operating system's resources, and the scan duration. The higher the heuristic analysis level, the more resources and time are required for scanning.
|
Light — The least thorough scan with minimum load on the system.
Medium — A medium heuristic analysis level with a balanced load on the system.
Deep — The most thorough scan with maximum load on the system.
Recommended (default value) — The recommended value.
|
UseIChecker
|
Enables usage of the iChecker technology.
|
Yes (default value) — Enable use of the iChecker technology.
No — Disable use of the iChecker technology.
|
ScanByAccessType
|
File Threat Protection task operation mode. The ScanByAccessType setting applies only to the File Threat Protection task.
|
SmartCheck (default value) — Scan a file on attempts to open it, and scan it again on attempts to close it if the file has been modified. If a process accesses an object multiple times in the course of its operation and modifies it, the application scans the object again only when the process closes it for the last time.
OpenAndModify — Scan a file on attempts to open it, and scan it again on attempts to close it if the file has been modified.
Open — Scan a file on attempts to open it for reading, execution, or modification.
|
The [ScanScope.item_#] section contains the following settings:
|
AreaDesc
|
Description of the scan scope, which contains additional information about the scan scope.
The maximum length of the string specified using this setting is 4096 characters.
|
Default value: All objects .
Example:
AreaDesc=" Scanning of email databases "
|
|
UseScanArea
|
Enables scans of the specified scope. To run the task, enable scans of at least one scope.
|
Yes (default value) — Scan the specified scope.
No — Do not scan the specified scope.
|
AreaMask.item_#
|
Scan scope limitation. With this scan scope, the application only scans files that are specified using masks in the shell format.
If this setting is not specified, the application scans all the objects in the scan scope. You can specify several values for this setting.
|
The default value is * (scan all objects).
Example:
AreaMask_item_< item number >=*doc
|
|
Path
|
Path to the directory with objects to be scanned.
|
< path to local directory > — Scan objects in the specified directory. You can use masks and tags to specify the path.
You can use special tags to specify a container or image:
[container-id:< identifier >]/< path to local directory > [container-name:< name >]/< path to local directory > [image-id:< identifier >]/< path to local directory > [image-name:< name >]/< path to local directory >
You can also use unique combinations of the [container-id:< identifier >], [container-name:< name >], [image-id:< identifier >] and [image-name:< name >]/< path to local directory > tags.
Any combination of 1 to 4 unique tags within one area is allowed. The order they are listed in is not important.
For example:
[container-name:< name >][image-name:< name >]/< path to local directory > [container-id:< identifier >][image-name:< name >]/< path to local directory > [image-name:< name >][image-id:< identifier >]/< path to local directory > [container-name:< name >][container-id:< identifier >][image-name:< name >]/< path to local directory > [container-name:< name >][image-id:< identifier >][container-id:< identifier >][image-name:< name >]/< path to local directory >
You can use masks (? and * characters) in names and identifiers.
You can use the * (asterisk) character to create a file or directory name mask.
You can indicate a single * character to represent any set of characters (including an empty set) preceding the / character in the file or directory name. For example, /dir/*/file or /dir/*/*/file .
You can indicate two consecutive * characters to represent any set of characters (including an empty set and the / character) in the file or directory name. For example, /dir/**/file*/ or /dir/file**/ .
The ** mask can be used only once in a directory name. For example, /dir/**/**/file is an incorrect mask.
You can use a single ? character to represent any one character in the file or directory name.
Shared:NFS — Scan the device file system resources that are accessible via the NFS protocol.
Shared:SMB – Scan the device file system resources that are accessible via the Samba protocol.
Mounted:NFS – Scan the remote directories mounted on a device using the NFS protocol.
Mounted:SMB – Scan the remote directories mounted on a device using the Samba protocol.
AllRemoteMounted – Scan all remote directories mounted on the device using the Samba and NFS protocols.
AllShared – Scan all the device file system resources that are accessible via the Samba and NFS protocols.
< file system type > — Scan all the resources of the specified device file system.
|
The [ExcludedFromScanScope.item_#] section contains the following settings:
|
AreaDesc
|
Description of the scan exclusion scope, which contains additional information about the exclusion scope.
|
The default value is not defined.
|
UseScanArea
|
Excludes the specified scope from scans.
|
Yes (default value) — Exclude the specified scope.
No — Do not exclude the specified scope.
|
AreaMask.item_#
|
Limitation of scan exclusion scope. In the exclusion scope, the application excludes from scans only files that are specified using masks in the shell format.
If this setting is not specified, the application does not scan any of the objects within the exclusion scope. You can specify several values for this setting.
|
Default value: * (exclude all objects from scan)
|
Path
|
Path to the directory with objects to be excluded.
|
< path to local directory > — Exclude objects in the specified directory (including subdirectories) from scans. You can use masks and tags to specify the path.
You can use special tags to specify a container or image:
[container-id:< identifier >]/< path to local directory > [container-name:< name >]/< path to local directory > [image-id:< identifier >]/< path to local directory > [image-name:< name >]/< path to local directory >
You can also use unique combinations of the [container-id:< identifier >], [container-name:< name >], [image-id:< identifier >] and [image-name:< name >]/< path to local directory > tags.
Any combination of 1 to 4 unique tags within one area is allowed. The order they are listed in is not important.
For example:
[container-name:< name >][image-name:< name >]/< path to local directory > [container-id:< identifier >][image-name:< name >]/< path to local directory > [image-name:< name >][image-id:< identifier >]/< path to local directory > [container-name:< name >][container-id:< identifier >][image-name:< name >]/< path to local directory > [container-name:< name >][image-id:< identifier >][container-id:< identifier >][image-name:< name >]/< path to local directory >
You can use masks (? and * characters) in names and identifiers.
You can use the * (asterisk) character to create a file or directory name mask.
You can indicate a single * character to represent any set of characters (including an empty set) preceding the / character in the file or directory name. For example, /dir/*/file or /dir/*/*/file .
You can indicate two consecutive * characters to represent any set of characters (including an empty set and the / character) in the file or directory name. For example, /dir/**/file*/ or /dir/file**/ .
The ** mask can be used only once in a directory name. For example, /dir/**/**/file is an incorrect mask.
You can use a single ? character to represent any one character in the file or directory name.
Mounted:NFS – Exclude the remote directories mounted on a device using the NFS protocol from scan.
Mounted:SMB – Exclude the remote directories mounted on a device using the Samba protocol from scan.
AllRemoteMounted – Exclude all remote directories mounted on the device using the Samba and NFS protocols from scan.
<file system type > — Exclude all the resources of the specified device file system from scans.
|
The [ExcludedForProgram.item_#] section contains the following settings:
|
ProgramPath
|
Path to excluded process.
|
< full path to process > – Do not scan the process in the indicated local directory.
|
ApplyToDescendants
|
Exclude child processes of the excluded process specified by the ProgramPath setting from scans.
|
Yes – exclude the specified process and all its child processes from scans.
No (default value) – exclude only the specified process from scans, do not exclude its child processes from scans.
|
AreaDesc
|
Description of the process exclusion scope.
|
Default value: All objects .
|
UseExcludedForProgram
|
Excludes the specified scope from scans.
|
Yes (default value) — Exclude the specified scope.
No — Do not exclude the specified scope.
|
AreaMask.item_#
|
Limitation of the process exclusion scope. In the process exclusion scope, the application excludes from scans only the files that are specified using masks in the shell format.
If this setting is not specified, the application excludes from scans all the objects within the process exclusion scope. You can specify several values for this setting.
|
Default value: * (exclude all objects from scan)
|
Path
|
Path to a directory with files that are modified by the process.
|
< path to local directory > — Exclude objects in the specified directory from scan. You can use masks to specify the path.
You can use the * (asterisk) character to create a file or directory name mask.
You can indicate a single * character to represent any set of characters (including an empty set) preceding the / character in the file or directory name. For example, /dir/*/file or /dir/*/*/file .
You can indicate two consecutive * characters to represent any set of characters (including an empty set and the / character) in the file or directory name. For example, /dir/**/file*/ or /dir/file**/ .
The ** mask can be used only once in a directory name. For example, /dir/**/**/file is an incorrect mask.
You can use a single ? character to represent any one character in the file or directory name.
Shared:NFS — Exclude device file system resources that are accessible via the NFS protocol from scans.
Shared:SMB — Exclude device file system resources that are accessible via the Samba protocol from scans.
Mounted:NFS – Exclude the remote directories mounted on a device using the NFS protocol from scan.
Mounted:SMB – Exclude the remote directories mounted on a device using the Samba protocol from scan.
AllRemoteMounted – Exclude all remote directories mounted on the device using the Samba and NFS protocols from scan.
AllShared – Exclude all device file system resources that are accessible using the Samba and NFS protocols from scan.
< file system type > — Exclude all the resources of the specified device file system from scans.
|