On-Demand System Integrity Check

On-Demand System Integrity Check is a task that you can run manually or on a schedule. When running the Baseline System Integrity Monitor task, the application compares the current state of the objects included in the monitoring scope with their baseline state. A baseline is created when the task is first started.

For System Integrity Monitoring to work, you must add at least one rule. A System Integrity Monitoring rule is a set of criteria that define the access of users to files and the registry. System Integrity Monitoring detects changes in the files and the registry within the specified monitoring scope. The monitoring scope is one of the criteria of a System Integrity Monitoring rule.

Configuring the monitoring scope for the Baseline System Integrity Monitor task

By default, the monitoring scope of the Baseline System Integrity Monitor task is the same as the monitoring scope of System Integrity Monitoring. You can configure a different monitoring scope for the task.

System Integrity Monitoring does not support the import of HKEY_CURRENT_USER and HKEY_CURRENT_CONFIG keys for the System Integrity Check task. If the monitoring scope of the task contains these keys, the application generates the Monitoring scope includes incorrect objects event.

How to configure a different monitoring scope for the Baseline System Integrity Monitor task in the Kaspersky Security Center Administration Console

How to configure a different monitoring scope for the Baseline System Integrity Monitor task in the Kaspersky Security Center Web Console

How to configure a different monitoring scope for the Baseline System Integrity Monitor task in the Application Console

Settings of a Baseline System Integrity Monitor task rule

Parameter

Description

Monitor file operations for the scope

The scope to which you want to apply File Integrity Monitoring. This field is mandatory.

Use masks:

Kaspersky Embedded Systems Security supports environment variables and the * and ? characters when entering a mask:

The * (asterisk) character, which takes the place of any set of characters, except the \ and / characters (delimiters of the names of files and folders in paths to files and folders). For example, the mask C:\*\*.txt will include all paths to files with the TXT extension located in folders on the C: drive, but not in subfolders.

Two consecutive * characters take the place of any set of characters (including an empty set) in the file or folder name, including the \ and / characters (delimiters of the names of files and folders in paths to files and folders). For example, the mask C:\Folder\**\*.txt will include all paths to files with the TXT extension located in folders nested within the Folder, except the Folder itself. The mask must include at least one nesting level. The mask C:\**\*.txt is not a valid mask.

The ? (question mark) character, which takes the place of any single character, except the \ and / characters (delimiters of the names of files and folders in paths to files and folders). For example, the mask C:\Folder\???.txt will include paths to all files residing in the folder named Folder that have the TXT extension and a name consisting of three characters.

Monitored objects

Here you can specify the name or value of a registry key.

Use masks:

Kaspersky Embedded Systems Security supports the * and ? characters when entering a mask:

Exclusions

On the Exclusions tab, you can add objects that you want to exclude from the monitoring scope:

  • For a File Integrity Monitor rule, you can specify a list of folders.
  • For a Registry Access Monitoring rule, you can specify registry keys or values.

Use masks:

Files

List of files and folders monitored by the component. Kaspersky Embedded Systems Security supports environment variables and the * and ? characters when entering a mask:

The * (asterisk) character, which takes the place of any set of characters, except the \ and / characters (delimiters of the names of files and folders in paths to files and folders). For example, the mask C:\*\*.txt will include all paths to files with the TXT extension located in folders on the C: drive, but not in subfolders.

Two consecutive * characters take the place of any set of characters (including an empty set) in the file or folder name, including the \ and / characters (delimiters of the names of files and folders in paths to files and folders). For example, the mask C:\Folder\**\*.txt will include all paths to files with the TXT extension located in folders nested within the Folder, except the Folder itself. The mask must include at least one nesting level. The mask C:\**\*.txt is not a valid mask.

The ? (question mark) character, which takes the place of any single character, except the \ and / characters (delimiters of the names of files and folders in paths to files and folders). For example, the mask C:\Folder\???.txt will include paths to all files residing in the folder named Folder that have the TXT extension and a name consisting of three characters.

Registry

Kaspersky Embedded Systems Security supports the * and ? characters when entering a mask: Exclusion entries have a higher priority than monitoring scope entries.

Event severity level

Kaspersky Embedded Systems Security logs file modification events whenever a file or registry key in the monitoring scope is modified. The following event severity levels are available: Informational, Warning, Critical.

Running the Baseline System Integrity Monitor task

The Baseline System Integrity Monitor task allows checking files or registry keys for changes and also checking the connection of external devices. To check files for changes, you can run the Baseline System Integrity Monitor task in the following modes:

The mode the task runs in does not affect the checking of the registry or external devices.

How to run the Baseline System Integrity Monitor task in the Kaspersky Security Center Administration Console

How to run the Baseline System Integrity Monitor task in the Kaspersky Security Center Web Console

Page top