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 Connect (Version 5.22)

From Tanium Knowledge Base
Jump to navigation Jump to search

Tanium Connect Version 5.22.60

Release Date: August 20, 2024

Improvements

  • Updated internal dependencies.

Tanium Connect Version 5.22.59

Release Date: August 6, 2024

Improvements

  • Updated internal dependencies.

Tanium Connect Version 5.22.57

Release Date: June 18, 2024

Resolved Issue

  • Fixed a display issue.

Tanium Connect Version 5.22.56

Release Date: May 16, 2024 Updated Date: June 17, 2024

Improvements

  • Stability improvements.

Known Issue

  • In the Connect Overview, the Scheduled Connections per Hour graph aggregates and displays the number of scheduled connection runs for all destinations per day, not per hour.

Tanium Connect Version 5.22.54

Release Date: April 23, 2024 Updated Date: June 17, 2024

Requirements

  • NEW : Comply 2.24+ is required for existing and new Comply integrations. Please ensure Comply meets the minimum version requirement before upgrading Connect.
  • Tanium Server 7.4.5.1246+
  • RDB 1.2.155+
  • System User Service 1.0.192+
  • Secrets 1.0.263+
  • Email 1.0.26+ is required for connections with an email destination.

Enhancements

  • Connections with an AWS S3 destination will no longer send empty files when no data is returned by a connection. A new advanced setting, “Write File Even if Empty”, can be enabled for any connection where this behavior is not desired.
  • In the Settings page, renamed the “Email Destination Settings” tab to “Email Server Profiles”.
  • Connect now uses the Tanium Secrets shared service for storing credentials.
  • Upgraded AWS SDK for JavaScript to v3.
  • Comply Findings source has improved truncation of long values. Now all fields are truncated, including Criteria, at 32,767 characters. This improves importability in many spreadsheet applications.

Known Issues

  • Connections with an AWS S3 destination that have Object Lock enabled will fail to upload.
  • In the Connect Overview, the Scheduled Connections per Hour graph aggregates and displays the number of scheduled connection runs for all destinations per day, not per hour.

Resolved Issues

  • Fixed an issue where the Computer ID column was omitted from Client Status sources when they were configured to use an ElasticSearch destination.
  • Fixed an issue where having an invalid URL in an ElasticSearch destination could prevent the list of connections from loading on the Connections page.
  • Fixed an issue where a connection using a Tanium Reputation source could be created with a Timeout set to 0, resulting in a connection that could never complete.
  • Fixed an issue where a connection could be created for a Tanium Reputation destination without entering a value in the Hash Field, resulting in a failed connection.
  • Fixed an issue where exported connection configurations with Tanium Reporting sources could not be imported into the same environment.
  • Fixed an issue where importing an exported connection configuration would occasionally fail.
  • Fixed an issue where a failed attempt to import a connection configuration would appear successful in the Connect workbench.
  • Fixed an issue where Comply jobs failed when specifying a report for network unauthenticated scan exports.
  • Fixed an issue with Syslog RFC 5424 Format, where SD-PARAM values containing the double quotation mark (") character were not escaped. RFC 5424 (The Syslog Protocol) section 6.3.3 requires adding a backslash (\) escape character before double quotation marks, backslash, and closing bracket (]) characters if a PARAM-VALUE string contains these characters, to properly parse the value. RFC 5424-compatible parsers interpret invalid escape character sequences as backslash characters. As a result, A\\B and A\B are both interpreted in the same way, as A\B. However, because this fix changes the raw output format, parsers that do not interpret escape character sequences correctly might return different values.
  • Miscellaneous bug fixes and supportability improvements.

Security Updates

  • This release includes security updates. Details of the issue, including affected versions, and mitigation information, can be obtained within Tanium's Community site, or by contacting support.

Product Documentation and Resources