Release Notes Comply (Version 2.8)

Tanium Comply 2.8.44.0000

Release Date: February 18, 2021

This release includes security updates. Details of the issues, including affected versions and mitigation information, can be obtained within Tanium's Support Portal or by contacting your TAM.

Release Date: February 2, 2021

This release includes:

This release includes fixes for the following issues:

Fixed issue where Comply was utilizing too much CPU during idle times.
Fixed issue where viewing Compliance Reports produced "Error retrieving results...".
Fixed issue where Engine Targeting would cause an error.
Fixed issue where a user with "Comply Deployment Admin" role could not manage configurations.
Fixed issue where Vulnerability Reports from a custom source would display "Invalid Date" for Last Modified Date.
Fixed issue where Export Vulnerability Report Saved Question would erroneously be re-created.
Fixed issue where Vulnerability Reports would display invalid solution links.
Fixed Comply - All Versions and Comply - JRE Installation Status sensors on Windows endpoints.
Fixed issue where the user could not delete a Compliance Standard.
Fixed issue where a Remote Vulnerability Report was missing the Next Run value.

Release Date: December 3, 2020

This release includes:

Modified Engines Configuration page to better organize the scan engines and the JREs.
Use the Comply Action Group for the Coverage charts on the Overview page.
Updated Quick Links to the new user experience design.
Modified the Benchmarks list page to provide columns that indicate whether a benchmark is Tanium certified and the status of the benchmark.
Added currently unsupported benchmarks to the Unsupported Benchmarks List so that a user does not attempt to use them to create a Compliance Report.
Updated the versions of numerous Tanium libraries.
Use the Aggregate By Value feature for Compliance Reports to help improve the load times of Compliance Reports with a large number of endpoints.
Common Module Install now uses the latest Windows 10 compliance benchmark.
Only display reports that have run on the Overview page.
Include service.json in the Comply support bundle.
Provide feedback in the workbench when migrating deployments to the new Endpoint Configuration.
Modified the Engines Configuration page to better organize the scan engines and the JREs.

Fixed issue where custom check results were not being displayed in Compliance Reports.
Fixed issue where an error was displayed for Compliance Results using the new optimized Compliance Results Sensor.
Corrected the Patch Pivot Link in Vulnerability Reports.
Fixed issue where user could not edit the Service Account.
Fixed Configuration Custom Settings Targeting always shown as None.
The Comply - Coverage Status Details sensor was not working on Red Hat Linux endpoints.
Renewed the configuration event trigger so that the configuration check does not expire after 7 days.
Added resilience around downloading the latest Certified Benchmarks to make Common Module Install more resilient to network failures.
Fixed issue where editing a report's start time was not being saved.
Ensured that the first found and last found dates are included when exporting found vulnerabilities.
Fixed issue where a malformed or empty lock file on a Windows endpoint caused scans to not run.
Prevented loopback address in remote vulnerability custom sources.
Added "No Results Reported" for compliance reports and "No Endpoints Scanned" for vulnerability reports that have not run yet.
Fixed issue where Common Module Install would fail for Comply if Tanium Client Management was not installed first.
Fixed issue where Charts on the Overview page did not appear after upgrade.