Requirements
This topic summarizes the requirements for installing Tanium™ software.
Installation package and license files
Your technical account manager (TAM) provides the following Tanium™ installation package files and license file required to complete the installation:
- SetupServer.exe
- SetupModuleServer.exe
- SetupZoneServer.exe
- tanium.license
The installation package for each of these three servers must have the same build number (for example, all must have build number
The license is bound to the hostname you assign to the Tanium™ Server. In high availability (HA) deployments, the license must specify the hostnames of both Tanium Servers. Inform your TAM if the server hostnames change.
Server host system requirements
The following table summarizes basic requirements for server hosts. For detailed version specifications and sizing guidelines, see Reference: Host system sizing guidelines.
Client host system requirements
The following table summarizes basic requirements endpoint host systems. Hardware resource requirements vary according to the actions that may be taken on the endpoint. For hardware resource guidance, consult with your technical account manager (TAM).
| Operating system | OS Version | Tanium Client Version |
|---|---|---|
| Microsoft Windows Server |
* Nano Server not supported. |
7.2.314.3476, 7.2.314.3211, 7.2.314.2962, 6.0.314.1540, 6.0.314.1450 |
| Windows Server 2003, 2003R2 | 6.0.314.1540, 6.0.314.1450 |
|
| Microsoft Windows Workstation |
|
7.2.314.3476, 7.2.314.3211, 7.2.314.2962, 6.0.314.1540, 6.0.314.1450 |
| Windows XP (including Embedded) | 6.0.314.1540, 6.0.314.1450 |
|
| macOS (Intel processor only) |
* See the Tanium™ Support Knowledge Base for the Minimum Tanium product versions required to support endpoints that run macOS 10.14 Mojave. |
7.2.314.3476, 7.2.314.3236, 7.2.314.2962, 6.0.314.1579, 6.0.314.1442 |
| Linux | ||
| Amazon Linux 2 LTS (2017.12) | 7.2.314.3476, 7.2.314.3211 |
|
| Amazon Linux 1 AMI (2016.09, 2017.12, 2018.03) | 7.2.314.3476, 7.2.314.3211, 7.2.314.2962, 6.0.314.1579 |
|
| Debian 9.x, 8.x | 7.2.314.3476, 7.2.314.3211 |
|
| Debian 7.x, 6.x | 7.2.314.3476, 7.2.314.3211, 7.2.314.2962, 6.0.314.1579, 6.0.314.1442 |
|
| Oracle Enterprise Linux 7.x, 6.x | 7.2.314.3476, 7.2.314.3211, 7.2.314.2962, 6.0.314.1579 |
|
| Oracle Enterprise Linux 5.x | 7.2.314.3476, 7.2.314.3236, 7.2.314.2962 |
|
|
7.2.314.3476, 7.2.314.3211, 7.2.314.2962, 6.0.314.1579, 6.0.314.1442 |
|
|
7.2.314.3476, 7.2.314.3236, 7.2.314.2962, 6.0.314.1579, 6.0.314.1321 |
|
|
7.2.314.3211, 7.2.314.2962, 6.0.314.1579 |
|
|
7.2.314.3211, 7.2.314.2962, 6.0.314.1579, 6.0.314.1442 |
|
| Ubuntu 18.04 LTS | 7.2.314.3476, 7.2.314.3211 |
|
| Ubuntu 16.04 LTS | 7.2.314.3476, 7.2.314.3211, 7.2.314.2962, 6.0.314.1579 |
|
| Ubuntu 14.04 LTS | 7.2.314.3476, 7.2.314.3211, 7.2.314.2962, 6.0.314.1579, 6.0.314.1442 |
|
| Ubuntu 10.04 LTS | 6.0.314.1579, 6.0.314.1442 |
|
| AIX |
* 64-bit only, requires xlC.rte 12.1.0.1 or greater. |
6.0.314.1437 |
| Solaris |
* Requires SUNWgccruntime. |
6.0.314.1321 |
Tanium in cloud service environments
The Tanium Server and Tanium Client generally support the same operating systems listed above when virtualized in cloud service environments. Tanium customers have used our software in:
- Amazon Web Services (AWS)
- Google Cloud Platform (GCP)
- Microsoft Azure
- Oracle Cloud Infrastructure (OCI)
Use of Tanium in cloud environments entails important architectural considerations that can be unique from one deployment to another. Work with your TAM when planning to deploy or expand into such environments.
Network connectivity and firewall
Tanium components use TCP/IP to communicate over IPv4 and IPv6 networks (IPv6 support requires 7.3 versions of the Tanium Core Platform servers and Tanium Client). You must work with your network administrator to ensure that the Tanium components are provisioned with IP addresses and can use DNS to resolve hostnames.
The table below summarizes the Tanium processes and default values for ports used in Tanium Core Platform communication. Host and network firewalls might need to be configured to allow the specified processes to send/receive TCP via the ports listed. The Tanium installer opens required ports in the Windows host firewall. You must work with your network security administrator to ensure the platform components can communicate through any security barriers (such as firewalls) in their communication path. For a detailed explanation, see Reference: Network ports.
Your security administrator might also need to create rules to exempt or exclude Tanium processes that run on the host computers from blocking by antivirus or processing by encryption or other security and management stack software. For details, see Reference: Host system security exceptions.
Internet access (direct or by proxy)
During installation, the Tanium Server installer (SetupServer.exe) prompts you to download SQL Server Native Client and SQL Server CLI Utilities if you have not already done so. To enable the download, the host computer must be able to connect to http://download.microsoft.com.
During installation and ongoing operations, the Tanium Server and the browser used to access the Tanium Console must be able to connect to https://content.tanium.com to import updates into Tanium Core Platform components and modules.
The Tanium Server might need to connect to additional locations, based on the components you import. The following table lists URLs that the Tanium Server accesses.
| Import type | Components | URLs |
|---|---|---|
| Any |
Any (Both the Tanium Server and the browser used to access the Tanium Console must connect to these URLs.) |
https://content.tanium.com |
|
http://*.digicert.com
Module import fails if the Certificate Revocation List is blocked or inaccessible. |
||
| Content | Initial Content | http://linux-usb.org |
| Managed Applications (login required) | http://ardownload.adobe.com/ http://airdownload.adobe.com/ http://download.macromedia.com/ http://dl.google.com/ https://download.mozilla.org/ https://secure-appldnld.apple.com/ |
|
| Windows Security Patch Management | http://download.windowsupdate.com | |
| IR Gatherer | https://download.sysinternals.com | |
| Modules | ||
| Patch | http://download.windowsupdate.com | |
| IOC Detect | https://download.sysinternals.com | |
| Labs Content | EMET | https://download.microsoft.com |
| MSERT | https://definitionupdates.microsoft.com | |
| Stinger | http://downloadcenter.mcafee.com | |
| Symantec | https://support.symantec.com | |
|
Notes:
|
||
If your enterprise security policy does not allow Tanium Server to access these locations directly, you can use proxy servers. See Reference: Proxy server settings.
If your enterprise network uses SSL intercept technologies, such as man-in-the-middle (MITM) proxies, you must configure them so that they do not prevent the Tanium Server and Tanium Module Server from downloading files from these locations.
If you plan to deploy Tanium into an air-gapped environment, consult with your TAM.
SSL certificates
SSL/TLS certificate and key exchanges secure connections to the Tanium™ Console or SOAP and REST APIs, as well as connections between the Tanium Server and Tanium Module Server.
When you run the installation wizards, they prompt you to generate a self-signed certificate or specify the location of an existing certificate and key that was issued by a commercial Certificate Authority (CA) or your own enterprise CA. As a best practice, use the self-signed certificate option when you complete the initial installation steps provided in this guide. Doing this facilitates troubleshooting by separating potential installation issues and SSL issues. After you verify the deployment, you can replace the self-signed certificate with the certificates that the commercial or enterprise CA issued. For the procedure, see Replacing certificates in your deployment
Administrator account privileges
Work with your Microsoft Active Directory (AD) administrator to provision the accounts needed during Tanium Core Platform installations or upgrades and for post-installation/upgrade activities.
Administrator accounts for installations and upgrades
The following table lists the administrator accounts required to install or upgrade Tanium Core Platform servers, create Tanium databases, or deploy Tanium Clients. You can use a single service account to install the Tanium Server and to create databases on the SQL or PostgreSQL server, as long as the account has the all required group memberships and privileges for those servers. You can also use a single service account to install the Zone Server and Zone Server Hub. You must use a separate service account to install the Module Server.
Administrator accounts for post-installation/upgrade activities
The following table lists the administrator accounts required for regular, ongoing operations performed after installations or upgrades, including running the services for Tanium Core Platform servers and Tanium Clients, and accessing Tanium databases. If you reuse the accounts used for installations and upgades, first reduce the account privileges to those specified in the following table. You can use a single service account to run the Tanium Server service and access the Tanium databases. You can also use a single service account to run the Zone Server and Zone Server Hub services. You must use a separate service account to run the Module Server service.
| Service | Account Type | Host System | Required Group or Privileges | Account Purpose |
|---|---|---|---|---|
| Tanium Server and Tanium databases | AD service account* | Tanium Server host | User-level privileges | This service account runs the Tanium Server service. The service runs in the context of the Local System or the AD account, depending on the option you select when installing the server. |
| SQL Server host | DBO on Tanium databases |
This service user account accesses the tanium and tanium_archive databases. If you use the same account for running the Tanium Server service, the account must be able to connect remotely to the SQL Server. The account requires db_owner role membership for the Tanium databases. Assign the View server state privilege as a best practice to enable the Tanium Server to access data faster than the DBO role alone. |
||
| PostgreSQL Server host | User-level privileges | This service user account accesses the tanium and tanium_archive databases. If you use the same account for running the Tanium Server service, the account must be able to connect remotely to the PostgreSQL Server. | ||
| Tanium Module Server | AD service account* | Tanium Module Server host | Administrator | This service account runs the Tanium Module Server service. The service runs in the context of the Local System account. |
| Tanium Zone Server and Zone Server Hub | AD service account* | Tanium Zone Server host | User-level privileges | This service account runs the Tanium Zone Server service. The service runs in the context of the Local System or the AD account, depending on the option you select when installing the server. |
| Tanium Zone Server Hub host | User-level privileges | This service account runs the Tanium Zone Server Hub service. The service runs in the context of the Local System or the AD account, depending on the option you select when installing the server. | ||
| Tanium Client | Local System | Tanium Client Deployment Tool host | Administrator | On Windows, the Tanium Client service runs in the context of the Local System account. |
| *It is possible to use the Local System account in a POC deployment, but not in a production deployment. | ||||
Last updated: 12/18/2018 10:34 AM | Feedback