On the command line, you can manage Exploit Prevention using the settings of the Behavior Detection (Behavior_Detection) predefined task.
You can configure Exploit Prevention by editing the settings of the Behavior Detection predefined task (see the table below).
Exploit Prevention settings
|
Setting |
Description |
Values |
|---|---|---|
|
|
Enable the Exploit Prevention component. |
|
|
|
The action to take when an exploit is detected. |
If set to If set to |
|
The [AEPExclusions.item_#] section contains exclusions from scanning for the Exploit Protection component. |
||
|
|
Enabling the exclusion from scanning of the Exploit Prevention protection component. |
|
|
|
Excludes an object from scans by the name of the threat detected in the object. Before specifying a value for this setting, make sure that the |
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. 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. |
|
|
Excludes an object in which a threat was detected by its hash. Before specifying a value for this setting, make sure that the |
|
|
|
The type of file hash that you want to use to exclude the file from scanning using the |
|
|
|
Excludes an object in which a threat was detected by its path. Before specifying a value for this setting, make sure that the |
|
|
|
Exclude objects containing the threats specified by the |
|
|
|
Exclude files with a detected threat by their hashes. The file hash is specified in the |
|
|
|
Exclude files with a detected threat by their paths. The path to the file is specified using the |
|