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.8)
Tanium Comply 1.8.5.0002
Release Date: December 11, 2018
Bug Fixes
- Fixed an issue where users were unable to create Vulnerability reports in Internet Explorer 11 under certain conditions.
- Fixed an issue where SCC compliance scans were not executing properly on Linux.
Tanium Comply 1.8.4.0001
Release Date: December 4, 2018
Other enhancements
- Added support for CIS-CAT 3.0.54.
Tanium Comply 1.8.3.0002
Release Date: November 6, 2018
Bug Fixes
- Fixed an issue where deployments with customized engine settings were incorrectly considered/labeled as ‘Legacy Deployments’ in the Setup > Deployments view.
- Fixed an issue where Comply was not properly reporting scan errors when the Joval scan engine would fail to execute a scan due to an invalid benchmark XML.
- Fixed an issue where Vulnerability reports were incorrectly displaying the total vulnerability count when no vulnerabilities were found.
Tanium Comply 1.8.2.0000
Release Date: October 23, 2018
Bug Fixes
- Fixed an issue where report exports could not be downloaded by users having only the Report Reviewer role.
Tanium Comply 1.8.1.0001
Release Date: October 9, 2018
Bug Fixes
- Fixed an issue where the associations of custom checks to a newly created report were not correctly saved.
Other enhancements
- Added support for Joval 6.0.6.
Tanium Comply 1.8.0.0012
Release Date: October 2, 2018
Bug Fixes
- Fixed an issue where vulnerability scans would fail on machines whose regional settings call for a comma decimal separator in numbers.
Known Issues
- Custom checks associated with newly created Compliance reports are not correctly saved and will not be included in the content that is evaluated on endpoints. Existing reports are not affected by this issue and will continue to report results correctly.
Tanium Comply 1.8.0.0011
Release Date: September 25, 2018
New Features
- Added the ability to edit all attributes of an existing report except targeted Computer Groups. The title, scan engine, scan priority, schedule, and labels can now be modified. Note that in some instances, you may need to redeploy the report after changing scan engine/priority in order to see results.
- Joval 6.0.5 now ships with Tanium Comply. Version 6.0.5T will be present in the engine list and can be associated with deployments. This version of Joval does not include content. Note that the last three supported versions of the Joval OEM will be included with Comply. At this time, 6.0.4T and 6.0.5T will be available.
Other Enhancements
- Added support for CIS-CAT 3.0.51.
- Added support for exporting report open port reports.
- Implemented WebPack packaging for workbench to improve efficiency.
- Improved the UX of the stale reports dialog.
- Improved the UX of custom check selection on the report creation page.
Bug Fixes
- Fixed an error when copying SCC results files on Linux/macOS systems.
- Fixed an issue where export file names used epoch time rather than human-readable text.
- Fixed an issue where new advanced deployment settings did not overwrite previous values.
- Added table of contents entries for open ports to vulnerability report exports.
- Fixed an issue where republishing a deployment with advanced settings could fail.
- Fixed an issue where the AND/OR computer group selectors would function incorrectly when multiple computer group selectors are present.
- Fixed an issue where filter remote open port reports by protocol would result in no results.
- Fixed an issue where user could not create vulnerability report when report list was filtered to vulnerability reports.
- Fixed an issue where clicking on the remote endpoints link on remote open ports reports would not open the endpoints list modal window.
- Fixed an issue that would cause Comply to fail to load in IE 11.
- Fixed an issue where manually imported benchmarks could result in duplicated SCE check scripts.
- Fixed an issue where permissions on the comply-service-files folder(s) were set incorrectly on 1.7.4. This could cause engine/Java uploads to fail on Linux-based module servers.
- Fixed an issue where mousing over a single rollover button would cause all rollover buttons on a page to appear.
- Fixed issues with report loading performance by paging on large result sets.
- Fixed an issue where report publish jobs would sometimes fail to complete and would not be properly cleaned up. This prevented further deployments of the report.
- Fixed issues with report selection state when filtering on the report list.
- Fixed an issue where the report list would fail to load if any report was missing its saved action.
- Fixed an issue where the home page would show two loading spinners.
- Fixed an issue where vendor specific vulnerability links were missing from vulnerability report exports.
- Fixed some issues with performance and reliability when pulling saved question data.
- Fixed an RBAC issue with the sensor used to pull remote open ports report data.
- Fixed an issue where report publishing could block vulnerability source update operations.
- Added reporting of skipped scans as a scan error.
- Fixed an issue where the Type/Architecture of imported SCC engines was displayed as "null".
- Fixed an issue where import/export of custom profiles did not include customized titles.
- Fixed an issue where Joval license issues were not being reported as scan errors.
- Fixed an issue where "undefined" would be displayed if an attempt was made to delete a report by a user other than its owner.
Known Issues
- Custom checks associated with newly created Compliance reports are not correctly saved and will not be included in the content that is evaluated on endpoints. Existing reports are not affected by this issue and will continue to report results correctly.
Supported Tanium Platforms
Tanium Server 7.0, 7.1, 7.2