STIGViewer Support

Multifactor authentication must be enabled and enforced on the Tanium Server for all access and all accounts.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-254897TANS-AP-000195SV-254897r1015861_ruleCCI-000056medium
Description
To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses, except the following. (i) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and (ii) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity. Satisfies: SRG-APP-000080, SRG-APP-000148, SRG-APP-000149, SRG-APP-000150, SRG-APP-000151, SRG-APP-000152, SRG-APP-000156, SRG-APP-000391, SRG-APP-000392, SRG-APP-000402, SRG-APP-000403, SRG-APP-000005, SRG-APP-000004, SRG-APP-000002
STIGDate
Tanium 7.x Application on TanOS Security Technical Implementation Guide2025-02-11

Related Frameworks

16 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (18) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-01.2Authenticate, Authorize and Audit (AAA)
1.00
IAC-02Identification & Authentication for Organizational Users
1.00
IAC-02.2Replay-Resistant Authentication
1.00
IAC-03Identification & Authentication for Non-Organizational Users
1.00
IAC-03.1Acceptance of PIV Credentials from Other Organizations
1.00
IAC-04Identification & Authentication for Devices
1.00
IAC-05Identification & Authentication for Third-Party Technology Assets, Applications and/or Services (TAAS)
1.00
IAC-24.1Pattern-Hiding Displays
1.00
MON-09Non-Repudiation
1.00
IAC-02.3Acceptance of PIV Credentials
0.50

+8 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-11Device Lock
1.00
AC-11(1)Pattern-hiding Displays
1.00
AC-12Session Termination
1.00
AC-12(2)Termination Message
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.10
1.00
3.5.1
1.00
3.5.2
1.00
3.5.3
1.00
3.5.4
1.00
CCI16 mappings

+6 more (top 10 by weight shown)

NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

Who does this work

7 NICE work roles and 5 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-254897r1015861_chk)

1. Access the Tanium Server interactively. 2. Log on to the TanOS console with the "tanadmin" user role. 3. Enter "2" to access the "Tanium Operations" menu. 4. Enter "2" to access the "Tanium Configuration" Settings menu. 5. Enter "1" to access the "Edit Tanium Server Settings" menu. 6. Validate the value for "ForceSOAPSSLClientCert" is set to "1". 7. Validate the following keys exist and are configured: 7A. "ClientCertificateAuthField" For example: X509v3 Subject Alternative Name. 7B. "ClientCertificateAuthRegex" For example: .*:\s(\d+)@.* Note: This regex may vary. 7C. "ClientCertificateAuth" For example: /opt/Tanium/TaniumServer/cac.pem 7D. "TrustedHostList" For example: Append 127.0.0.1 (for IPv4) and [::1] (for IPv6) If the value for "ForceSOAPSSLClientCert" is not set to "1" and the remaining registry values are not configured, this is a finding.

Fix Text (F-58454r986515_fix)

Use the vendor documentation titled "Multi-Factor Authentication" to implement correct configuration settings for this requirement. Vendor documentation can be downloaded from the following URL: https://docs.tanium.com/platform_deployment_reference/platform_deployment_reference/smart_card_authentication.html#cac_Tanium_Appliance 1. Access the Tanium Server interactively. 2. Log on to the TanOS server with the tanadmin user role. 3. Enter "2" to access the "Tanium Operations" menu. 4. Enter "2" to access the "Tanium Configuration" Settings menu. 5. Enter "1" to access the "Edit Tanium Server Settings" menu. 6. Validate the value for "ForceSOAPSSLClientCert" is set to "1". 7. Validate the following keys exist and are configured: 7A. "ClientCertificateAuthField" For example: X509v3 Subject Alternative Name. 7B. "ClientCertificateAuthRegex" For example: .*:\s(\d+)@.* Note: This regex may vary. 7C. "ClientCertificateAuth" For example: /opt/Tanium/TaniumServer/cac.pem Note: The path name is case sensitive. 7D. "TrustedHostList" For example: Append 127.0.0.1 (for IPv4) and [::1] (for IPv6).