File Integrity Monitoring Release 4.9.5
November 02, 2026
This release adds hourly scheduling for correlation rules, daily updates to failure reasons for FIMC Stopped assets, start and end dates to scheduled event reports, new container search tokens, and a correlation rule fix.
Enhancement
Run Correlation Rules Every Hour to Detect Incidents Sooner
What Changed For You
You can now schedule a correlation rule to run every hour or every few hours. Each time the rule runs, FIM creates an incident for the matching events, so you can investigate changes within hours instead of waiting up to a day.

Previously, you could schedule a recurring correlation rule only on a daily, weekly, or monthly basis. The recurring schedule now includes an Hourly option, and the rule runs at the hourly interval you specify, starting from the start date and time you specify.
The Hourly option is available in the Schedule Management section of the Incidents > Correlation Rules > Create Correlation Rule page when you select Recurring Job.
For more information, refer to Configuring Correlation Rules to Auto-Create Incidents.
Enhancement
Troubleshoot Stopped FIM Agents Sooner with Daily Failure Reasons
What Changed For You
You can now view the latest failure reasons for assets with the FIMC Stopped agent status every day, so you can troubleshoot and resume file integrity monitoring on those assets sooner.
Previously, FIM ran the Custom Assessment and Remediation (CAR) script that identifies these failure reasons once a week, on Saturdays. FIM now runs the script daily, so the Failure Reasons column on the Assets > Real Time Assets tab shows updated failure reasons every day.
For more information, refer to Viewing Assets.
Enhancement
Verify the Reporting Period in Scheduled Event Reports
What Changed For You
You can now see updated failure reasons every day for assets whose agent status is FIMC Stopped, so you can troubleshoot and resume file integrity monitoring on those assets sooner.

Previously, scheduled event reports displayed the report generation date and the filter query, but not the start and end dates of the events included in the report. Scheduled event reports now display Start Date and End Date in the report summary, along with Filter Query and Total Counts. FIM derives these dates from the date range in the report's filter query, including relative ranges such as dateTime:[now-1w..now], and displays them in UTC.
The Start Date and End Date fields are available in the PDF, CSV, and HTML formats for event reports you schedule from Reports > Report Rules > Create Report Rule with Events as the report source, but not for reports that use Assets as the report source.
For more information, refer to Creating Reports on FIM Events.
Token
New Tokens in FIM
| Token | Tab | Description |
|---|---|---|
|
container.cluster.name |
Events > All Events Events > Ignore Events Events > Event Review |
Search for container-based events by the name of the cluster from which the event originated. Example:
|
|
container.cluster.namespace.name |
Events > All Events Events > Ignore Events Events > Event Review |
Search for container-based events by the name of the namespace from which the event originated. Example:
|
For more information, refer to the Search Events Tokens.
Fix
Fixes
The following issues are fixed in this release:
| Component/Category | Description |
|---|---|
| FIM - Correlation Rules | We fixed an issue where reusing the query for a saved correlation rule, such as reopening the rule or copying its query into a new rule or the All Events search, caused a validation error. This issue occurred because FIM saved the actor.actualUsername and actor.auditUsername tokens as actor.auditUserName (with a capital N), which query validation did not recognize. Now, saved correlation rules, including rules created before this release, display the actor.actualUsername token, and you can reuse their queries without errors. Both tokens search the same field, so your rules continue to match the same events. |