This topic summarizes requirements for a Tanium Appliance installation.
Obtain a valid license from your Tanium technical account manager (TAM). The same license file is used to activate all of the Tanium appliances in your deployment. Your TAM must know the fully qualified domain names (FQDN) for each of the appliances in your deployment in order to generate your license file.
The connections to the Tanium Console or SOAP and REST APIs, the connections between Tanium Server and Tanium Module Server, and connections to the Module Server are secured with SSL/TLS certificate and key exchanges. The installation process uses self-signed certificates. We recommend that you verify the installation with the self-signed certificates before you replace them with your commercial or enterprise CA certificates. Doing this facilitates troubleshooting by separating potential installation issues and SSL issues.
For more information on SSL certificate requirements, see the Tanium Core Platform Deployment Reference Guide: SSL certificates.
Tanium components use TCP/IP to communicate over IPv4 networks. IPv6 is not supported. You must work with your network administrator to ensure that the Tanium components are provisioned IP addresses and that DNS can be used to resolve hostnames.
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.
The following table summarizes the Tanium processes and default values for ports used in Tanium core platform communication. Network firewalls might need to be configured to allow the specified processes to send/receive TCP via the ports listed. For a detailed explanation, see Tanium Core Platform Deployment Reference Guide: Network ports.
In addition, the installation and management of the appliance requires communication over common network service ports. The following table shows the default ports for these services.
|Services||Inbound port||Destination port|
|ESP (IPSec for HA cluster)||50/ip||50/ip|
|IKE (IPSec for HA cluster)||500/udp, 4500/udp||500/udp, 4500/udp|
|LDAP (optional)||389/tcp, 636/tcp|
|SSH, SCP, SFTP||22/tcp||22/tcp|
|iDRAC (recommended)||443/tcp*, 5900/tcp*|
|* These ports need to be open only for the IP address of the dedicated iDRAC port (if applicable). The iDRAC port has an IP address that is different from the TanOS network interfaces. See Configure the iDRAC interface|
For a network port summary that includes solution module ports, see the Tanium Support Knowledge Base article (login required).
During both installation and ongoing operations, the Tanium Server must be able to access specific Internet URLs to import updates to Tanium core components and modules. For a list of URLs, see Tanium Core Platform Deployment Reference Guide: Internet URLs required.
If your enterprise network environment requires outbound Internet connections to traverse a proxy server, you can configure settings to use to traverse the proxy server. For guidelines on proxy settings, see Tanium Core Platform Deployment Reference Guide: Proxy server settings.
If you plan to deploy Tanium into an air-gapped environment, see Reference: Airgap support.
Last updated: 11/13/2019 8:26 AM | Feedback