Tanium Asset

Asset Management

Overview

The Tanium Asset connector integrates with the Tanium platform to synchronize asset and endpoint inventory, including hardware specifications, operating system details, network adapters, and installed applications. Records are mapped to the Brinqa Host model.

Data retrieved from Tanium Asset

Connector Object	Required	Maps to Data Model
Asset	Yes	Host

note

For detailed steps on how to view the data retrieved from Tanium Asset in the Brinqa Platform, see How to view your data.

Setup

Connection settings

When setting up a data integration, select Tanium Asset from the Connector dropdown and provide the following:

Setting	Required	Default	Description
Server URL	Yes	https://<servername>	Tanium server URL
Api token	Yes	—	Tanium api token
Domain	No	—	(Optional) Tanium account domain name
Page size	No	1000	Maximum number of records to get per API request
SSL / TLS	Yes	false	Skip certificate verification

Authentication

The connector uses API token authentication. The configured API token is sent in the session request header on every call; the connector does not perform an interactive login at sync time. An Accept: application/json header is also sent.

Endpoint

Method	URL
GET	https://<servername>/plugin/products/asset/v1/assets
GET	https://<servername>/plugin/products/asset/v1/entities

Request Headers

Header	Value
session	<api-token>
Accept	application/json

Request Body

API token authentication is header-based; asset listing requests are GET calls and carry no request body. The asset query is parameterized via query string:

Query Parameter	Description
limit	Page size (from the pageSize configuration property)
minimumAssetId	Cursor for keyset pagination; advanced from the previous page's nextAssetId

Sample Response

A successful assets listing returns a JSON document with a data array and pagination metadata:

{
  "data": [
    {
      "id": 12345,
      "computer_id": "987654321",
      "computer_name": "WIN-HOST-01",
      "system_uuid": "4C4C4544-0042-1234-8030-XXXXXXXXXXXX",
      "serial_number": "ABC123",
      "operating_system": "Windows 10 Enterprise",
      "os_platform": "Windows",
      "os_version": "10.0.19045",
      "manufacturer": "Dell Inc.",
      "model": "Latitude 7420",
      "ip_address": "10.1.2.3",
      "user_name": "jdoe",
      "created_at": "2024-01-01T00:00:00.000Z",
      "updated_at": "2024-06-01T12:00:00.000Z",
      "last_seen_at": "2024-06-09T08:30:00.000Z"
    }
  ],
  "meta": {
    "nextAssetId": 12346,
    "endOfReader": false
  }
}

Response Fields

Field	Description
data[]	Array of asset records; each is a flat map of attribute name to value
meta.nextAssetId	Next cursor id; passed as minimumAssetId to retrieve the next page
meta.endOfReader	true when all pages have been read; pagination stops

Usage

The configured API token is attached to the session header of all subsequent API requests. Pagination iterates with minimumAssetId/nextAssetId until endOfReader is true or no further records are returned.

How to obtain Tanium Asset credentials

Generate a Tanium API token

For the Tanium Asset connector to use the Tanium Asset REST API, you must provide an API token. To generate a token, follow these steps:

1. Login to your organization's Tanium Asset portal as an administrator.

2. Navigate to Administration > Permissions > API Tokens.

3. Click New API Token.

   Complete the following fields:

   • Notes: (Optional) Provide a description for the API token.

   • Expiration: Provide an expiry time in days.

   • Persona: Click the dropdown and select the Persona for which the token is associated with. This Persona must have the Asset Report Reader and Gateway User roles assigned to it, as these are considered to be the minimum roles required to read and retrieve data from the Tanium Asset API. For additional information on Personas, see Tanium Asset documentation.

   • Trusted IP Addresses: Provide the external IP addresses, either IPv4 or IPv6, of the systems with which this token can be used to authenticate. You can use commas or new lines to indicate multiple IP addresses. If you need assistance with the trusted IP addresses for whitelisting, please contact your Brinqa Support team.

