Learn about File Integrity Monitoring (FIM) capabilities in Cortex XDR.
File Integrity Monitoring (FIM) serves as a security control designed to detect unauthorized or anomalous modifications to files and folders in the file system. Any change, such as, a new file being created or an existing file being modified, will trigger an event that is sent to the Cortex Platform.
Cortex XDR agent integrates FIM capabilities directly into its endpoint detection and response engine, enhancing the fidelity and actionable intelligence derived from file events. This also allows seamless deployment of FIM capabilities over workstations and servers with the XDR agent installed.
Notice
File Integrity Monitoring usage requires a dedicated FIM add-on or the Cloud Runtime Security add-on, with XDR Pro capabilities enabled.
File Integrity Monitoring requires a Cortex XDR agent with version 8.9.0 and above. FIM capabilities can be enabled on the following platforms and environments. See Where can I install Cortex XDR agent for full platform options.
Platform | Available Implementation |
|---|---|
Windows | Servers and workstations |
Linux | User mode and Kernel mode |
Kubernetes | Containerized environments |
Configuration and implementation
FIM rules are used to define which files and folders should be monitored, and FIM rule groups are used to consolidate multiple FIM rules into a single entity.
Creating, modifying and viewing FIM rule groups and rules is be done in the Rule Groups page, located at the → → menu.
First, a new rule group is created by choosing Add a new FIM rule group.
After defining the general settings of the group, set up FIM rules in the Rules section by selecting with the following properties:
Description: a brief description of the rule and its purpose
Path: the path of the file or folder to be monitored. See the File and Folder path configuration section for more information.
Events To Monitor: type of events that should be monitored. will capture all events on the defined file path, allows the selection of specific event types as Delete, Create, Modify. When choosing Any, new types of events that may be added in the future will also be monitored.
Once created, a FIM rule group must be assigned to a specific File Integrity Monitoring extension profile. Apply File Integrity Monitoring profiles to your endpoint policies
Note
It is recommended to create a policy that targets only the necessary files and folders.