Tanium 7.0 Security Technical Implementation Guide

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]

Details

Version / Release: V1R2

Published: 2018-07-09

Updated At: 2018-09-23 19:21:51

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-93283r1_rule TANS-CL-000001 CCI-000778 MEDIUM The Tanium endpoint must have the Tanium Servers public key in its installation, which will allow it to authenticate and uniquely identify all network-connected endpoint devices before establishing any connection. Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Without authenticatin
    SV-93285r1_rule TANS-CL-000002 CCI-000163 MEDIUM Access to Tanium logs on each endpoint must be restricted by permissions. 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 ap
    SV-93287r1_rule TANS-CL-000003 CCI-001184 MEDIUM The Tanium cryptographic signing capabilities must be enabled on the Tanium Clients, which will ensure the authenticity of communications sessions when answering requests from the Tanium Server. All of Tanium's signing capabilities should be enabled upon install. Tanium supports the cryptographic signing and verification before execution of all Sensors, Questions, Actions, Sensor Libraries, File Shards, etc. Enabling signing does away with the ab
    SV-93289r1_rule TANS-CL-000004 CCI-000382 MEDIUM Firewall rules must be configured on the Tanium Endpoints for Client-to-Server communications. In addition to the client-to-server TCP communication that takes place over port 17472, Tanium Clients also communicate to other Tanium-managed computers over port 17472. The Tanium environment can perform hundreds or thousands of times faster than other
    SV-93291r1_rule TANS-CL-000005 CCI-002165 MEDIUM Control of the Tanium Client service must be restricted to SYSTEM access only for all managed clients. The reliability of the Tanium client's ability to operate depends upon controlling access to the Tanium client service. By restricting access to SYSTEM access only, the non-Tanium system administrator will not have the ability to impact operability of the
    SV-93293r1_rule TANS-CL-000006 CCI-002165 MEDIUM The ability to uninstall the Tanium Client service must be disabled on all managed clients. By default, end users have the ability to uninstall software on their clients. In the event the Tanium Client software is uninstalled, the Tanium Server is unable to manage the client and must redeploy to the client. Preventing the software from being dis
    SV-93295r1_rule TANS-CL-000007 CCI-002165 MEDIUM The permissions on the Tanium Client directory must be restricted to only the SYSTEM account on all managed clients. By restricting access to the Tanium Client directory on managed clients, the Tanium client's ability to operate and function as designed will be protected from malicious attack and unintentional modifications by end users.
    SV-93297r1_rule TANS-CL-000008 CCI-000366 MEDIUM Tanium endpoint files must be excluded from on-access antivirus actions. Similar to any other host-based applications, the Tanium Client is subject to the restrictions other System-level software may place on an operating environment. That is to say that Antivirus, IPS, Encryption, or other security and management stack softwa
    SV-93299r1_rule TANS-CL-000010 CCI-000366 MEDIUM The Tanium Client Deployment Tool (CDT) must not be configured to use the psexec method of deployment. When using the Tanium Client Deployment Tool (CDT), using psexec represents an increased vulnerability as the NTLM hash and clear text passwords of the authenticating user is exposed in the memory of the remote system. To mitigate this vulnerability, the
    SV-93301r1_rule TANS-CL-000012 CCI-000366 MEDIUM Tanium endpoint files must be protected from file encryption actions. Similar to any other host-based applications, the Tanium Client is subject to the restrictions other System-level software may place on an operating environment. That is to say that Antivirus, Encryption, or other security and management stack software ma
    SV-93303r1_rule TANS-CL-000013 CCI-001094 MEDIUM Tanium must restrict the ability of individuals to place too much impact upon the network, which might result in a denial-of-service (DoS) event on the network by using RandomSensorDelayInSeconds. DoS is a condition where a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. Individuals of concern can include hostile insiders or external adver
    SV-93305r1_rule TANS-CL-000014 CCI-000366 MEDIUM Tanium endpoint files must be excluded from host-based intrusion prevention intervention. Similar to any other host-based applications, the Tanium Client is subject to the restrictions other System-level software may place on an operating environment. Antivirus, IPS, Encryption, or other security and management stack software may disallow the
    SV-93307r1_rule TANS-CN-000002 CCI-000015 MEDIUM The Tanium Server must be configured with a connector to sync to Microsoft Active Directory for account management functions, must isolate security functions from non-security functions, and must terminate shared/group account credentials when members leave the group. By restricting access to the Tanium Server to only Microsoft Active Directory, user accounts and related permissions can be strictly monitored. Account management will be under the operational responsibility of the System Administrator for the Windows Ope
    SV-93309r1_rule TANS-CN-000003 CCI-000015 MEDIUM The Tanium Server must be configured to only use Microsoft Active Directory for account management functions. By restricting access to the Tanium Server to only Microsoft Active Directory, user accounts and related permissions can be strictly monitored. Account management will be under the operational responsibility of the System Administrator for the Windows Ope
    SV-93311r1_rule TANS-CN-000004 CCI-000213 MEDIUM Tanium Computer Groups must be used to restrict console users from affecting changes to unauthorized computers. Computer Groups allow a site running Tanium to assign responsibility of specific Computer Groups to specific Tanium console users. By doing so, a desktop administrator, for example, will not have the ability to enforce an action against a high visibility
    SV-93313r1_rule TANS-CN-000005 CCI-000213 MEDIUM Documentation identifying Tanium console users and their respective User Roles must be maintained. 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
    SV-93315r1_rule TANS-CN-000006 CCI-000213 HIGH Role-based system access must be configured to least privileged access to Tanium Server functions through the Tanium interface. User accessibility to various Tanium Server functions performed via the console can be restricted by User Roles. Those User Roles are: Administrator, Read Only User, Question Author, Action User, Action Approver, Action Author, Sensor Author, Action/Senso
    SV-93317r1_rule TANS-CN-000007 CCI-000213 MEDIUM Tanium console users User Roles must be validated against the documentation for User Roles. 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
    SV-93319r1_rule TANS-CN-000008 CCI-000213 MEDIUM Documentation identifying Tanium console users and their respective Computer Group rights must be maintained. 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
    SV-93321r1_rule TANS-CN-000009 CCI-000213 MEDIUM Tanium console users Computer Group rights must be validated against the documentation for Computer Group rights. 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
    SV-93323r1_rule TANS-CN-000010 CCI-000765 HIGH Common Access Card (CAC)-based authentication must be enforced and enabled on the Tanium Server for network and local access with privileged and non-privileged accounts. To assure 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 orga
    SV-93325r1_rule TANS-CN-000014 CCI-001762 MEDIUM Firewall rules must be configured on the Tanium Server for Console-to-Server communications. An HTML5 based application, the Tanium Console runs from any device with a browser that supports HTML5. For security, the HTTP and SOAP communication to the Tanium Server is SSL encrypted, so the Tanium Server installer configures the server to listen for
    SV-93327r1_rule TANS-CN-000015 CCI-001384 MEDIUM The publicly accessible Tanium application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application. Display of a standardized and approved use notification before granting access to the publicly accessible application ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policie
    SV-93329r1_rule TANS-CN-000016 CCI-000139 MEDIUM Tanium must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability and system opera
    SV-93331r1_rule TANS-CN-000018 CCI-001233 MEDIUM Flaw remediation Tanium applications must employ automated mechanisms to determine the state of information system components with regard to flaw remediation using the following frequency: continuously, where HBSS is used; 30 days, for any additional internal network scans not covered by HBSS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP). Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the system components may remain vulnerable to the exploits presented by undetected software flaws. To support this requirement, the flaw remediatio
    SV-93333r1_rule TANS-CN-000019 CCI-001683 MEDIUM Tanium must notify system administrators and ISSO when accounts are created. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Notification of account creation i
    SV-93335r1_rule TANS-CN-000020 CCI-001684 MEDIUM Tanium must notify system administrators and ISSO when accounts are modified. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply modify an existing account. Notification of account modi
    SV-93337r1_rule TANS-CN-000021 CCI-002132 MEDIUM Tanium must notify the SA and ISSO of account enabling actions. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of accoun
    SV-93339r1_rule TANS-CN-000022 CCI-001855 MEDIUM Tanium must provide an immediate warning to the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of repository maximum audit record storage capacity. If security personnel are not notified immediately upon storage volume utilization reaching 75 percent, they are unable to plan for storage capacity expansion.
    SV-93341r1_rule TANS-CN-000027 CCI-000056 MEDIUM Common Access Card (CAC)-based authentication must be enabled and enforced on the Tanium Server for all access and all accounts. To assure 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 orga
    SV-93343r1_rule TANS-CN-000032 CCI-001685 MEDIUM Tanium must notify System Administrators and Information System Security Officers for account disabling actions. When application accounts are disabled, user accessibility is affected. Accounts are used for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user acce
    SV-93345r1_rule TANS-CN-000033 CCI-001686 MEDIUM Tanium must notify System Administrators and Information System Security Officers for account removal actions. When application accounts are removed, user accessibility is affected. Accounts are used for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user acces
    SV-93347r1_rule TANS-CN-000036 CCI-001812 MEDIUM Tanium must prohibit user installation of software without explicit privileged status and enforce access restrictions associated with changes to application configuration. Allowing regular users to install software without explicit privileges creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular user
    SV-93349r1_rule TANS-CN-000037 CCI-000154 MEDIUM Tanium must provide the capability to centrally review and analyze audit records from multiple components within the system. Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the application does not provide the ability
    SV-93351r1_rule TANS-DB-000001 CCI-002346 MEDIUM The Tanium SQL database must be installed on a separate system. Failure to protect organizational information from data mining may result in a compromise of information. Data storage objects include, for example, databases, database records, and database fields. Data mining prevention and detection techniques include
    SV-93353r1_rule TANS-DB-000002 CCI-002346 MEDIUM The Tanium SQL server must be dedicated to the Tanium database. Failure to protect organizational information from data mining may result in a compromise of information. Data storage objects include, for example, databases, database records, and database fields. Data mining prevention and detection techniques include
    SV-93355r1_rule TANS-DB-000003 CCI-001814 MEDIUM The access to the Tanium SQL database must be restricted. Only the designated database administrator(s) can have elevated privileges to the Tanium SQL database. After the Tanium Server has been installed and the Tanium databases created, only the Tanium Receiver, Tanium Module, and Tanium connection manager (ad sync) service needs to access the SQL Server database.
    SV-93357r1_rule TANS-DB-000004 CCI-001814 MEDIUM The Tanium Server installers account SQL database permissions must be reduced from sysadmin to db_owner. Creating the tanium and tanium_archive databases through the Tanium Server installer program or using the database create SQL scripts requires Sysadmin-level permissions. Once the databases have been created, the Tanium Server and Apache services must be
    SV-93359r1_rule TANS-DB-000005 CCI-001762 MEDIUM Firewall rules must be configured on the Tanium Server for Server-to-Database communications. The Tanium Server can use either a SQL Server RDBMS installed locally to the same device as the Tanium Server application or a remote dedicated or shared SQL Server instance. Using a local SQL Server database typically requires no changes to network firew
    SV-93361r1_rule TANS-DB-000006 CCI-002617 MEDIUM SQL stored queries or procedures installed during Tanium installation must be removed from the Tanium Server. Failure to protect organizational information from data mining may result in a compromise of information. Data storage objects include, for example, databases, database records, and database fields. Data mining prevention and detection techniques include
    SV-93363r1_rule TANS-SV-000001 CCI-001184 MEDIUM The Tanium Server must protect the confidentiality and integrity of transmitted information with cryptographic signing capabilities enabled to ensure the authenticity of communications sessions when making requests from Tanium Clients. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. Without authenticating devices, unidentified or unknown devices may be intr
    SV-93365r1_rule TANS-SV-000002 CCI-000057 MEDIUM The Tanium Server console must be configured to initiate a session lock after a 15-minute period of inactivity. The Tanium Console, when CAC is enabled, will initiate a session lock based upon the ActivClient or other Smart Card software. By initiating the session lock, the console will be locked and not allow unauthorized access by anyone other than the original
    SV-93367r1_rule TANS-SV-000003 CCI-001453 MEDIUM Tanium Trusted Content providers must be documented. 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 co
    SV-93369r1_rule TANS-SV-000004 CCI-001453 MEDIUM Content providers must provide their public key to the Tanium administrator to import for validating signed content. 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 co
    SV-93371r1_rule TANS-SV-000005 CCI-001453 MEDIUM Tanium public keys of content providers must be validated against documented trusted content providers. 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 co
    SV-93373r1_rule TANS-SV-000006 CCI-000213 MEDIUM The Tanium Action Approval feature must be enabled for two person integrity when deploying actions to endpoints. The Tanium Action Approval feature provides a "four eyes" control mechanism designed to achieve a high level of security and reduce the possibility of error for critical operations. When this feature is enabled, an action configured by one Tanium console
    SV-93375r1_rule TANS-SV-000007 CCI-001414 MEDIUM The Tanium documentation identifying recognized and trusted IOC Detect streams must be maintained. An IOC stream is a series or "stream" of IOCs that are imported from a vendor based on a subscription service. An IOC stream can be downloaded manually or on a scheduled basis. The items in an IOC stream can be separately manipulated after they are import
    SV-93377r1_rule TANS-SV-000008 CCI-001414 MEDIUM The Tanium IOC Detect must be configured to receive IOC streams only from trusted sources. An IOC stream is a series or "stream" of IOCs that are imported from a vendor based on a subscription service or manually downloaded and placed in a folder. IOC Detect can be configured to retrieve the IOC content on a regularly scheduled basis. The items
    SV-93379r1_rule TANS-SV-000010 CCI-000158 MEDIUM The Tanium Connect module must be configured to forward Tanium IOC Detect events to identified destinations. Indicators of Compromise (IOC) is an artifact that is observed on the network or system that indicates computer intrusion. The Tanium IOC Detect module detects, manages, and analyzes systems against IOCs real-time. The module also responds to those detect
    SV-93381r1_rule TANS-SV-000011 CCI-001493 MEDIUM The Tanium Server must protect audit tools from unauthorized access, modification, or deletion. Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. Applications providing tools to interface with
    SV-93383r1_rule TANS-SV-000015 CCI-001749 MEDIUM The Tanium Server must be configured to only allow signed content to be imported. Changes to any software components can have significant effects on the overall security of the application. Verifying software components have been digitally signed using a certificate that is recognized and approved by the organization ensures the softwa
    SV-93385r2_rule TANS-SV-000016 CCI-001499 MEDIUM All installation files originally downloaded to the Tanium Server must be configured to download to a location other than the Tanium Server directory. Typically, the Tanium Server stores the Package Source Files that it downloads from the Internet and server shares or files uploaded through the Tanium Console in a subdirectory of the server's installation directory called Downloads. To ensure package fi
    SV-93387r1_rule TANS-SV-000017 CCI-000382 MEDIUM Firewall rules must be configured on the Tanium Server for Client-to-Server communications. In addition to the client-to-server TCP communication that takes place over port 17472, Tanium Clients also communicate to other Tanium-managed computers over port 17472. The Tanium environment can perform hundreds or thousands of times faster than other
    SV-93389r1_rule TANS-SV-000018 CCI-000382 MEDIUM Firewall rules must be configured on the Tanium Zone Server for Client-to-Zone Server communications. In customer environments using the Tanium Zone Server, a Tanium Client may be configured to point to a Zone Server instead of a Tanium Server. The communication requirements for these Clients are identical to the Server-to-Client requirements. https://do
    SV-93391r1_rule TANS-SV-000019 CCI-000382 MEDIUM The Tanium Server must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical po
    SV-93393r1_rule TANS-SV-000020 CCI-000185 MEDIUM 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. 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 co
    SV-93395r1_rule TANS-SV-000021 CCI-000186 HIGH The Tanium Server certificate and private/public keys directory must be protected with appropriate permissions. If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the privat
    SV-93397r1_rule TANS-SV-000023 CCI-001082 MEDIUM The Tanium Module server must be installed on a separate system. Unauthorized access to the Tanium Server is protected by disabling the Module Server service on the Tanium Server and by configuring the Module Server on a separate system. When X509 smartcard certificates (CAC or PIV tokens) are used for access to the T
    SV-93399r1_rule TANS-SV-000024 CCI-002165 MEDIUM The Tanium Server directory must be restricted with appropriate permissions. Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired
    SV-93401r1_rule TANS-SV-000025 CCI-002165 MEDIUM The Tanium Server http directory and sub-directories must be restricted with appropriate permissions. Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired
    SV-93403r1_rule TANS-SV-000026 CCI-002165 MEDIUM The permissions on the Tanium Server registry keys must be restricted to only the Tanium service account and the [Tanium Admins] group. Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired
    SV-93405r1_rule TANS-SV-000027 CCI-002165 MEDIUM The Tanium Server Logs and TDL_Logs directories must be restricted with appropriate permissions. Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired
    SV-93407r1_rule TANS-SV-000028 CCI-002235 MEDIUM All Active Directory accounts synchronized with Tanium for non-privileged functions must be non-privileged domain accounts. Tanium has the ability to synchronize with Active Directory for Tanium account management. Tanium advises that all replicated accounts for non-privileged level functions should be non-privileged domain accounts. In doing so, should a vulnerability in the
    SV-93409r1_rule TANS-SV-000029 CCI-001851 MEDIUM A Tanium connector must be configured to send log data to an external audit log reduction-capable system and provide alerts. While the Tanium Server records audit log entries to the Tanium SQL database, retrieval and aggregation of log data through the Tanium console is not efficient. The Tanium Connect module allows for SIEM connectors in order to facilitate forensic data ret
    SV-93411r1_rule TANS-SV-000030 CCI-001811 MEDIUM File integrity monitoring of critical executables that Tanium uses must be configured. Tanium inherently watches files and their respective hash values for change but while Tanium can do file integrity checks of critical executables, it is important to conduct File Integrity Monitoring (FIM) via an outside service such as Host Based Securit
    SV-93413r1_rule TANS-SV-000031 CCI-001762 MEDIUM Firewall rules must be configured on the Tanium module server to allow Server-to-Module Server communications from the Tanium Server. The Tanium Module Server is used to extend the functionality of Tanium through the use of various workbenches. The Tanium Module Server requires communication with the Tanium Server on port 17477. Without a proper connection from the Tanium Server to the
    SV-93415r1_rule TANS-SV-000032 CCI-001762 MEDIUM Firewall rules must be configured on the Tanium Server for Server-to-Module Server communications. The Tanium Module Server is used to extend the functionality of Tanium through the use of various workbenches. The Tanium Module Server requires communication with the Tanium Server on port 17477. Without a proper connection from the Tanium Server to the
    SV-93417r1_rule TANS-SV-000033 CCI-001762 MEDIUM Firewall rules must be configured on the Tanium Server for Server-to-Zone Server communications. If you are using the Tanium Zone Server to proxy traffic from Tanium-managed computers on less trusted network segments to the Tanium Server on the core network, then the Tanium Zone Server Hub, typically installed to the Tanium Server device, must be abl
    SV-93419r1_rule TANS-SV-000035 CCI-002450 MEDIUM The SSLHonorCipherOrder must be configured to disable weak encryption algorithms on the Tanium Server. Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assuran
    SV-93421r1_rule TANS-SV-000036 CCI-002470 MEDIUM The Tanium Server certificate must be signed by a DoD Certificate Authority. The Tanium Server has the option to use a "self-signed" certificate or a Trusted Certificate Authority signed certificate for SSL connections. During evaluations of Tanium in Lab settings, customers often conclude that a "self-signed" certificate is an ac
    SV-93423r1_rule TANS-SV-000037 CCI-002422 MEDIUM Any Tanium configured EMAIL RESULTS connectors must be configured to enable TLS/SSL to encrypt communications. Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures
    SV-93425r1_rule TANS-SV-000040 CCI-000366 MEDIUM Tanium Server files must be excluded from on-access antivirus actions. Similar to any other host-based applications, the Tanium Server is subject to the restrictions other System-level software may place on an operating environment. Antivirus, IPS, Encryption, or other security and management stack software may disallow the
    SV-93427r1_rule TANS-SV-000041 CCI-000048 MEDIUM The Tanium Server console must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to The Tanium Server. Display of the DoD-approved use notification before granting access to the application ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and
    SV-93429r1_rule TANS-SV-000042 CCI-000050 MEDIUM The Tanium Server console must be configured to retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access. The banner must be acknowledged by the user prior to allowing the user access to the application. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD
    SV-93431r1_rule TANS-SV-000043 CCI-000366 MEDIUM Tanium Server files must be protected from file encryption actions. Similar to any other host-based applications, the Tanium Server is subject to the restrictions other System-level software may place on an operating environment. Antivirus, Encryption, or other security and management stack software may disallow the Taniu
    SV-93433r1_rule TANS-SV-000045 CCI-000054 MEDIUM The Tanium max_soap_sessions_total setting must be explicitly enabled to limit the number of simultaneous sessions. Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to DoS attacks. This requirement may
    SV-93435r1_rule TANS-SV-000046 CCI-000054 MEDIUM The Tanium max_soap_sessions_per_user setting must be explicitly enabled to limit the number of simultaneous sessions. Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to DoS attacks. This requirement may
    SV-93437r1_rule TANS-SV-000048 CCI-001414 MEDIUM The Tanium documentation identifying recognized and trusted folders for IOC Detect Folder streams must be maintained. An IOC stream is a series or "stream" of IOCs that are imported from a vendor based on a subscription service or manually downloaded and placed in a folder. IOC Detect can be configured to retrieve the IOC content on a regularly scheduled basis. The items
    SV-93439r1_rule TANS-SV-000049 CCI-001414 MEDIUM The Tanium IOC Detect Folder streams must be configured to restrict access to only authorized maintainers of IOCs. An IOC stream is a series or "stream" of IOCs that are imported from a vendor based on a subscription service or manually downloaded and placed in a folder. IOC Detect can be configured to retrieve the IOC content on a regularly scheduled basis. The items
    SV-93441r1_rule TANS-SV-000050 CCI-001414 MEDIUM The Tanium documentation identifying recognized and trusted SCAP feeds must be maintained. NIST validated SCAP XML documents are provided from several possible sources such as DISA, NIST, and the other non-government entities. These documents are used as the basis of compliance definitions leveraged to automate compliance auditing of systems. T
    SV-93443r1_rule TANS-SV-000051 CCI-001414 MEDIUM The Tanium documentation identifying recognized and trusted OVAL feeds must be maintained. OVAL XML documents are provided from several possible sources such as the CIS open source repository, or any number of vendor/3rd party paid repositories. These documents are used to automate the passive validation of vulnerabilities on systems and theref
    SV-93445r1_rule TANS-SV-000052 CCI-001414 MEDIUM Tanium Comply must be configured to receive SCAP feeds only from trusted sources. NIST-validated SCAP XML documents are provided from several possible sources such as DISA, NIST, and the other non-government entities. These documents are used as the basis of compliance definitions leveraged to automate compliance auditing of systems. T
    SV-93447r1_rule TANS-SV-000053 CCI-001414 MEDIUM Tanium Comply must be configured to receive OVAL feeds only from trusted sources. OVAL XML documents are provided from several possible sources such as the CIS open source repository, or any number of vendor/3rd party paid repositories. These documents are used to automate the passive validation of vulnerabilities on systems and theref
    SV-93449r1_rule TANS-SV-000054 CCI-001665 MEDIUM Tanium must be configured in a High-Availability (HA) setup to ensure minimal loss of data and minimal disruption to mission processes in the event of a system failure. Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the
    SV-93451r1_rule TANS-SV-000055 CCI-001095 MEDIUM The bandwidth consumption for the Tanium Server must be limited. DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. In the case of application DoS attacks, care must be taken when design
    SV-93453r1_rule TANS-SV-000056 CCI-001849 MEDIUM The Tanium SQL Server RDBMS must be configured with sufficient free space to ensure audit logging is not impacted. In order to ensure Tanium has sufficient storage capacity in which to write the audit logs, the SQL Server RDMBS must be configured with sufficient free space. Consult the server sizing documents located at https://docs.tanium.com/platform_install/platfo
    SV-93455r1_rule TANS-SV-000062 CCI-002385 MEDIUM Tanium must limit the bandwidth used in communicating with endpoints to prevent a denial-of-service (DoS) condition at the server. DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of applications to mitiga
    SV-93457r1_rule TANS-SV-000064 CCI-002605 MEDIUM Tanium Server must install security-relevant software updates within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to
    SV-93459r1_rule TANS-SV-000065 CCI-000366 MEDIUM Tanium Server files must be excluded from host-based intrusion prevention intervention. Similar to any other host-based applications, the Tanium Server is subject to the restrictions other System-level software may place on an operating environment. Antivirus, IPS, Encryption, or other security and management stack software may disallow the
    SV-93461r1_rule TANS-SV-000066 CCI-002361 MEDIUM Tanium must set an absolute timeout for sessions. Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, net
    SV-93463r1_rule TANS-SV-000067 CCI-002361 MEDIUM Tanium must set an inactive timeout for sessions. Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web s
    SV-93465r1_rule TANS-SV-000068 CCI-002385 MEDIUM Tanium service must be protected from being stopped by a non-privileged user. DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of applications to mitiga
    SV-93467r1_rule TANS-SV-000069 CCI-002385 MEDIUM The Tanium web server must be tuned to handle the operational requirements of the hosted application. Denial of service (DoS) is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of ap
    SV-93469r1_rule TANS-SV-000070 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93471r1_rule TANS-SV-000071 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93473r1_rule TANS-SV-000073 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93475r1_rule TANS-SV-000074 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93477r1_rule TANS-SV-000075 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93479r1_rule TANS-SV-000076 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93481r1_rule TANS-SV-000077 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93483r1_rule TANS-SV-000078 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93485r1_rule TANS-SV-000079 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93487r1_rule TANS-SV-000080 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93489r1_rule TANS-SV-000081 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93491r1_rule TANS-SV-000082 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93493r1_rule TANS-SV-000083 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93495r1_rule TANS-SV-000084 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93497r1_rule TANS-SV-000085 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93499r1_rule TANS-SV-000086 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93501r1_rule TANS-SV-000087 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93503r1_rule TANS-SV-000088 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93505r1_rule TANS-SV-000089 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93507r1_rule TANS-SV-000090 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93509r1_rule TANS-SV-000091 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93511r1_rule TANS-SV-000092 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93513r1_rule TANS-SV-000093 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93515r1_rule TANS-SV-000094 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93517r1_rule TANS-SV-000095 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93519r1_rule TANS-SV-000096 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93521r1_rule TANS-SV-000097 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93523r1_rule TANS-SV-000098 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93525r1_rule TANS-SV-000099 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93527r1_rule TANS-SV-000100 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93529r1_rule TANS-SV-000101 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93531r1_rule TANS-SV-000102 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93533r1_rule TANS-SV-000103 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93535r1_rule TANS-SV-000104 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93537r1_rule TANS-SV-000105 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93539r1_rule TANS-SV-000106 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93541r1_rule TANS-SV-000107 CCI-002418 MEDIUM Tanium must be configured to communicate using TLS 1.2 Strict Only. Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requirement applies only to those applications that are either distri
    SV-93543r1_rule TANS-SV-000047 CCI-000054 MEDIUM The Tanium soap_max_keep_alive setting must be explicitly enabled to limit the number of simultaneous sessions. Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to DoS attacks. This requirement may
    SV-93545r1_rule TANS-SV-000044 CCI-002450 MEDIUM The SSLCipherSuite must be configured to disable weak encryption algorithms on the Tanium Server. Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assuran