Tanium
Import into OverView the inventory of endpoints managed by Tanium, their installed software and their vulnerabilities
The Tanium connector imports into OverView the inventory of endpoints managed by Tanium. It queries the Tanium Gateway GraphQL API in read-only mode with an API token, on Tanium Cloud as well as on a Tanium platform installed on premises.
The connector reads the data already collected by the Tanium Data Service: it asks no real-time question to the endpoints and therefore adds no load on your fleet. The data imported depends on the Tanium modules you own and on the permissions granted:
- Core: name, domain, serial number, manufacturer, operating system, IP and MAC addresses, primary user, last seen date
- Endpoint Management: installed software
- Comply: vulnerabilities (CVE) detected on each endpoint, optional
- Discover: devices without a Tanium agent (unmanaged), optional
Collecting unmanaged devices (Discover) is enabled by default, collecting vulnerabilities (Comply) is disabled (see Parameters). If a collection is enabled without the module or without the matching role, the import reports a permission error naming the role to grant to the persona.
Prerequisites
- A Tanium administrator account allowed to create personas, assign them roles and create API tokens
- Tanium Cloud: an HTTPS flow allowed from the OverView outbound IP addresses to
https://<customerName>-api.cloud.tanium.com. OverSOC support provides these addresses - Tanium on premises: an OverView OutPost deployed in your network and an HTTPS flow allowed from the OutPost VM to the Tanium server
Information to provide in OverView
| Field | Description |
|---|---|
| API URL | Base URL of the Tanium API, without the /plugin/products/gateway/graphql path. Tanium Cloud: https://<customerName>-api.cloud.tanium.com. On premises: https://<tanium-server> |
| API Token | Tanium API token, including its token- prefix (see the procedure below) |
Parameters
These parameters are optional.
| Parameter | Description | Default |
|---|---|---|
| Include Unmanaged Devices (Discover) | Import the devices without a Tanium agent found by the Discover module. Requires Discover and the Discover Read Only User role (see Optional permissions). Disable it if you do not own Discover | Enabled |
| Include Vulnerabilities (Comply) | Import the vulnerabilities (CVE) detected by the Comply module. Requires Comply and the Comply Report Reviewer role (see Optional permissions) | Disabled |
Procedure
Create the persona
- In the Tanium console, go to Administration > Permissions > Personas and create a dedicated persona, for example
overview-connector. - Assign it the Tanium roles listed in Required permissions and, depending on the modules you own, in Optional permissions. No administration or action role is required.
- In its Computer Groups, uncheck No Computers and check All Computers.
The token only reaches the endpoints of its persona's computer groups. Without All Computers, the import succeeds but brings back no endpoint: when "0 endpoint" is imported, check this computer group first, then the persona's Interact role.
Generate the API token
An API token inherits exactly the permissions of the persona it is generated from. Generate it from the persona created above.
- Go to Administration > Permissions > API Tokens, then click New API Token.
- Fill in the form:
- Notes: an explicit label, for example
OverView - Expiration: 7 days by default, 365 days at most: the maximum duration is recommended, within your security policy
- Trusted IP addresses: the OverView outbound IP addresses for Tanium Cloud, or the LAN IP address of the OutPost VM for an on-premises platform
- Notes: an explicit label, for example
- Click Save.
- Copy the token, including its
token-prefix, and keep it somewhere safe: it will not be displayed again.
Tanium rejects calls made with a token from an address outside its trusted addresses. For an on-premises platform, the LAN IP address of the OutPost VM is shown on the hypervisor console banner.
A Tanium API token is not renewed automatically. Plan its rotation: before it expires, generate a new one and replace it in OverView.
Configure the connector in OverView
- In OverView, go to Data Sources Settings > Sources.
- Select Tanium and click Configure.
- For an on-premises Tanium platform, choose your OutPost as the collection point.
- Enter the API URL and the API Token.
- Click Save Configuration.
Required permissions
The connector is read-only: it goes through the Gateway API only and reads the data already collected by the Tanium Data Service, without launching any action. These three roles are mandatory.
| Persona role | Purpose |
|---|---|
| Gateway User | Call the Gateway API |
| Token - Use | Use an API token on Tanium Cloud |
| An Interact role granting sensors read (for example Interact Basic User) | Endpoint inventory and installed software |
The persona must also have the All Computers computer group (see Create the persona).
Optional permissions
Grant them only if you own the module and its collection is enabled in the connector parameters. If collection is enabled without the matching role, the import reports a permission error.
| Persona role | Module | Purpose |
|---|---|---|
| Comply Report Reviewer | Comply | Vulnerabilities (CVE) detected on each endpoint |
| Discover Read Only User | Discover | Devices without a Tanium agent (unmanaged) |