This page summarizes requirements you should understand before you attempt to deploy the Tanium™ Client to endpoints.
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).
On Windows, the Tanium Client is installed as a service that runs in the context of the Local System account.
On AIX, Linux, macOS, and Solaris, it is installed as a system service. The admin user account must be able to use sudo to elevate privileges when installing the Tanium Client and managing the system service.
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.
Host and network firewalls may need to be configured to allow the Tanium Client process to send/receive TCP via ports 17472.
In addition to the client-to-server TCP communication that takes place on port 17472, Tanium Clients also communicate to peers on port 17472. Clients dynamically communicate with peers based on proximity and latency. Peer chains form to match an enterprise topology automatically. For example, endpoints in California form one chain, while endpoints in Germany form a separate chain. With this dynamic configuration in mind, you must allow bi-directional TCP communication on port 17472 between clients on the same local area network, but not necessarily between all clients on the internal network.
Some environments use security software to monitor and block unknown host system processes. Work with your network and security team to whitelist Tanium processes. Define exclusions to allow the Tanium™ platform components to operate smoothly and at optimal performance. Typically, this means configuring the security software to exempt the Tanium™ Client installation directories from real-time inspection as well as setting a policy to ignore I/O from the Tanium binaries.
If you use Microsoft Group Policy Objects (GPO) or other central management tools to manage host firewalls, you might need to create rules to allow inbound and output TCP traffic across port 17472 on any endpoints to be managed.
If running McAfee Host Intrusion Prevention System (HIPS), mark the Tanium Client as both Trusted for Firewall and Trusted for IPS, per McAfee KB71704.
The Tanium Client uses the Windows Update offline scan file, Wsusscn2.cab, to assess computers for installed or missing operating system and application security patches. If your endpoint security solutions scan archive files, refer to the Microsoft KB for information on how to configure those tools to interact appropriately with the Wsusscn2.cab file.
Table 2 lists Tanium Client folders that should be excluded from on-access or real-time scans by antivirus or other host-based security applications. Default values are shown. Include subfolders of these locations when you create the exception rules. If you have changed the defaults, create rules based on the actual locations.
Tanium solution modules may have their own requirements for the client. For a comprehensive list, including solution module requirements, see the Tanium Support Knowledge Base article (login required).
|Windows 32-bit||\Program Files\Tanium\Tanium Client\|
|Windows 64-bit||\Program Files (x86)\Tanium\Tanium Client\|
The following system processes must be allowed (not blocked, quarantined, or otherwise processed):
- TaniumClient.exe (Windows)
- TaniumClient or taniumclient (macOS, Linux, UNIX)
Last updated: 2/20/2018 4:13 PM | Feedback