Release Notes Asset (Version 1.32)

Product Documentation and Resources

• Asset Documentation
• Tanium Product Documentation
• Tanium User Research
• Software Updates and Announcements Signup

Tanium Asset 1.32.126

Release Date: February 20, 2025

Improvements

• Upgraded various third-party libraries to newer versions.

Resolved Issues

• Fixed issue where Asset Installed Applications will clear endpoint data when an error state is returned.
• Fixed issues with ServiceNow destinations for Installed Applications.

Known Issues

• Tanium Software Manager (swmgr-cx): Data reset when upgrading
  • For long running instances of swmgr-cx on an endpoint, upgrading swmgr-cx might cause a reset of the Software Manager Database. This reset causes a restart and reset of collected data.
    • Previously collected Software Inventory & Usage (SIU) data is wiped and usage data is reset on affected endpoints.
    • SBOM data is wiped and rebuilt on affected endpoints.
  • If you are planning to upgrade, wait for the March 2025 update.

Tanium Asset 1.32.117

Release Date: December 10, 2024

Asset Software Usage and Inventory Improvements

• What has changed in Asset Software Usage and Inventory?
  • Asset SIU Installed Products sensor enhanced to return Used as T/F values for all products regardless of Tracking status in Asset. No longer do you need to enable Tracking for every product to see if there is Usage.
    • Used is returned as T (true) if there is a Last Used date for the Product that is within the last 90 calendar days. If not then the default value of F(false) is returned.
  • Asset SIU User Interface Enhancements.
    • Now with the changes to the Asset SIU Installed Products sensor, every Product in the Software Inventory and Usage console will now show counts for Used / Unused. No longer does the Asset Operator need to enable Tracking in order to see if a Product is used in their environment.
    • Software Inventory and Usage the Products workbenches now have an Expand details function that is a Live Interact Question for the selected Product and does not require the Product to be tracked by Asset. Values returned are;
      • Version (If the endpoint had multiple versions over time you will see every installed version.)
      • First Seen (The date that SIU first discovered the Product on the endpoint. Over time, this will represent the date that the Product was Installed or Upgraded.)
      • Removed Date (The date that SIU has determined that the Product was removed from the endpoint. Missing dates are expected if the Product is still installed.)
      • First Used (The date that SIU first observed usage for the Product, by Version)
      • Last Used (The most recent date that SIU observed usage for the Product, by Version.)
      • Usage Bucket (The Usage over time that SIU recorded for the Product over a 90 day period, by Version)
• What does this all mean for the Asset Operators?
  • No longer do you have to enable Tracking for every Product on your endpoints. You can now see actual Product usage across your entire landscape.
  • With a simple click of the mouse you can see extended details as well as Product Version history on your endpoints without the need to build complicated Interact queries.
  • You can now focus Asset Application Usage Tracking to those products that have CapEx implications to reduce your licensed Software spend.

Asset File Evidence

• What is Asset File Evidence?
  • Asset File Evidence is a file-based data collection process from endpoints that has been part of the Asset integration to Flexera. With this release, the process has been upgraded to now use index-cx to collect this information.
  • This feature can only be enabled using a Tanium Feature Flag. Contact Tanium Support to have enabled.
• What data is collected by Asset File Evidence?
  • When an Asset File Evidence Profile is created Asset instructs index-cx to start collecting evidence of the following files by extension:
    • .exe
    • .sys
    • .*sys2
    • .*wtag
    • .*ptag
    • .lax
    • .*dtag
    • .sig
• What data elements (attributes) are collected for these files?
  • For all Windows, MAC and Linux Operating Systems
    • File Path
    • File Name
    • File Size
  • Extended: For Windows Operating Systems ONLY and defined in the Asset File Evidence Profile
    • File Version
    • Product Name
    • Product Version
    • Company
    • Description
    • Language
• Frequently Asked Questions
  • Why don't I see File Evidence in Asset Profiles?
    • Asset File Evidence is currently only available for Private Preview. Contact Tanium Support if you would like to start using this feature.
  • Can I control what files are collected by Asset File Evidence?
    • No. For this release, the Tanium team worked directly with Flexera to define file requirements for Windows, MAC and Linux endpoints
  • Why are the Extended Data details blank?
    • The operating system is not Windows.
    • The Windows endpoint is not defined in the targeting group of the profile.
  • If I already have legacy File Evidence collecting data, will this affect me?
    • If you previously had legacy Asset File Evidence running you will need enable Asset File Evidence and then create an Asset Profile for File Evidence collection. Once completed Asset File Evidence will start collecting data from the targetted Computer Groups in the File Evidence Profile.
    • File Evidence collected by the legacy process will clear from the Asset Database over time. It is recommended that you contact Tanium Support if you want to enable the new Asset File Evidence feature.
  • Can I use Index sensors if I only have Asset File Evidence?
    • No. Index sensors for the new index-cx are not included with Asset at this time.
  • What additional updates have been made to this version of File Evidence?
    • File Evidence Profile targeting enforcement. Only targeted Computer Groups will have File Evidence collected.
    • Asset File Evidence now uses index-cx
    • Added Index Maintenance Packages with Asset

TDS Load Improvements

• For TDS Load enabled environments the Asset Primary Key that identifies a unique endpoint now mirrors TDS.
• EID (Endpoint ID) is now used for TDS Load Enabled environments vs the 2 of 3 match that has been used before TDS Loads.
  • Computer Name, Computer ID and Endpoint Fingerprint are used for Saved Questions based Tanium Source loads.
