The Tanium Server certificates must have Extended Key Usage entries for the serverAuth object TLS Web Server Authentication and the clientAuth object TLS Web Client Authentication.

From Tanium 6.5 Security Technical Implementation Guide

Part of SRG-APP-000175

Associated with: CCI-000185

SV-81573r1_rule The Tanium Server certificates must have Extended Key Usage entries for the serverAuth object TLS Web Server Authentication and the clientAuth object TLS Web Client Authentication.

Vulnerability discussion

Information can be either unintentionally or maliciously disclosed or modified during reception including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.This requirement applies only to those applications that are either distributed or can allow access to data non-locally. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When receiving data, applications need to leverage protection mechanisms, such as TLS, SSL VPNs, or IPSEC.

Check content

Access the Tanium Module server interactively and log on as an Administrator. Navigate to the \Program Files\Tanium\Tanium Server directory. Locate the SOAPServer.crt file and double-click on it to open the certificate. Select the “Details” tab. Scroll down through the details to find and select the “Extended Key Usage” Field. If there is no “Extended Key Usage” field, this is a finding. In the bottom screen, verify "TLS Web Server Authentication" and "TLS Web Client Authentication" are both identified. If "TLS Web Server Authentication" and "TLS Web Client Authentication" are not both identified, this is a finding.

Fix text

Request or regenerate the certificate being used to include both the serverAuth and clientAuth objects.

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.

Powered by sagemincer