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 install the Tanium Server, Tanium Module Server, and Tanium Zone Server:
- 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 Tanium Core Platform and database servers that are installed on customer-provided Windows infrastructure. For detailed version specifications and sizing guidelines, see Reference: Host system sizing guidelines.
| Server | Hardware | Operating System | Software |
|---|---|---|---|
| Tanium Server |
CPU cores: 4 to 80 Memory: 16 to 512 GB Disk: 100 GB to 3.5 TB |
|
A web browser is required to use Tanium Console: see Tanium Console User Guide: Web browser requirements. |
| Database Server | CPU cores: 4 to 32 Memory: 4 to 48 GB Disk: 125 GB to 750 GB |
|
|
| Tanium Module Server | CPU cores: 4 to 16 Memory: 8 to 48 GB Disk: 150 GB to 300 GB |
|
|
| Tanium Zone Server | CPU cores: 4 to 80 Memory: 8 to 256 GB Disk: 100 GB to 3.5 TB |
|
Client host system requirements
The following table summarizes basic requirements for endpoint host systems where you install the Tanium Client. Hardware resource requirements vary based on the actions that you deploy to the endpoints; consult your technical account manager (TAM) for guidance.
We strongly recommend that all Windows endpoints have the following root certificate authority (CA) certificates because they are required to verify the integrity of the Tanium Client binaries:
- DigiCert Assured ID Root CA (thumbprint 0563B8630D62D75ABBC8AB1E4BDFB5A899B24D43)
- DigiCert High Assurance EV Root CA (thumbprint 5FB7EE0633E259DBAD0C4C9AE6D38F1A61C7DC25)
- DigiCert SHA2 Assured ID CA (thumbprint E12D2E8D47B64F469F518802DFBD99C0D86D3C6A)
- DigiCert SHA2 Assured ID Code Signing CA (thumbprint 92C1588E85AF2201CE7915E8538B492F605B80C6)
| Operating system | OS Version | Tanium Client Version |
|---|---|---|
| Microsoft Windows Server |
* Nano Server not supported. |
7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 6.0.314.1540 |
| Windows Server 2003, 2003R2 | 6.0.314.1540 | |
| Microsoft Windows Workstation |
|
7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 6.0.314.1540 |
| Windows XP (including Embedded) | 6.0.314.1540 | |
| macOS (Intel processor only) |
macOS 10.15 Catalina*
* If you enable the app notarization requirement (a security process that Apple introduced in macOS 10.15), you must install Tanium Client 7.2.314.3608 or later. |
7.2.314.3608 7.2.314.3518 |
* 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.3608 7.2.314.3518 7.2.314.3476 7.2.314.3236 6.0.314.1579 |
|
| OS X 10.10 Yosemite | 7.2.314.3518 7.2.314.3476 7.2.314.3236 6.0.314.1579 |
|
| Linux | ||
| Amazon Linux 2 LTS (2017.12) | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 |
|
| Amazon Linux 1 AMI (2016.09, 2017.12, 2018.03) | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 6.0.314.1579 |
|
| Debian 9.x, 8.x | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 |
|
| Debian 7.x, 6.x | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 6.0.314.1579 |
|
| Oracle Enterprise Linux 7.x, 6.x | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 6.0.314.1579 |
|
| Oracle Enterprise Linux 5.x | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3236 |
|
|
7.2.314.3584 | |
|
7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 6.0.314.1579 |
|
|
7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3236 6.0.314.1579 |
|
|
7.2.314.3584 7.2.314.3518 7.2.314.3211 6.0.314.1579 |
|
|
7.2.314.3584 7.2.314.3518 7.2.314.3211 6.0.314.1579 |
|
|
6.0.314.1442 | |
| Ubuntu 18.04 LTS | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 |
|
| Ubuntu 16.04 LTS | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 6.0.314.1579 |
|
| Ubuntu 14.04 LTS | 7.2.314.3584 7.2.314.3518 7.2.314.3476 7.2.314.3211 6.0.314.1579 |
|
| Ubuntu 10.04 LTS | 6.0.314.1579 | |
| AIX |
* 64-bit only. Tanium Client 6.0 requires xlC.rte 12.1.0.1 or later, and Tanium Client 7.2 requires xlC.rte 13.1.3.1 or later. |
7.2.314.3584 7.2.314.3518 6.0.314.1437 |
| Solaris |
* Requires SUNWgccruntime. |
7.2.314.3584 7.2.314.3518 6.0.314.1321 |
Internet access, network connectivity, and firewall
Tanium components use TCP/IP to communicate over IPv4 and IPv6 networks. Tanium Core Platform 7.2 and earlier supports only IPv4. If you need IPv6 support in version 7.3 or later, consult your TAM. 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.
During installation and ongoing operations, the Tanium Server and the web browser that you use to access the Tanium Console must connect to https://content.tanium.com to import updates to Tanium Core Platform components and modules. The Tanium Server might need to connect to additional URLs based on the components you import. For a list of the required URLs, see Tanium Core Platform Deployment Reference Guide: Internet URLs required.
The Tanium Server must be able to connect to the Tanium database server and Module Server. In an HA deployment, the Tanium Servers must be able to connect to each other over a reliable Ethernet connection. All these connections require a minimum throughput of 1 Gbps and a maximum round-trip latency of 30 ms.
If your enterprise network environment requires outbound Internet connections to traverse a proxy server, you can configure settings for traversing the proxy server. For details, see Tanium Console User Guide: Configuring proxy server settings.
Table 3 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 Tanium Core Platform Deployment Reference Guide: 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 Tanium Core Platform Deployment Reference Guide: Host system security exceptions.
The following figure illustrates how the Tanium Core Platform uses these ports in an HA deployment on Windows infrastructure.
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 Tanium Core Platform Deployment Reference Guide: SSL certificates.
Administrator account permissions
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 permissions 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 permissions 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 Permissions | Account Purpose |
|---|---|---|---|---|
| Tanium Server and Tanium databases | AD service account* | Tanium Server host | User-level permissions | 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 permission as a best practice to enable the Tanium Server to access data faster than the DBO role alone. | ||
| PostgreSQL Server host | User-level permissions | 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 | Local user or AD | Tanium Zone Server host | User-level permissions | 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 permissions | 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: 11/12/2019 3:30 PM | Feedback