• How will this affect potential duplicate endpoints in Asset?
  • When TDS identifies a duplicate endpoint it will remove the endpoint from TDS and pass the removed EID to Asset.
  • Asset will, at next load, remove those EIDs from Asset regardless of the Asset Purge rules.
  • Manually deleted endpoints from TDS will still follow the Asset Purge rules.
• Date stamp updates for last_seen_at and last_seen_in_tds will now be updated during every Tanium Source run vs the original once a day update.

Improvements

General

• Third-party dependency updates.
• Removed unnecessary errors from Asset start up logs
• ECF Data Improvements
• Added Create/Rotate RBAC Rights to Asset API User Role

Database

• RDB Client Upgrade.
• Asset RDB Performance Tuning
• Purge Short-lived Assets. Short-lived assets are endpoints that are online for less than 1% during the first 30 days in Tanium.
• RDB Query Optimizations
• Improved Asset Report Data Storage
• RDB Database Maintenance Improvements

SIU

• Add upper limit for SIU Tracked Products. Default 300
• The SIU Limit for Tracked Products up to 300 within Workbench will create warnings once reached or exceeded.
• ECF now handles SIU Tracked Items in a single config vs many

Integrations

• Extend TDS Data Mapping to support 3rd Party Integrations
• Limit Destination concurrency to prevent failures.
• Better ServiceNow error handling for Destination / Push failures.
• Added Cert Support for AWS Integration
• New Custom Sources to import data into Asset
  • Note: The AWS, Azure, Google Chromebook, Google Cloud and Intune sources are currently beta features.
  • AWS
    • AWS Organization is now supported
  • Azure
  • Google Cloud
  • Google Chromebooks
  • Intune
  • Import API
    • Updates to Asset Reconciliation that will roll up added data and prevent Duplicates with existing Asset managed endpoints.
• Custom Source will only save after successful connection with source
• Added retry logic for Google and Azure Custom Sources

Reports and Views

• Provided the ability to remove ServiceNow / Flexera (Reserved) Views and Reports
• New Data Elements to All Assets Report
  • Source ID
• New Tanium Support Report
  • Enhanced All Assets report that includes TDS Load Data details
    • Asset ID
    • Source ID
    • Computer Name
    • Computer ID
    • Endpoint Fingerprint
    • Serial Number
    • EID
    • Operating System
    • Created At
    • Updated At
    • Last Seen At
    • Last Seen In TDS
    • Asset Is Managed

Issues Addressed

General

• Fixed issues with Asset API Updates not registering in Gateway.
• Fixed logging issues with Warning messages being recorded as Error.
• Fixed issues where Asset Destination jobs report Running after Failure
• Fixed issue where Asset fails to register with Gateway properly
• Failures on Tanium Source First Loads
• Asset Permissions do not allow False as a value
• Various UI Improvements
• Fixed broken Documentation links in Asset UI
• Fixed issue with missing reference IDs in RDB Database
• Fixed issue with Tanium Cloud Network Egress Alert in On Prem Tanium builds.
• Fixed Asset Upgrade hiding Profiles when upgrading to recent builds
• Fixed issues with ServiceNow Destination failures after recent release
• Fixed issue with Asset Is Managed not being recorded properly in TDS properties

Integrations

• Fixed issue where removing all Custom Attributes from Asset block the creation of any new Custom Attributes that are used by Asset ImportAPI.
• Fixed issues with Tanium Source Load not completing.
• Fixed issue where edit Tanium Source was visible.
• Fixed Intune Source never terminating on API errors.
• Fixed issues with External Source connections.
• Fixed issue with Custom Source Fields not masking properly
• Fixed errors with Intune Source Data Mapping
• Fixed issue with updates to Custom Sources causing screen to hang
• Fixed Asset Service restart on AWS API Gateway dropped connections
• Fixed issue with ImportAPI requiring connection verification when there is no connection required
• Fixed issue with AWS not assuming Elevated Roles when provided causing errors
• Fixed issue when creating Intune Custom Source
• Unable to connect to DB Source using TLS
• Custom Source does not validate mappings on Generate Preview
• Asset API requires elevated privileges for certain basic Attributes
• Fixed errors when trying to create a Database Source
• Fixed errors when filtering by Source when there are none present
• Fixed errors when editing Import API JSON
• Fixed errors when trying to Create or Update Custom Sources

Reports, Views, and Attributes

• Fixed issue where you could not select Date/Time filter for Date based Attributes.
• Fixed issue with Attributes that have a hyphen (-) in the Name.
• Fixed Report Filters failing when Reference Data is added to Repor
• Fixed performance issues with Asset Add Attributes page loading slowly
• Fixed issue where SIU Usage Reports were including endpoints where Usage reported as Not installed
• Reference Attributes fail to clear old results where No Results is returned
• Errors when editing Last Seen filter in Asset Reports
• Fixed errors in Age of Asset report query
• Unable to delete Custom Attributes
• Fixed timeout issues in Asset Export Service for Reports
• Fixed issues where Attribute Evaluation defaulting to Reference when actually Simple

SBOM

• Errors when selecting SBOM Libraries for tracking and reporting
• Fixed issues with establishing session specific context when creating SBOM profiles.
• Fixed issues where you were unable to delete SBOM Reports after SBOM removal
• Fixed issue when toggling SBOM Tracking from start to stop adding a null to the attribute

Sensors

• Removed legacy sensor Asset - Tools Version.
• Fixed issues Asset SIU Installed Products returning errors on Unix Endpoints. Asset SIU Installed Products only supported on Mac and Windows.
• Fixed issues with Asset SQL Server sensor
• Fixed SSL Errors when running Asset SQL Server Sensors
• Sign Powershell Sensor content
• Fixed issues with upgrades not changing Asset Saved Questions from Computer Serial Number to Endpoint Fingerprint