Documentation identifying Tanium console users and their respective User Roles must be maintained.

From Tanium 7.0 Security Technical Implementation Guide

Associated with: CCI-000213

SV-93313r1_rule Documentation identifying Tanium console users and their respective User Roles must be maintained.

Vulnerability discussion

System access should be reviewed periodically to verify that all Tanium users are assigned the appropriate role, with the least privileged access possible to perform assigned tasks being the recommended best practice. Users who have been removed from the documentation should no longer be configured as a Tanium Console User. Consider removing users that have not logged onto the system within a predetermined time frame.When using Active Directory synchronization, as is required by this STIG, User Roles assignments are via the AD Sync connector. AD security groups correlate, one to one, to Tanium User Roles.To change a Tanium user's User Role, their Active Directory account needs to be moved to the AD security group that correlates with the applicable User Role.

Check content

Consult with the Tanium System Administrator to review the documented list of Tanium users. The users' respective, approved roles, as well as the correlated Active Directory security group for the User Roles, must be documented. If the site does not have the Tanium users and their respective, approved roles and AD security groups documented, this is a finding.

Fix text

Prepare and maintain documentation identifying the Tanium console users and their respective User Roles and AD security groups.

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.