4. Click Create, and then click Yes in the Confirm Your Action dialog window.

   Your new API token displays. You cannot view the token again after this. Copy and save it to a secure location.

Note: If you do not have permissions to create an API token, contact your Tanium Asset administrator. For additional information, see Tanium Asset documentation.

(Optional) Create an Asset API-only user

In addition to using credentials tied to an existing Tanium Asset user account, you can also create a dedicated Asset API-only user in Tanium Asset. This account is specifically intended for API access and retrieving data from the Tanium Asset REST API. For additional information on creating an Asset API-only user, see the Tanium Asset documentation.

note

Note on Server URL: When attempting to connect to a customer's Tanium Asset data that is hosted in the cloud, the Server API URL follows this format: https://<customerURL>-api.cloud.tanium.com. If this specific format is not used for cloud environments, the connector may appear to be non-functional.

Data & mappings

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes:

Asset

Source Field Name	SDM Attribute
computer_id, falling back to system_uuid, then id	UID
computer_name	NAME
computer_name (normalized)	HOSTNAMES
constant Host category	CATEGORIES
created_at	SOURCE_CREATED_DATE
derived from os_platform + os_version	OPERATING_SYSTEM
email	EMAIL
enabled ci_item entity fields (e.g. serial_number, os_platform, service_pack, domain_name, ram, uptime, is_virtual, disk_total_space, cpu_name, cpu_speed, cpu_core, cpu_logical_cores, chassis_type, ci_installed_application, ci_network_adapter, ci_physical_disk, ci_logical_disk, ...)	Dynamic attributes
ip_address	IP_ADDRESSES
ip_address (when private)	PRIVATE_IP_ADDRESSES
ip_address (when public)	PUBLIC_IP_ADDRESSES
last_seen_at	LAST_SEEN
manufacturer	MANUFACTURER
model	MODEL
normalized constant Active	STATUS
os_version	CURRENT_VERSION
updated_at	SOURCE_LAST_MODIFIED
user_name	USERNAME

Operations & API

Operations & API

Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).

Asset

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: REST endpoint

Changelog

Changelog

The Tanium Asset connector has undergone the following changes:

Version	Description	Migration Steps
3.0.6	Bug Fixes - Resolved excessive duplicate Asset records caused by an unstable identity key. The connector now uses Tanium's stable per-endpoint identifier so subsequent syncs update the existing record instead of inserting a new one.	• Asset: The unique identifier used for Tanium Asset records has changed. Existing records keyed on the previous identifier will no longer match new syncs and will become stale. Action: stop the connector schedule, archive or delete existing TaniumAsset records for the source instance, upgrade to 3.0.6, then run a full sync to repopulate with stable identifiers.
3.0.5	Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform.	N/A
3.0.4	Improvements - Hostnames imported from Tanium are now normalized to a consistent format, improving matching and deduplication of Asset records against hosts discovered by other connectors.	N/A
3.0.3	Improvements - Date and time attributes reported by Tanium are now imported as proper timestamp values instead of plain text, enabling correct sorting, filtering, and age-based reporting on those fields. - Attributes that Tanium reports as text but returns as numeric values are now normalized to text consistently, preventing import errors and inconsistent attribute values.	• Asset: Date/time attributes that were previously stored as text are now stored as timestamps. Existing Asset records will retain the old text values until refreshed. Action: run a full sync after upgrading to repopulate these attributes with the corrected timestamp type.
3.0.2	Bug Fixes - Fixed an error that could occur when an endpoint reported a missing (null) IP address during sync; such values are now skipped safely instead of interrupting the import.	N/A
3.0.1	Bug Fixes - Assets that report no stable identifier (for example, some re-imaged endpoints) are now skipped and logged rather than being imported with a missing identifier, preventing malformed Asset records.	N/A
3.0.0	Overview The Tanium Asset connector integrates with Tanium to synchronize endpoint asset inventory, including host identity, network addresses, operating system details, and hardware metadata. Category: Asset Management Models	N/A