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.4.2)

From Tanium Knowledge Base
Jump to navigation Jump to search

Tanium Comply 1.4.2.0016

Release Date: January 30, 2018

Other Enhancements

  • Added support for CIS-CAT 3.0.45.

Tanium Comply 1.4.2.0015

Release Date: January 16, 2018

New Features

  • Added full IAVM file upload and mapping support.
  • Added the ability to clone and edit Comply engine deployments.
  • Added the ability to clone custom profiles.
  • Deployment creation screen has been redesigned for clarity and ease of use.

Other Enhancements

  • Added support for Joval 6.0.1 and CIS-CAT 3.0.44.
  • Added a specific role for custom check creation. In RBAC-enabled environments, an administrator must explicitly grant this role to users who are allowed to create and delete custom checks.
  • Added links to vendor vulnerability information pages where applicable. These can be found in report details, the CVE list, and on report exports.
  • Added a sensor to display Comply report ages.
  • Added the ability to use a policy saved action to fire Comply deployments. A saved question to check targeted endpoints for the contents of the deployment is used to trigger the action. This saved question is asked once per hour.
  • The platform of a vulnerability scan will now be automatically set when the "Create Report" button is used from the vulnerability source listing.
  • Added aggregate report numbers to the top of report exports.
  • Added the ability to specify labels for a report at report creation.
  • Added the ability to filter report list by report hash.
  • Added custom profiles and custom checks to support bundle.

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

Bug Fixes

  • Fixed an issue where the schedule of a report using max age scheduling could not be edited.
  • Fixed an issue where default schedule setting on a deployment or report could cause the scheduled start time to be set in the past.
  • Fixed an issue that resulted in a long delay before vulnerability report results were available.
  • Fixed an issue where custom profile creation would fail on a newly created Comply environment.
  • Fixed an issue where the customized title on a custom profile rule would be overwritten when editing the rule value.
  • Fixed an issue where JRE upload could not be performed using Internet Explorer 11.
  • Fixed an issue where policy saved action-driven reports would not report results.
  • Fixed an issue where the distribute over value for a Comply deployment was not being used by the tools distribution action.
  • Fixed an issue where overly aggressive aggregate polling could cause performance issues in large environments.
  • Corrected latest CIS-CAT version text on setup help screen.

Additional Release Information

Known Issues

  • There is currently an issue with the TVL for macOS that results in failed vulnerability scans. As a result, the macOS vulnerability feed has been temporarily pinned to the version available on Nov. 17, 2017. Updates will be enabled once this issue has been resolve.
  • Java 9 is not currently supported by Tanium Comply.
  • In RBAC-enabled environments, Report Administrator users will see an error if they try to remove a report created by another Report Administrator user. The report and its constituent Tanium constructs will be deleted except for the Saved Question associated with 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.

Product Documentation and Resources