Tanium must be configured in a High-Availability (HA) setup to ensure minimal loss of data and minimal disruption to mission processes in the event of a system failure.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-78743	SRG-APP-000226	TANS-SV-000054	SV-93449r1_rule	2018-07-09	1

Description
Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving application state information helps to facilitate application restart and return to the operational mode of the organization with less disruption to mission-essential processes.

Description

Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving application state information helps to facilitate application restart and return to the operational mode of the organization with less disruption to mission-essential processes.

ℹ️ Check
If the system is not considered mission critical, this is Not Applicable. Consult with the Tanium System Administrator to verify that Tanium is configured in a high-availability (HA) Active-Active setup. If Tanium is not configured in a HA Active-Active setup, this is a finding.

✔️ Fix
If the system is not considered mission critical, this is Not Applicable. Work with the Tanium System Administrator to configure Tanium in a HA Active-Active setup based on the process outlined in the Tanium documentation found at https://docs.tanium.com/platform_install/platform_install/installing_an_ha_active_active_cluster.html.