Release Notes Comply (Version 2.16)

Tanium Comply 2.16.97

Release Date: January 31, 2023

Bug Fixes

Fixed an issue with:

• Compliance assessments using browser benchmarks end in COMPLY-FATAL and produce Fail findings.
• Compliance findings for Remote Authenticated assessments are not displayed in Findings.
• Compliance findings from Remote Authenticated assessments return 0 rows when exported through the Tanium Comply (Findings) source.
• The Comply service failing due to too many open files after failing to connect to content.tanium.com via a proxy.

Tanium Comply 2.16.93

Release Date: January 17, 2023

Enhancements

This release includes:

• Support for MacOS 13
• Support for Oracle Linux 9

Bug Fixes

Fixed an issue with:

• Investigations failing with "403 error due to RBACInsufficientPrivilege"
• Large Connect exports failing with "Maximum call stack size exceeded"
• Some Investigation filters not working correctly.
• Errors when importing the same custom profile more than once.

Known Issues

• Compliance assessments using browser benchmarks end in COMPLY-FATAL and produce Fail findings
• Compliance findings for Remote Authenticated assessments are not displayed in Findings.
• Compliance findings from Remote Authenticated assessments return 0 rows when exported through the Tanium Comply (Findings) source.

Tanium Comply 2.16.80

Release Date: December 20, 2022

Enhancements

This release includes:

• A new Investigations workflow allowing you to see the checks performed, the expected values, and the actual values found for all vulnerability and compliance findings. Comply Documentation

Bug Fixes

Fixed an issue with:

• Connect exports of RAS findings returning 0 rows.
• Incorrect "% Compliant" values.
• Not being able to edit the name of network unauthenticated assessments.
• The sensor "Comply - Compliance Percentage" returning TSE-Errors for many rows.
• Custom ID mappings not showing values in the "Comply - JovalCM Results Full" sensor.
• Default CPU settings not being applied on endpoints.
• Network unauthenticated scans sometimes showing the wrong OS for a discovered device.
• Remote unauthenticated scans failing to authenticate with Solaris 10 endpoints.
• Assessments not being updated with the latest CVEs after upgrading to Comply 2.14.

Known Issues

• Some endpoints will see increased memory consumption, up to 50% higher, during scans. This memory usage will be decreased in subsequent releases.
• Uploading XML files for custom profiles generates an error message, but the upload actually works.
• Compliance findings investigations return no results when the Status Category filter is applied
• Findings investigations may fail with 403 error due to missing sensor (Contact Tanium Support)
• Compliance assessments using browser benchmarks end in COMPLY-FATAL and produce Fail findings
• Compliance findings for Remote Authenticated assessments are not displayed in Findings.
• Compliance findings from Remote Authenticated assessments return 0 rows when exported through the Tanium Comply (Findings) source.

Prerequisites

• Tanium™ Connect 4.10.5 or later (To customize columns for exports, you must have Connect 5.8.49 or later)
• Tanium™ Discover 3.0 or later required for remote vulnerability reports
• Tanium™ Endpoint Configuration 1.2 or later
• Endpoint Configuration is installed as part of Tanium™ Client Management 1.7 or later.
• Tanium™ Interact 2.12.114 or later
• Tanium™ Trends 3.6 or later
• Tanium™ Reporting service 1.3.12 or later
• Tanium™ API Gateway 1.1.13 or later
• Tanium™ Blob service 1.0.6 or later
• Tanium™ RDB service 1.0.148 or later
• Tanium™ System User service 1.0.77 or later

Additional Remote Authenticated Scanning requirements:

• Tanium Direct Connect 2.1 or later
• Tanium Discover 4.5.144 or later

Additional Investigations requirements:

• Tanium Interact 2.14.106 or later for full functionality (converting Findings filters to Investigations filters is not supported with earlier versions of Interact)

Supported Tanium Platforms

• Tanium Server 7.4.1.1939 or later