Reference: Host system resource guidelines

You can use the following guidelines to estimate host system requirements for Tanium Core Platform servers. Exact requirements vary based on dynamic usage factors, such as the Tanium modules that you use and the number of managed endpoints. Because usage differs among customers, the requirements listed in the following tables are based on representative data from numerous deployments ranging in size from under 1,000 to over 500,000 managed endpoints.

Tanium Server host system

Operating system support

You can install the Tanium Server on Standard or Enterprise editions of the following Windows servers:

  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019

Resource requirements

Use the following table to determine the device type (physical or virtual) and resources that the Tanium Server host requires. The columns indicate the total endpoints deployed. In a high availability (HA) deployment, both Tanium Servers must meet or exceed the requirements for the total number of endpoints that your deployment targets. That means each server must be able to independently handle load from the full deployment in the event of failure.

Table 1:   Tanium Server resource requirements
Specification Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 500,000¹
Server device type Physical or virtual Physical or virtual Physical or virtual Physical² Physical² Physical²
CPU cores³ 4 8 16 24 40 80
Memory 16 GB 32 GB 48 GB 96 GB 256 GB 512 GB
Disk Space⁴ 100 GB 250 GB 400 GB 750 GB 1.5 TB 3 TB
¹ The Tanium Core Platform supports over one million endpoints. For the resource specifications of deployments with over 500,000 endpoints, contact Tanium.
² Tanium strongly recommends that the host system have 10Gb network cards with chip sets from Intel for deployments with over 70,000 endpoints.
³ Calculate CPU cores based on only the physical cores from allocated CPUs, not the logical cores available with Hyper-Threading enabled.
⁴ Total space for Microsoft OS and Tanium Server. If you use Tanium™ Patch, the Tanium Server needs an additional 500 GB of disk space to store and manage patches. If you use Tanium™ Deploy, the Tanium Server needs additional disk space greater than or equal to twice the Deploy software library storage.

Tanium Module Server host system

Operating system support

You can install the Tanium Module Server on Standard or Enterprise editions of the following Windows servers:

  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019

Resource requirements

Use the following table to determine the device type (physical or virtual) and resources that the Module Server host requires. The columns indicate the total endpoints deployed.

Table 2:   Module Server resource requirements
Specification Up to 35,000 Up to 75,000 Up to 150,000 Up to 500,000¹
Server device type Physical or virtual Physical or virtual Physical or virtual Physical or virtual
CPU cores 4 8 12 24
Memory 12 GB 24 GB 32 GB 64 GB
Disk space 150 GB 150 GB 200 GB 300 GB
¹ The Tanium Core Platform supports over one million endpoints. For the resource specifications of deployments with over 500,000 endpoints, contact Tanium.

Tanium Zone Server host system

Operating system support

You can install the Tanium Zone Server on Standard or Enterprise editions of the following Windows servers:

  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019

Resource requirements

Use the following table to determine the device type (physical or virtual) and resources that the Zone Server host requires. The columns indicate the number of endpoints that report through the Zone Server. In a Zone Server HA deployment, provision each Zone Server to independently handle load for the cluster in case one HA peer fails.

Table 3:   Tanium Zone Server resource requirements
Specification Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 500,000¹
Server device type Physical or virtual Physical or virtual Physical or virtual Physical² Physical² Physical²
CPU cores³ 4 8 16 24 40 80
Memory 8 GB 16 GB 24 GB 48 GB 128 GB 256 GB
Disk space⁴ 100 GB 250 GB 400 GB 750 GB 1.5 TB 3 TB
¹ The Tanium Core Platform supports over one million endpoints. For the resource specifications of deployments with over 500,000 endpoints, contact Tanium.
² Tanium strongly recommends that the host system have 10Gb network cards with chipsets from Intel for deployments with over 70,000 endpoints.
³ Calculate CPU cores based on only the physical cores from allocated CPUs, not the logical cores available with Hyper-Threading enabled.
⁴ Total space for Microsoft OS and Tanium Zone Server. If you use Tanium Patch, the Tanium Zone Server needs an additional 500 GB of disk space to store and manage patches. If you use Tanium Deploy, the Tanium Zone Server needs additional disk space greater than or equal to twice the Deploy software library storage.

PostgreSQL Server

Contact your TAM for guidance on host computer specifications and PostgreSQL server version specifications.

SQL Server

Use the following tables to determine SQL server host and version specifications. The columns indicate the total endpoints deployed.

Operating system support

You can install the SQL server on Standard or Enterprise editions of the following Windows servers:

  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019

You can install the database server on the following Microsoft SQL Server versions:

  • SQL Server 2012
  • SQL Server 2014
  • SQL Server 2016
  • SQL Server 2017 (validated for use only with Tanium 7.2 or later)
  • SQL Server 2019 (validated for use only with Tanium 7.2 or later)

The following table lists the supported Microsoft SQL Server editions for the database server based on the number of managed endpoints:

Table 4:   Database server operating system support
Edition Up to 500 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 500,000¹
Express² check mark          
Standard check mark check mark check mark      
Business Intelligence check mark check mark check mark  
Enterprise check mark check mark check mark check mark check mark check mark
¹ The Tanium Core Platform supports over one million endpoints. For the sizing specifications of deployments with over 500,000 endpoints, contact Tanium.
² Proof-of-concept deployments only.

Resource requirements

Use the following table to determine the device type (physical or virtual) and resources that the SQL server host requires. The specifications are for Tanium Core Platform 7.0 or later.

Table 5:   SQL server resource requirements
Specification Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 500,000¹
Server device type Physical or virtual Physical or virtual Physical or virtual Physical² Physical² Physical²
CPU cores³ 4 4 8 10 16 32
Memory 4 GB 8 GB 16 GB 24 GB 32 GB 48 GB
Disk space⁴ 125 GB 150 GB 200 GB 300 GB 500 GB 750 GB
Database size 5 GB 20 GB 75 GB 150 GB 300 GB 500 GB
Disk array IOPS 100 100 150 250 500 1000
¹ The Tanium Core Platform supports over one million endpoints. For the resource specifications of deployments with over 500,000 endpoints, contact Tanium.
² Tanium strongly recommends that the host system have 10Gb network cards with chipsets from Intel for deployments with over 70,000 endpoints.
³ Calculate CPU cores based on only the physical cores from allocated CPUs, not the logical cores available with Hyper-Threading enabled.
⁴ Total space for Microsoft OS and SQL Server. Microsoft recommends that the disk space available for memory dumps be at least three times the amount of installed RAM. The required disk space for the OS and SQL Server accounts for the size of the OS, the size of the swap file, and the space required for memory dumps.

Most organizations achieve optimal performance using a single, internal RAID array when Microsoft SQL Server transaction logging is set to Simple. If you plan to enable Full transaction logging, you might have to provision an external RAID array to manage the transaction logs.

To determine the specific disk drive performance characteristics and RAID configuration necessary to support deployments of different sizes, see Table 5 for the minimum input and output operations per second (IOPS) that the database server requires. Using IOPS as the performance measurement enables internal storage administrators or storage vendors the flexibility to recommend a final disk configuration to provide optimal performance at the least cost.

The results reported from each managed endpoint use an average of about 20 MB of data. However, storage requirements are directly related to platform usage patterns. Unless actual measurements confirm that the underlying disk infrastructure provides the minimum acceptable performance, the best practice is to not use a storage attached network (SAN) for the Tanium application server databases.