Contents
System Integrity Check
When the System Integrity Check task is running, a change in each object is found by comparing the current state of the monitored object with its original state. The following comparison criteria can be used:
- File hash
- File change time
- File size
The initial state of monitored objects is recorded as a baseline. The baseline contains paths to monitored objects and their metadata.
A baseline may also contain personal data.
A system baseline is created when a System Integrity Check task runs on the device for the first time. If you have created multiple System Integrity Check tasks, a separate baseline is created for each. The task is only executed if the baseline contains information about objects that belong to the monitoring scope defined for the task. If the baseline does not match the monitoring scope, Kaspersky Embedded Systems Security generates a system integrity violation event.
A baseline is rebuilt when task settings change, for example, if a new monitoring scope is added.
The application creates a baseline storage on the protected device. By default, the storage for baselines is located in /var/opt/kaspersky/kess/private/fim.db. Root privileges are required to access a database that contains baselines.
You can delete a baseline by deleting the appropriate System Integrity Check task.
You can run a system integrity check on demand and configure the scan settings:
- Enable or disable baseline rebuild every time a system integrity check task finishes.
- Select criteria for comparing the current state of the monitored file with the original state: use the file hash and change time, or only the file size.
- Configure monitoring scopes for checking system integrity.
- Configure exclusion scopes from the system integrity check. You can specify paths to excluded files and directories, and exclude individual objects by name mask.
Configuring System Integrity Check in the Web Console
You can run a system integrity check in the Web Console with the help of the System Integrity Check task.
You can create and run user system integrity check tasks. You can configure the scan settings by editing the settings of the tasks.
System Integrity Check task settings
Setting |
Description |
---|---|
Rebuild baseline on each task start |
This check box enables or disables the reestablishment of a system baseline upon every start of the System Integrity Check task. This check box is cleared by default. |
Check SHA256 hash |
This check box enables or disables the use of the file hash as a criterion when comparing the current state of the file with its original state. If this check box is cleared, the application compares only the file size (if the file size has not changed, then the modification time is not considered a critical parameter). This check box is cleared by default. |
Track directories in monitoring scopes |
This check box enables or disables directory monitoring while system integrity check is running. This check box is cleared by default. |
Track the last time a file was accessed |
This check box enables or disables tracking the file access time while the System Integrity monitoring runs. This check box is cleared by default. |
Monitoring scopes |
The table that contains the monitoring scopes scanned by the task. By default, the table contains the Kaspersky internal objects (/opt/kaspersky/kess/) monitoring scope. You can add, configure, delete, move up, or move down monitoring scopes in the table. |
Add scan scope window
In this window, you can add or configure the monitoring scope for the System Integrity Check task.
Monitoring scope settings
Setting |
Description |
---|---|
Scope name |
Field for entering the monitoring scope name. This name will be displayed in the table in the Scan settings section. The entry field must not be blank. |
Use this scope |
This check box enables or disables scans of this scope by the application. If this check box is selected, the application controls this monitoring scope during the application's operation. If this check box is cleared, the application does not control this monitoring scope during the operation. You can later include this scope in the component settings by selecting the check box. The check box is selected by default. |
File system, access protocol, and path |
Entry field for the path to the local directory that you want to include in the monitoring scope. You can use masks to specify the path. The field must not be blank. The / path is specified by default – the application scans all directories of the local file system. |
Masks |
The list contains name masks for the objects that the application scans. By default the list contains the * mask (all objects). |
Exclusion scopes section
In the Exclusion scopes section for the System Integrity Check task, you can also configure exclusion scopes for the scan and exclusions by mask.
Page topExclusion scopes window
The table contains monitoring exclusion scopes for the System Integrity Check component. The application does not scan files and directories located at the paths specified in the table. By default, the table is empty.
Monitoring exclusion scope settings
Setting |
Description |
---|---|
Exclusion scope name |
Exclusion scope name. |
Path |
Path to the directory excluded from monitoring. |
Status |
Indicates whether the application excludes this scope from monitoring during the task operation. |
You can add, edit, and delete items in the table.
Page topAdd exclusion scope window
In this window, you can add and configure the monitoring exclusion scope for the System Integrity Check task.
Monitoring exclusion scope settings
Setting |
Description |
---|---|
Exclusion scope name |
Field for entering the exclusion scope name. This name will be displayed in the table in the Exclusion scopes window. The entry field must not be blank. |
Use this scope |
The check box enables or disables the exclusion of the scope from monitoring when the application is running. If this check box is selected, the application excludes this scope from monitoring during the task operation. If this check box is cleared, the application monitors this scope during the task operation. You can later exclude this scope from monitoring by selecting the check box. The check box is selected by default. |
File system, access protocol, and path |
Entry field for the path to the local directory that you want to add to the exclusion scope. You can use masks to specify the path. The field must not be blank. The / path is specified by default. The application excludes all directories of the local file system from scan. |
Masks |
The list contains name masks of the objects that the application excludes from the monitoring. By default the list contains the * mask (all objects). |
Exclusions by mask window
You can configure the exclusion of objects from monitoring based on name masks. The application does not scan the files with the names containing the specified masks. By default, the list of masks is empty.
You can add, edit, or delete masks.
Page topConfiguring System Integrity Check in the Administration Console
You can perform a system integrity check in the Administration Console, with the help of the System Integrity Check task.
You can create and run user system integrity check tasks. You can configure the scan settings by editing the settings of the tasks.
In the Settings section of the properties of the System Integrity Check task, you can edit the settings listed in the table below.
System Integrity Check task settings
Setting |
Description |
---|---|
Rebuild baseline on each task start |
This check box enables or disables the rebuilding of the system baseline every time the System Integrity Check task is started. This check box is cleared by default. |
Check SHA256 hash |
This check box enables or disables the use of the file hash as a criterion when comparing the current state of the file with its original state. If this check box is cleared, the application compares only the file size (if the file size has not changed, then the modification time is not considered a critical parameter). This check box is cleared by default. |
Track directories in monitoring scopes |
This check box enables or disables scanning of directories within the specified monitoring scopes during a system integrity check. This check box is cleared by default. |
Track the last time a file was accessed |
This check box enables or disables tracking the file access time while the System Integrity monitoring runs. This check box is cleared by default. |
Monitoring scopes |
The group of settings contains the Configure button. Clicking this button opens the Scan scopes window. |
Under Exclusion scopes in the properties of the System Integrity Check, you can define monitoring exclusions and exclusions by mask.
Page topScan scopes window
The table contains monitoring scopes for the System Integrity Check task. The application monitors files and directories located in the paths specified in the table. By default, the table contains one monitoring scope, Kaspersky internal objects (/opt/kaspersky/kess/).
Monitoring scope settings
Setting |
Description |
---|---|
Scope name |
Monitoring scope name. |
Path |
Path to the directory that the application protects. |
Status |
The status indicates whether the application scans this scope. |
You can add, edit, delete, move up, and move down items in the table.
Kaspersky Embedded Systems Security scans objects in the specified scopes, in the order they appear in the list of scopes. If necessary, place the subdirectory higher in the list than its parent directory, to configure security settings for a subdirectory that are different from the security settings of the parent directory.
Page top<New scan scope> window
In this window, you can add and configure monitoring scopes for the System Integrity Check task.
Monitoring scope settings
Setting |
Description |
---|---|
Scan scope name |
Field for entering the monitoring scope name. This name will be displayed in the table in the Scan scopes window. The entry field must not be blank. |
Use this scope |
This check box enables or disables scans of this scope by the application. If this check box is selected, the application controls this monitoring scope during the application's operation. If this check box is cleared, the application does not control this monitoring scope during the operation. You can later include this scope in the component settings by selecting the check box. The check box is selected by default. |
File system, access protocol, and path |
Entry field for the path to the local directory that you want to include in the monitoring scope. You can use masks to specify the path. The field must not be blank. The default path is /opt/kaspersky/kess. |
Masks |
The list contains name masks for the objects that the application scans. By default the list contains the * mask (all objects). |
Exclusion scopes section
Settings of scan exclusions
Group of settings |
Description |
---|---|
Monitoring exclusions |
This group of settings contains the Configure button. Clicking this button opens the Exclusion scopes window. In this window, you can define the list of scopes to be excluded from monitoring. |
Exclusions by mask |
This group of settings contains the Configure button, which opens the Exclusions by mask window. In this window, you can configure the exclusion of objects from monitoring by name mask. |
Exclusion scopes window
The table contains scan exclusion scopes for the System Integrity Check component. The application does not scan files and directories located at the paths specified in the table. By default, the table is empty.
Scan exclusion scope settings for the System Integrity Check task
Setting |
Description |
---|---|
Exclusion scope name |
Exclusion scope name. |
Path |
Path to the directory excluded from scan. |
Status |
Indicates whether the application excludes this scope from monitoring during the component operation. |
You can add, edit, and delete items in the table.
Page top<New exclusion scope> window
In this window, you can add and configure the monitoring exclusion scope for the System Integrity Check task.
Monitoring exclusion scope settings
Setting |
Description |
---|---|
Exclusion scope name |
Field for entering the exclusion scope name. This name will be displayed in the table in the Exclusion scopes window. The entry field must not be blank. |
Use this scope |
The check box enables or disables the exclusion of the scope from monitoring when the application is running. If this check box is selected, the application excludes this scope from monitoring during the task operation. If this check box is cleared, the application monitors this scope during the task operation. You can later exclude this scope from monitoring by selecting the check box. The check box is selected by default. |
File system, access protocol, and path |
Entry field for the path to the local directory that you want to add to the exclusion scope. You can use masks to specify the path. The field must not be blank. The / path is specified by default. The application excludes all directories of the local file system from scan. |
Masks |
The list contains name masks of the objects that the application excludes from the monitoring. By default the list contains the * mask (all objects). |
Exclusions by mask window
You can configure the exclusion of objects from monitoring based on name masks. The application does not scan the files with the names containing the specified masks. By default, the list of masks is empty.
You can add, edit, or delete masks.
Page topConfiguring System Integrity Check in the command line
You can run a system integrity check on a device in the command line by using user System Integrity Check tasks (ODFIM tasks).
You can manually start, stop, pause, or resume user tasks and configure the task schedule. You can configure system integrity checking by editing the settings of these tasks.
System Integrity Check task settings
Setting |
Description |
Values |
---|---|---|
|
Enables baseline to rebuild after the System Integrity Check task finishes. |
|
|
Use the file hash (SHA256) as a criterion when comparing the current state of the monitored file with its original state. |
|
|
Enables directory monitoring. |
|
|
Enables tracking last file access time. In the Linux operating systems it is the |
|
|
Enables monitoring scope exclusions for objects specified by the This setting only applies if a value is specified for the |
|
|
Excludes objects from monitoring by names or masks. 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. Before specifying a value for this setting, make sure that the You can specify several masks. Each mask must be specified on a new line with a new index. |
The default value is not defined. |
The [ScanScope.item_#] section contains the monitoring scopes of the System Integrity Check. At least one monitoring scope must be specified for the task. You can specify several [ScanScope.item_#] sections in any order. The application processes the scopes by index in ascending order. The [ScanScope.item_#] section contains the following settings: |
||
|
Description of monitoring scope; contains additional information about the monitoring scope. |
The default value is not defined. |
|
Enables monitoring of the specified scope. |
|
|
Path to the monitoring directory. |
You can use masks to specify the path. Default value: /opt/kaspersky/kess/ |
|
Monitoring scope limitation. Within the monitoring scope, the application scans only the objects that are specified using the masks in the shell format. You can specify several |
Default value: |
The [ExcludedFromScanScope.item_#] section contains the objects to be excluded from all [ScanScope.item_#] sections. You can specify several [ExcludedFromScanScope.item_#] sections in any order. The application processes the scopes by index in ascending order. The [ExcludedFromScanScope.item_#] section contains the following settings: |
||
|
Description of the monitoring exclusion scope, which contains additional information about the monitoring exclusion scope. |
The default value is not defined. |
|
Excludes the specified scope from monitoring. |
|
|
Path to the directory with objects excluded from monitoring. |
You can use masks to specify the path. The default value is not defined. |
|
Limitation of monitoring exclusion scope. In the monitoring exclusion scope, the application only excludes the objects that are specified using masks in the shell format. You can specify several |
Default value: |