Access to Tanium logs on each endpoint must be restricted by permissions.

From Tanium 6.5 Security Technical Implementation Guide

Associated with: CCI-000163

SV-81463r1_rule Access to Tanium logs on each endpoint must be restricted by permissions.

Vulnerability discussion

For the Tanium Client software to run without impact from external negligent or malicious changes, the permissions on the Tanium log files and their directory must be restricted.Tanium is deployed with a Client Hardening Solution. This solution, when applied, will ensure directory permissions are in place.

Check content

Fix text

Using a web browser on a system that has connectivity to the Tanium Server, access the Tanium Server web user interface (UI) and log on with CAC. On the Dashboard, select "Client Hardening Tool". Select the "Set Client Directory Permissions". Tanium will parse the script and return a row for "Restricted" and a row for "Not Restricted", with their respective client counts. Click on the "Not Restricted" row and right-click. Select "Deploy Action". In the "Deploy Action" dialog box, the package "Client Service Hardening - Set SYSTEM only permissions on Tanium Client directory" will be selected. The clients which have their Tanium Client directory "Not Restricted" will be displayed in the bottom window. Click on "Target & Schedule". Choose a schedule to deploy the hardening. Click on "Finish". Verify settings and click on "Confirm".

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.