Checklist Summary:

The Tanium 7.x Security Technical Implementation Guide (STIG) is intended to provide security guidelines for the protection of the Tanium application and its components, including but not limited to the Tanium application, Tanium Console, Tanium Module Server, Tanium Clients, and Tanium SQL Database. This Tanium 7.x STIG is intended to apply to Tanium 7.4 and beyond. For versions previous to Tanium 7.4, refer to the appropriate Tanium 7.3 or 7.0 STIG. Tanium 7.x is a scalable endpoint security and management system. Its foundation is the Tanium Core. Tanium Core includes basic asset inventory, control, and utilization monitoring capabilities, as well as connectors for integrating with third-party systems. Tanium uses a linear peer-to-peer architecture specifically designed for fault tolerance, transient endpoints, and global wide area network (WAN) segments. It is not a typical peer-to-peer application; only other Tanium endpoints can communicate over the peer-to-peer architecture. The clients communicate with each other over a specific Transmission Control Protocol (TCP) port.

Checklist Role:

• Office Software

Known Issues:

Not provided.

Target Audience:

Parties within the DoD and federal government’s computing environments can obtain the applicable STIG from the DoD Cyber Exchange website at https://cyber.mil/. This site contains the latest copies of STIGs, SRGs, and other related security information. Those without a Common Access Card (CAC) that has DoD Certificates can obtain the STIG from https://public.cyber.mil/.

Target Operational Environment:

• Managed
• Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

Not provided.

Comments/Warnings/Miscellaneous:

Not provided.

Disclaimer:

DISA accepts no liability for the consequences of applying specific configuration settings made on the basis of the SRGs/STIGs. It must be noted that the configuration settings specified should be evaluated in a local, representative test environment before implementation in a production environment, especially within large user populations. The extensive variety of environments makes it impossible to test these configuration settings for all potential software configurations. For some production environments, failure to test before implementation may lead to a loss of required functionality. Evaluating the risks and benefits to a system’s particular circumstances and requirements is the system owner’s responsibility. The evaluated risks resulting from not applying specified configuration settings must be approved by the responsible AO. Furthermore, DISA implies no warranty that the application of all specified configurations will make a system 100 percent secure. Security guidance is provided for the DoD. While other agencies and organizations are free to use it, care must be given to ensure that all applicable security guidance is applied at both the device hardening level and the architectural level due to the fact that some settings may not be configurable in environments outside the DoD architecture.

Product Support:

Not provided.

Point of Contact:

Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil. DISA will coordinate all change requests with the relevant DoD organizations before inclusion in this document. Approved changes will be made in accordance with the DISA maintenance release schedule.

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

Updated resource per DISA - 8/26/22
updated to FINAL - 9/26/2022

Dependency/Requirements:

URL	Description

References:

Reference URL	Description

NIST checklist record last modified on 09/26/2022