Kaspersky Endpoint Security contains a multitude of various binary modules in the form of dynamic-link libraries, executable files, configuration files, and interface files. A hacker can replace one or more application executable modules or files with other files containing malicious code. To prevent the replacement of modules and files, Kaspersky Endpoint Security can check the integrity of application components.
The application checks modules and files for the presence of unauthorized changes or corruption. If an application module or file has an incorrect checksum, it is considered to be corrupted.
The application checks the integrity of the manifest file containing a list of application files whose integrity is critical for correct operation of the application component.
The integrity of application components is checked by using the integrity_check_tool located in the directory /opt/kaspersky/kesl/bin. The same directory contains the integrity_check.xml manifest file, protected by the cryptographic signature of Kaspersky.
Root user account privileges are required to run the integrity check tool.
The integrity check can be performed using the tool that is installed together with the application or using the tool on a certified CD.
It is recommended to run the integrity check tool from the certified CD to ensure the integrity of the tool. When running the tool from CD, the full path to manifest file in the application directory must be provided.
To check the integrity of application components, run the following command:
integrity_check_tool -v[|--verify] -m[|--manifest] <file path>
<file path> is the path to the manifest file. By default, the tool uses the integrity_check.xml file located in the directory /opt/kaspersky/kesl/bin.
You can run the integrity check tool with the following optional settings:
-h, --help—display Help for tool settings.
-V, --verbose—expanded output of performed actions and results. If you do not specify this setting, only errors, objects that did not pass the check, and summary scan statistics will be provided.
-L, -- log-file <file>, where
<file>is the name of the file used for writing events that occur during a scan. By default, events are sent to the standard stream stdout.
-l, -- log-level <0-1000>, where
<0-1000>is the level of detail of event output. The default level of detail is
The result of checking each manifest file is displayed next to the name of the manifest file in the following format:
SUCCEEDED—integrity of the files is confirmed (return code
FAILED—integrity of the files is not confirmed (return code is not