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 2.0)

From Tanium Knowledge Base
Jump to navigation Jump to search

Tanium Comply 2.0.6.0001

Release Date: March 12, 2019

Bug Fixes

  • Fixed an issue where custom Compliance profiles would not run on Windows under certain circumstances. This issue only occurs when using Joval-Utilities 6.0.7 or Joval-Utilities 6.0.8. Note that Joval-Utilities was the default package beginning with Comply 2.0.5 (as Joval 6.0.8T).

Tanium Comply 2.0.5.0016

Release Date: March 5, 2019

Bug Fixes

  • Fixed an issue where reports could incorrectly be marked as 'Requires Migration' under certain conditions.
  • Fixed an issue where reports could display 'Unable to find Saved Question' immediately after creation.
  • Fixed an issue where some files were not correctly copied during Tools deployment on MacOS.
  • Fixed an issue where Joval 6.0.7 was unable to be uploaded due to an incorrect hash in the whitelist.

Other Enhancements

  • Added support for the Amazon Corretto JRE (version 8) as an alternative to Oracle's JRE.
  • Added support for JovalCM version 6.0.8.
  • Added support for the Joval-Utilities JovalCM packaging for Joval 6.0.7 and newer.
  • Added support for CIS-CAT version 3.0.55.
  • Added support for SCC version 5.1.
  • Added Windows Server 2019 to the list of platforms available for Vulnerability reports.
  • Improved report loading progress indicator by showing the percent completed.
  • Improved messaging related to TVL download and processing failures.

Tanium Comply 2.0.4.0004

Release Date: January 31, 2019

Bug Fixes

  • Fixed an issue where Windows Compliance scans run with the JovalCM engine created an errant results file at C:\Program.
  • Fixed an issue where Windows Vulnerability scans run with the JovalCM engine will not produce the expected results XML.

Tanium Comply 2.0.3.0015

Release Date: January 29, 2019

Bug Fixes

  • Fixed an issue where advanced engine properties could fail to deploy to Windows under certain conditions.
  • Fixed an issue where users could create Remote Vulnerability / Remote Open ports report without a backing NMap scan.
  • Fixed an issue where compliance results percentages were incorrectly rounded up when very close to 100%.
  • Fixed an issue where updating the service account could fail under certain conditions after updating to Comply 2.0.
  • Fixed an issue where creating a report could incorrectly create two saved questions under certain conditions.
  • Fixed an issue where the report detail question was asked before report had run causing empty results to cache for 15 minutes.
  • Fixed an issue where compliance scans could fail on Windows under certain conditions.
  • Fixed an issue where some SCC versions would ignore the benchmark profile selection.
  • Fixed an issue where CPU core affinity setting was ineffective on machines with more than 16 cores.
  • Fixed an issue where the support bundle's filename contained the incorrect month.

Tanium Comply 2.0.2.0008

Release Date: January 8, 2019

Bug Fixes

  • Fixed an issue where the exports page could fail to load when one or more exports did not complete successfully.
  • Fixed an issue where exports of reports created with updated saved questions did not include recent results.
  • Fixed an issue where Tanium Vulnerability Library downloads could get blocked on new Comply installs under certain conditions.

Other Enhancements

  • Improved supportability of report exports by logging detailed information about export question progress.

Tanium Comply 2.0.1.0006

Release Date: December 23, 2018

Bug Fixes

  • Fixed an issue where users were unable to migrate some reports from 1.8 to 2.0 under certain conditions.
  • Fixed an issue where users were unable to export some reports created in versions of Comply prior to 2.0 without migrating them.
  • Fixed an issue where Compliance and Vulnerability CSV report exports were non-functional under certain conditions.

Tanium Comply 2.0.0.0224

Release Date: December 18, 2018

New Features

  • Remote Vulnerability assessment against unmanaged assets.
    • By integrating with Tanium Discover, Tanium Comply can now identify exposure to vulnerabilities in services running on your unmanaged assets.
  • Improved report results accuracy and usability.
    • Report results use better saved question constructs for improved handling of offline endpoints to increase the accuracy of machine counts and individual results.
    • All new reports will be created using this new style of saved question.
    • Existing reports will need to be migrated to this new style of question. We've made this as painless as possible by adding a visual indicator to reports that must be updated and an 'Upgrade Report Question' button to upgrade one or more reports with a single click.
  • New vulnerability report landing page.
    • The Vulnerability report view has an all new look. The landing page for this view is now a high-level overview including a list of the 'Most Vulnerable Computers' as well as the 'Highest Severity CVEs'. The full list of vulnerabilities is still available.

Other Enhancements

  • Added support for JovalCM 6.0.7.
  • Improved logging and supportability.
  • Improved scan concurrency protection (by using the scan's PID).
  • Allow usage/upload of Server JRE as JRE engine for running scans.
  • Added a new loading message to each report's statistics section in the reports list view.
  • Added an indicator to the report summary view to show when Custom ID mapping was used.

Bug Fixes

  • Fixed an issue where the first report in report list is not clickable if top of control is covered.
  • Fixed an issue where SCC compliance scans could fail when running on Linux.
  • Fixed an issue where script error when running concurrent scans, nothing written to Tools/Comply logs.
  • Fixed an issue where users were redirected to Application Settings instead of Compliance Customizations after creating a custom profile.
  • Fixed an issue where the Service Account could not be edited/updated under certain conditions.
  • Fixed an issue where editing a report's schedule to remove scheduling had no effect.
  • Fixed an issue where custom checks were not included in aggregate counts.
  • Fixed an issue where report statistics where not properly configured to re-issue automatically.
  • Fixed an issue with the button layout in the report exports view.
  • Fixed an issue where vulnerability scans on Linux weren't appending errors correctly to aggregate results.
  • Fixed an issue where the results count in detailed views was not based on the filtered set of results.
  • Fixed an issue where the deployments view could incorrectly show valid scheduled actions as legacy.
  • Fixed an issue where vulnerability scans could fail on Ubuntu 18.x under certain conditions.
  • Fixed an issue where users who have report read permission could not download exported reports.
  • Fixed an issue where detailed compliance results counts are wrong for older saved questions.
  • Fixed an issue where changing the engine on a report, the report's saved question was not being updated properly.
  • Fixed an issue where the report list view could be empty after deploying a report.
  • Fixed an issue where scan timeouts were not configured to match Tanium's action timeout.
  • Fixed an issue where unscored vulnerability definitions where incorrectly included in total counts when no vulnerabilities were found.
  • Fixed an issue where reports could be marked "dirty" after editing engine/priority and results could no longer be viewed.
  • Fixed an issue where refresh statistics could fail to retrieve updated statistics.
  • Fixed an issue where JovalCM compliance scans did not return severity scores for STIG scans.
  • Fixed an issue where changing open ports report interval could result in a PackageNotFound error.
  • Fixed an issue where Remote open ports report CSV exports could fail and be empty under certain conditions.
  • Fixed an issue where lock files could potentially fail to be deleted after scans completion.
  • Fixed an issue where some vulnerabilities were incorrectly included in scans due to invalid CVSS scores.
  • Fixed an issue where the stale reports UI could incorrectly include report result XML files in addition to the reports.
  • Fixed an issue where the reports could incorrectly show "Question Returned No Results" when results exist.

Supported Tanium Platforms

Tanium Server 7.0, 7.1, 7.2, 7.3

Product Documentation and Resources

Retrieved from "https://kb.tanium.com/wiki/index.php?title=Release_Notes_Comply_(Version_2.0)&oldid=29145"