Public keys of content providers must be validated against documented trusted content providers.

From Tanium 6.5 Security Technical Implementation Guide

Associated with: CCI-001453

SV-81533r1_rule Public keys of content providers must be validated against documented trusted content providers.

Vulnerability discussion

A Tanium Sensor, also called content, enables an organization to gather real-time inventory, configuration, and compliance data elements from managed computers. Sensors gather specific information from the local device and then write the results to the computer's standard output channel. The Tanium Client captures that output and forwards the results through the platform's unique "ring" architecture for display in the Tanium Console. The language used for Sensor development is based on the scripting engine available on the largest number of devices under management as well as the scripting experience and background of the people who will be responsible for creating new Sensors. VBScript and PowerShell are examples of common scripting languages used for developing sensors.Because errors in scripting can and will provide errant feedback at best and will impact functionality of the endpoint to which the content is directed, it is imperative to ensure content is only accepted from trusted sources.

Check content

Note: If only using Tanium provided content and not accepting content from any other content providers, this is Not Applicable. Access the Tanium Server interactively. Log on with an account with administrative privileges to the server. Open an Explorer window. Navigate to the \Program Files\Tanium\Tanium Server\content_public_keys\content folder. If a public key, other than the default Tanium public key, resides in the content folder and is not documented on the trusted content provider list, this is a finding.

Fix text

Remove the content from Tanium for which a public key is imported into Tanium and which is not documented as a trusted content provider.

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.