Tanium

Prev Next
Self Service Ingestion

Connect this data source on your own, using the Hunters platform.

TL;DR

Supported data types

3rd party detection

Hunters detection

IOC search

Search

Table name

Log format

Collection method

Tanium Audit Logs

tanium_audit_logs

NDJSON

API / S3 list


Overview

Tanium is an endpoint security and systems management platform that gives large organizations real-time visibility, control, and the ability to remediate threats and manage devices at a massive scale. It uses a unique, patented "linear-chain" architecture to communicate efficiently with millions of endpoints, which enables its speed and scalability. The platform integrates multiple IT and security functions, helping to break down silos and improve collaboration between teams.

Tanium audit logs record user activity, system status, and action history, which can be used for security, compliance, and troubleshooting. These logs track a wide range of operations, such as user changes to settings, computer groups, and roles. Tanium recommends forwarding these logs to a central log management solution using tools like Tanium Connect, which can automate exports to destinations like Hunter’ SIEM, email, or file.  

Tanium Direct Connect provides other Tanium solutions a communication channel to endpoints and provides a central location in the Tanium user interface (UI) where you can monitor direct endpoint connections across solutions. For example, Direct Connect enables Tanium Investigate users to monitor and manage processes on endpoints through a direct connection. You can also use Direct Connect to designate specific endpoints as satellites for running certain targeted, secure workloads on other endpoints that Tanium™ Cloud cannot directly reach. For example, a satellite can run remote authenticated scans for Tanium Comply.

Supported data types

Tanium Audit Logs

Table name: tanium_audit_logs

tanium audit logs  contain 33 different sub-log types. please be aware that you would have to set-up 33 integrations through the “Create data source” screen on the portal.

Send data to Hunters

Hunters supports the collection of logs from Tanium using API (and also S3).

To connect Tines logs:

  1. Retrieve the following information by following this guide by Tanium:

    • Host (example - xxx.tanium.com)

    • Audit Type (one of the 33 options)

    • Token (following the guide)

  2. Complete the process on the Hunters platform, following this guide.

Expected format

The expected format of the logs is the JSON format as detailed here:

  1. Working with Tanium audit logs

  2. Reviewing and exporting the audit log

Tanium Audit Log Sample

{
  "object_id": 123,
  "audit_name": "Global - Limited Admin",
  "creation_time": "2025-10-14T14:26:54Z",
  "modification_time": "2025-10-14T14:26:54Z",
  "last_modified_by": "xxx@xyz.com",
  "modifier_user_id": 10,
  "mod_user": {
    "id": 10,
    "name": "xxx@xyz.com",
    "domain": "",
    "display_name": "ABC"
  },
  "details": "User group (ID 1): updated with user ids added 123; ",
  "audit_row_id": 1234,
  "type": 1,
  "type_name": "UpdateObject",
  "object_name": "xxx@xyz.com",
  "object_type_name": "user"
}

The Tanium Audit Logs has 33 different logs (with 33 different endpoints), All of them are based on the same format / schema, with some minor changes.

The supported audit log types are (from their official documentation):

Audit types

Route syntax

api_token

/api/v2/audit_logs/api_tokens

authentication2

/api/v2/audit_logs/authentication

content_set

/api/v2/audit_logs/content_sets

content_set_privilege

/api/v2/audit_logs/content_set_privileges

content_set_role

/api/v2/audit_logs/content_set_roles

content_set_role_membership

/api/v2/audit_logs/content_set_role_memberships

content_set_role_privilege

/api/v2/audit_logs/content_set_role_privileges

content_set_user_group_role_membership

/api/v2/audit_logs/content_set_user_group_role_memberships

dashboard

/api/v2/audit_logs/dashboards

dashboard_group

/api/v2/audit_logs/dashboard_groups

downloader_auth_cert

/api/v2/audit_logs/downloader_auth_certs

downloader_auth_user

/api/v2/audit_logs/downloader_auth_users

downloader_trusted_cert

/api/v2/audit_logs/downloader_trusted_certs

group3

/api/v2/audit_logs/groups

intentional_subnet

/api/v2/audit_logs/intentional_subnets

isolated_subnet

/api/v2/audit_logs/isolated_subnets

local_setting

/api/v2/audit_logs/local_settings

package_spec

/api/v2/audit_logs/packages

persona

/api/v2/audit_logs/personas

pki_key_configuration

/api/v2/audit_logs/pki_key_configurations

pki_root_key

/api/v2/audit_logs/pki_root_keys

plugin_schedule

/api/v2/audit_logs/plugin_schedules

saved_action

/api/v2/audit_logs/saved_actions

saved_question

/api/v2/audit_logs/saved_questions

sensor

/api/v2/audit_logs/sensors

separated_subnet

/api/v2/audit_logs/separated_subnets

server_registration_request

/api/v2/audit_logs/pki_server_registration_requests

server_trust

/api/v2/audit_logs/server_trusts

system_setting

/api/v2/audit_logs/system_settings

user

/api/v2/audit_logs/users

user_group

/api/v2/audit_logs/user_groups

white_listed_url

/api/v2/audit_logs/white_listed_urls

zone_server

/api/v2/audit_logs/zone_server_assignments