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.6)
Tanium Comply 1.6.3.0002
Release Date: May 15, 2018
Bug Fixes
- Fixed an issue with report result sensors that could return script errors in situations where the detailed report results file is missing or empty.
- Fixed an error in the Vulnerability - Full sensor when pulling in vulnerability discovery dates.
Tanium Comply 1.6.2.0003
Release Date: May 1, 2018
Bug Fixes
- Fixed an issue with CVSS score processing that could result in scores greater than 10.0.
- Fixed an issue where report exports would not complete under certain conditions.
Tanium Comply 1.6.1.0008
Release Date: April 24, 2018
New Features
- Added support for SCAP 1.2 datastreams. These files can now be imported via the Import Benchmark feature.
Bug Fixes
- Fixed an issue where multiple Comply scans could be executed concurrently on an endpoint. Only a single Comply scan can run at a time; additional scans will be prevented from starting and will need to be run again.
Tanium Comply 1.6.0.0059
Release Date: April 3, 2018
New Features
- Added a new user experience to the report list screen.
- Added a new user experience to the vulnerability and compliance report detail screens.
- Added a new user experience to the report exports screen.
- Added automatic updating of report vulnerability definitions if a service account has been configured.
Other Enhancements
- Added new Vulnerability - Full sensors that include the First Found/Last Seen dates for vulnerability results.
For more information on which versions of CIS-CAT, Joval, and SCC are supported, see Comply Supported Engines.
Security Update
- 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.
Bug Fixes
- Fixed an issue where multiple custom checks in a report would cause report export to fail.
- Fixed an issue causing report exports to time out if answered machine threshold did not reach 99%.
- Fixed an issue where vulnerability reports could take an excessive amount of time to display results after completing.
- Fixed an issue where the Remove Client Files package would not properly remove SCC or Joval scan engines or report results.
- Fixed an issue where the font in column headers on some pages would appear red.
- Fixed an issue where editing the schedule of a policy saved action-driven report was not recreating actions correctly.
- Fixed an issue where CIS-CAT jar signature validation was not properly disabled when necessary.
- Fixed an issue with deployment actions not firing when initially created.
- Fixed an issue where aggregate report results were showing too many decimal places.
Additional Release Information
Known Issues
- Java 9 is not currently supported by Tanium Comply.
- In RBAC-enabled environments, a report can can only be deleted by the owner of the report or a Tanium Administrator. Even with Report Administrator privileges, other users will encounter an error if they attempt to remove the report.
- 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.
- Endpoint computers with a single CPU may have their performance more noticeably impacted by Comply scans, even with lowered priority.