IMPORTANT: This site is planned to be decommissioned in 2026. Visit the Tanium Resource Center for all Tanium release notes, user guides, and support information. To view release notes in the Resource Center, see Tanium Release Notes.
IMPORTANT: If you are using semi-annual releases for on premises, see the Release notes for 2024H1 semiannual release, Release notes for 2024H2 semiannual release, or Release notes for 2025H1 semiannual release on the Tanium Resource Center.
Effective October 15, 2024: On prem release notes on the Tanium Knowledge Base are frozen. For release notes related to 7.4 or 7.5 Server and Solutions, see the Monthly updates for Tanium Version 7.4 and 7.5 Server and Solutions on the Tanium Resource Center.

Release Notes Comply (Version 1.2.5)

From Tanium Knowledge Base
Jump to navigation Jump to search

Tanium Comply 1.2.5

Release Date: February 2, 2017

Feature Improvements

  • Added detailed messaging when unsupported/rejected CIS-CAT versions are uploaded.
  • Added CAC support to Comply.
  • Added a workaround to OS X CIS content that caused compliance scans to fail with incorrect platform mismatch error.
  • Added a block engine upload preventing the use of CIS-CAT 3.0.31 and 3.0.32 due to engine instability and problems with the content shipping with these versions.

For more information on which versions of CIS-CAT and SCC are supported, see Comply Supported Engines.

Bug Fixes

  • Fixed an issue where report export was not working on 6.5.
  • Renamed Comply content to be more generic.
  • Fixed an issue where deploying a JRE to a Windows endpoint would not remove old JRE files.
  • Fixed the Remove Client Files content to remove the JRE version file as well as the JRE.
  • Fixed vulnerability post-processing to accept a wider range of content.
  • Fixed an issue where the JRE sensor would fail if the Tool/Comply folder was not present.

Known Issues

  • Tanium Comply does not support any benchmarks that require authentication.
  • Endpoint computers with less than 2GB of installed RAM may not have enough free memory to run the CIS-CAT engine when evaluating CIS checklists.
  • Red Hat vulnerability definitions do not work correctly with Comply.

Product Documentation and Resources