Tanium Client Status

The Tanium Client Status adapter provides an inventory of all clients that have registered with the Tanium platform.

Related Enforcement Actions:

• Tanium - Create Action
• Tanium - Create Software Deployment

Parameters

1. Hostname or IP Address (required) - The Hostname or IP address of the Tanium server that Axonius can communicate with via the Required Ports. This adapter supports both on-premise and Tanium Cloud instances. When connecting to a Tanium Cloud instance, "-api" must be added to the end of the subdomain of your Tanium Cloud instance. For example: "domain.cloud.tanium.com" should be entered as "domain-api.cloud.tanium.com".
2. User Name or API Token ID (required) - The credentials for a user account that has the Required Permissions to fetch assets. If an API token is being used for authentication, this must be the ID of the API token. The Token ID column in Tanium may be hidden.
3. Password or API Token (required) - The credentials for a user account that has the Required Permissions to fetch assets. If an API token is being used for authentication, this must be the API token string.

4. Only fetch clients that have registered in the past N minutes (optional, default: empty) - Only fetch assets that have registered with the Tanium platform within the past minutes supplied by this value. Tanium considers any agent that has not reported in the past 5 minutes as "broken", however leave this value empty if you want to be able to build queries in Axonius that check for "broken agents". A value of "0" will disable this filter.

5. Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

6. HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.

Advanced Settings

The Tanium System Status adapter has advanced settings which control the logic for fetching assets.

1. Number of assets to fetch per page (required, default: 1000) - Control the number of assets that are fetched per page.
2. Number of seconds to wait in between each page fetch (required, default: 10) - Control the number of seconds to wait in between each page.
3. Devices to exclude by host name (optional, default: Empty) - A comma-separated list of device host names to exclude.
4. Devices to exclude by model (optional, default: Empty) - A comma-separated list of device models to exclude.
5. Devices to exclude by domain (optional, default: Empty) - A comma-separated list of device domain names to exclude.
6. Deduplicate devices - Select this option to deduplicate devices.

Required Ports

Axonius must be able to communicate with the value supplied in Hostname or IP Address via the following ports:

• TCP port 443: REST API

Required Permissions

• Required Micro Admin Permissions

Required Micro Admin Permissions

You must Create a Micro Admin Role since none exists that grants these Micro Admin Permissions:

1. Read System Status

Create a Micro Admin Role

These are the steps to create a role that grant the Required Micro Admin Permissions:

1. Log in to the value supplied in Hostname or IP Address with an account that has the permissions necessary to edit roles.
2. In the navigation menu:
   1. Go to the Permissions > Roles page.
3. In the Permissions Page:
   1. Click New Role.
   2. Select Grant Micro Admin Role.
4. In the Create Role page in the Role Details section:
   1. Fill in the Name field. (for example: System Status Read Only)
5. In the Create Role page In the Micro Admin Permissions section click the plus sign next to the following permissions:
   1. Read System Status
6. The Create Role page should look like:
   
7. At the bottom of the Create Role page:
   1. Click Save.
8. In the Notice dialog window:
   1. Click Continue.

Assigning Required Permissions

These are the steps to assign the Required Permissions to the value supplied in User Name:

1. Log in to the value supplied in Hostname or IP Address with an account that has the permissions necessary to edit users.
2. In the navigation menu:
   1. Go to the Administration > Users page.
3. In the Users Page:
   1. Select the value supplied in User Name from the list of users.
   2. Click View User.
4. In the User Administration page in the Roles and Effective Permissions section:
   1. Click Edit Roles.
5. In the Assign Roles page in the Role Management > Grant Roles section:
   1. Click Edit.
6. In the Edit Grant Roles dialog window:
   1. Select the name of the role created in Create Micro Admin Role.
   2. Click Save.
7. In the Assign Roles page:
   1. Click Show Preview to Continue.
   2. Click Save.
8. In the Notice dialog window:
   1. Click Continue.
9. The User Administration page should look like this:
   
10. Perform the steps in Verifying Permissions

Verifying Permissions

1. Log in to the value supplied in Hostname or IP Address with the values supplied in User Name and Password.
2. In the navigation menu:
   1. Go to the Administration > System Status page.

Version Matrix

This adapter has only been tested with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.