Editing the monitoring scope

File Integrity Monitor cannot work without a specified monitoring scope. This means you must specify the paths to the files and folders whose changes File Integrity Monitor will control. We recommend adding rarely modified objects or objects that only the administrator has access to. This will reduce the number of File Integrity Monitor events.

To reduce the number of events, you can also add exclusions to the monitoring rules. Exclusion entries have a higher priority than monitoring scope entries. For example, the organization uses an application whose files you want to monitor for integrity. To do so, you need to add the path to the folder with the application (for example, C:\Users\Testadmin\Desktop\Utilities). You can exclude log files from the monitoring rule because such files do not affect system security. Moreover, the application constantly modifies log files, which results in a great number of similar events. To avoid this, add log files to exceptions (for example, C:\Users\Testadmin\Desktop\Utilities\*.log).

How to edit a monitoring scope in the Administration Console (MMC)

How to edit a monitoring scope in the Web Console

How to edit a monitoring scope in the application interface

Page top