Release Notes Integrity Monitor (Version 2.9)

Thank you for choosing Tanium. This document is intended to document the release of Tanium Integrity Monitor.

Tanium Integrity Monitor 2.9.544

Release Date: November 10, 2020

Endpoints targeted by multiple monitors now correctly use monitor priority to determine which monitor to deploy.
The Integrity Monitor Filtered File Events Overview and Integrity Monitor Unlabeled File Events Overview sensors are no longer automatically registered for collection in Interact.

If Endpoint Configuration approvals are still pending for a new monitor deployment, subsequent monitor deployments will fail until the original changes are approved.

Release Date: November 2, 2020

This release includes a refreshed user experience, bringing more reporting, consistency, and configurability to the forefront.
This release includes a new endpoint configuration framework, replacing the actions and packages formerly used to configure endpoint tooling.

The Integrity Monitor service account now must be the Tanium Administrator or another user with the Integrity Monitor Service Account user role and access to monitored computer groups.
With this release, support is ending for Tanium Administrative Console and Workbench in Internet Explorer 11. For the best experience, use a recent version of Google Chrome, Microsoft Edge, Mozilla Firefox, or Safari to access the Tanium Console.

Enhanced rules now correctly label by timestamp.
The count of endpoints on the monitors list pages now updates more quickly and accurately.
Watchlists with zero paths can no longer be deployed in a monitor.
Endpoints that are not using any enhanced rules no longer report that the Rules Engine is in a failed state.
Uninstalling the Tanium Client now stops the IM process.
The notification to deploy rules is now shown after deleting a rule.

Endpoints targeted by multiple monitors attempt to use monitor priority to determine which monitor to deploy, but in some cases an incorrect priority is used. After upgrading, ensure that endpoints that are targeted by multiple monitors are using the intended monitor.
The Coverage Status chart on the Integrity Monitor Overview page includes endpoints that are not supported by Client Extensions, and these endpoints remain in the Initializing state.