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.

From Tanium 7.0 Security Technical Implementation Guide

Associated with: CCI-001665

SV-93449r1_rule 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.

Vulnerability discussion

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 content

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 text

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.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.