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 API Gateway (Version 1.6)

From Tanium Knowledge Base
Jump to navigation Jump to search

Tanium API Gateway 1.6.32

Release Date: March 7, 2023

Security Update

  • 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.

Tanium API Gateway 1.6.31

Release Date: February 7, 2023

Resolved Issues

  • Fixed an issue where results return an error when response contained [no results]
  • Fixed an issue where results using FieldFilters did not match the results available in the workbench

Tanium API Gateway 1.6.29

Release Date: January 31, 2023

New Features

  • The endpoints query now supports filtering capabilities for the compliance.cveFindings, complianceFindings, and sensorReadings fields.
    • The currently supported operations include: EQ, CONTAINS, STARTS_WITH, ENDS_WITH, and MATCHES.
    • A new flag (restrictOwner) controls whether the filter applies only to the sensor values or also restricts the participating endpoints. This defaults to true.
    • Use of the compliance filters requires a minimum Comply solution version of 2.17.167.
  • The endpoints query now supports the ability to filter out endpoints that contain error or [no results] in requested sensors. This can be configured through setting the excludeErrors or excludeNoResults flags in the tds and ts sources.
  • The endpoints query now omits hidden sensor columns from the sensorReadings field by default. Hidden columns will be displayed if they are selected explicitly by name, or if the new includeHiddenColumns argument is given with a true value.

New Fields

The following new fields add new request functionality:

  • Comply requests
    • query.endpoints.edges.node.compliance.cveFindings (filter) - filter endpoint results based on CVE findings field values
    • query.endpoints.edges.node.compliance.complianceFindings (filter) - filter endpoints results based on compliance findings field values
  • Endpoint requests
    • query.endpoints (filter.memberOf.id) - filter endpoint results based on computer group membership, referencing the computer group ID
    • query.endpoints (source.tds.excludeErrors) - exclude endpoint results that contain common errors in returned field values from the Tanium Data Service source
    • query.endpoints (source.tds.excludeNoResults) - exclude endpoint results that contain [no results] in returned field values from the Tanium Data Service source
    • query.endpoints (source.ts.excludeErrors) - exclude endpoint results that contain common errors in returned field values from the Tanium Server source
    • query.endpoints (source.ts.excludeNoResults) - exclude endpoint results that contain [no results] in returned field values from the Tanium Server source
    • query.endpoints.edges.node.sensorReadings (includeHiddenColumns) - return hidden sensor columns in the response
    • query.endpoints.edges.node.sensorReadings (sensors.filter) - filter endpoint results based on sensor reading column values
  • Sensor requests
    • query.sensors.edges.node.columns.hidden - return whether a sensor column is hidden or not hidden by default

Deprecated Fields

No fields are deprecated in this release. Fields are deprecated in favor of replacement fields, which offer improved functionality or ease-of-use. After 12 months from the initial announcement, deprecated fields receive support and maintenance for a minimum of 6 months. For the best results, migrate any deprecated fields in your requests to the suggested replacement fields.

Improvements

  • The endpoints query ts data source honors its maxWaitTime argument and computes success correctly.
  • The endpoints query no longer requires column names to be specified for filters on multi-column sensors when using the UPDATED_AFTER or CREATED_AFTER operators with the tds data source.
  • The endpoints query allows much larger responses when used with the tds data source.