| V-254874 | | 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 allow... |
| V-254875 | | 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 allow... |
| V-254876 | | The Tanium Application Server console must be configured to initiate a session lock after a 15-minute period of inactivity. | The Tanium Console, when multifactor authentication is enabled, will initiate a session lock based upon the ActivClient or other Smart Card software.
... |
| V-254877 | | The Tanium Server must be set to only allow connections from endpoints when TLS is used. | Without cryptographic integrity protections in the Tanium Client, information could be altered by unauthorized users without detection.
Cryptographic... |
| V-254878 | | 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 ... |
| V-254879 | | 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 ... |
| V-254880 | | 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 ... |
| V-254881 | | The Tanium Application Server must be configured to only use LDAP for account management functions. | Enterprise environments make application account management challenging and complex. A manual process for account management functions adds the risk o... |
| V-254882 | | 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 desk... |
| V-254883 | | Documentation identifying Tanium console users, their respective User Groups, Computer Groups, and Roles must be maintained. | System access must be reviewed periodically to verify all Tanium users are assigned the appropriate functional role, with the least privileged access ... |
| V-254884 | | The Tanium application must be configured to use Tanium User Groups in a manner consistent with the model outlined within the environment's system documentation. | It is important for information system owners to document authorized user groups for the Tanium application to avoid unauthorized access to systems. M... |
| V-254885 | | Documentation identifying Tanium console users and their respective Computer Group rights must be maintained. | System access must be reviewed periodically to verify all Tanium users are assigned the appropriate computer groups, with the least privileged access ... |
| V-254886 | | The Tanium Action Approval feature must be enabled for two-person integrity when deploying actions to endpoints. | The Tanium Action Approval feature provides a two-person integrity control mechanism designed to achieve a high-level of security and reduce the possi... |
| V-254887 | | The Tanium documentation identifying recognized and trusted IOC streams must be maintained. | Using trusted and recognized IOC sources may detect and prevent systems from becoming compromised. An IOC stream is a series or stream of IOCs that ar... |
| V-254888 | | Tanium Threat Response must be configured to receive IOC streams only from trusted sources. | Using trusted and recognized IOC sources may detect and prevent systems from becoming compromised. An IOC stream is a series or stream of intel that i... |
| V-254889 | | The Tanium documentation identifying recognized and trusted folders for Threat Response Local Directory Source must be maintained. | Using trusted and recognized IOC sources may detect and prevent systems from becoming compromised. An IOC stream is a series or stream of IOCs that ar... |
| V-254891 | | The Tanium documentation identifying recognized and trusted SCAP sources must be maintained. | NIST validated SCAP XML documents are provided from several possible sources such as DISA, NIST, and the other nongovernment entities. These documents... |
| V-254892 | | 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/third-party paid reposit... |
| V-254893 | | Tanium Comply must be configured to receive SCAP content only from trusted sources. | NIST-validated SCAP XML documents are provided from several possible sources such as DISA, NIST, and the other nongovernment entities. These documents... |
| V-254894 | | 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/third party paid reposit... |
| V-254895 | | 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 not... |
| V-254896 | | The publicly accessible Tanium application must 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. | Display of a standardized and approved use notification before granting access to the publicly accessible application ensures privacy and security not... |
| V-254897 | | Multifactor authentication must be enabled and enforced on the Tanium Server for all access and all accounts. | To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and... |
| V-254898 | | The Tanium application 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 notificatio... |
| V-254899 | | The Tanium application must be configured to send audit records from multiple components within the system to a central location for review and analysis of audit records. | Successful incident response and auditing relies on timely, accurate system information and analysis to allow the organization to identify and respond... |
| V-254900 | | The Tanium applications must provide the capability to filter audit records for events of interest based upon organization-defined criteria. | The ability to specify the event criteria of interest provides the persons reviewing the logs with the ability to quickly isolate and identify these e... |
| V-254901 | | 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 d... |
| V-254902 | | The Tanium application must prohibit user installation, modification, or deletion of software without explicit privileged status. | Allowing regular users to install, modify, or delete software, without explicit privileges, creates the risk that the application performs in an incon... |
| V-254903 | | The Tanium cryptographic signing capabilities must be enabled on the Tanium Clients to safeguard the authenticity of communications sessions when answering requests from the Tanium Server. | All of Tanium's signing capabilities must be enabled upon install. Tanium supports the cryptographic signing and verification before execution of all ... |
| V-254904 | | The Tanium cryptographic signing capabilities must be enabled on the Tanium Server. | All of Tanium's signing capabilities must be enabled upon install. Tanium supports the cryptographic signing and verification before execution of all ... |
| V-254905 | | 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 comput... |
| V-254906 | | 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 comput... |
| V-254907 | | 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 com... |
| V-254908 | | The Tanium Application 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. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-254909 | | The Tanium endpoint must have the Tanium Servers public key in its installation. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access is access to DOD nonpu... |
| V-254910 | | The Tanium application must enforce a minimum 15-character password length. | The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexit... |
| V-254912 | | Tanium must enforce 24 hours/one day as the minimum password lifetime. | Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement.... |
| V-254913 | | The Tanium application must enforce a 60-day maximum password lifetime restriction. | Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals.
One method of minimiz... |
| V-254914 | | 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. | Restricting this setting limits the user's ability to change their password. Passwords need to be changed at specific policy based intervals; however,... |
| V-254915 | | The Tanium application must be configured for LDAP user/group synchronization to map the authenticated identity to the individual user or group account for PKI-based authentication. | Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will n... |
| V-254916 | | The Tanium application must uniquely identify and authenticate nonorganizational users (or processes acting on behalf of nonorganizational users). | Lack of authentication and identification enables nonorganizational users to gain access to the application or possibly other information systems and ... |
| V-254917 | | The Tanium application must separate user functionality (including user interface services) from information system management functionality. | Application management functionality includes functions necessary for administration and requires privileged user access. Allowing nonprivileged users... |
| V-254918 | | The Tanium Server and Client applications must have logging enabled. | 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 s... |
| V-254919 | | The Tanium application must restrict the ability of individuals to use information systems to launch organization-defined denial-of-service (DoS) attacks against other information systems. | The Tanium Action Approval feature provides a two-person integrity control mechanism designed to achieve a high-level of security and reduce the possi... |
| V-254920 | | The Tanium application must manage bandwidth throttles to limit the effects of information flooding types of Denial of Service (DoS) attacks. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or m... |
| V-254921 | | The Tanium application must reveal error messages only to the ISSO, ISSM, and SA. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-254923 | | Tanium must notify system administrator (SA) and the information system security officer (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 ... |
| V-254924 | | Tanium must notify system administrators (SAs) and the information system security officer (ISSO) when accounts are modified. | When application accounts are modified, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the ... |
| V-254925 | | Tanium must notify system administrators (SAs) and the information system security officer (ISSO) for account disabling actions. | When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the ... |
| V-254926 | | Tanium must notify system administrators (SAs) and the information system security officer (ISSO) for account removal actions. | When application accounts are removed, user accessibility is affected. Accounts are utilized for identifying users or for identifying the application ... |
| V-254927 | | The Tanium application 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 applicat... |
| V-254928 | | The Tanium Application Server must be configured with a connector to sync to 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. Accoun... |
| V-254929 | | Tanium must notify the system administrator (SA) and information system security officer (ISSO) of account enabling actions. | Once an attacker establishes access to an application, the attacker often attempts to create a persistent method of re-establishing access. One way to... |
| V-254930 | | 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 SYSTE... |
| V-254931 | | 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 Serv... |
| V-254932 | | 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 prote... |
| V-254933 | | The Tanium application must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | To ensure applications have a sufficient storage capacity in which to write the audit logs, applications need to be able to allocate audit record stor... |
| V-254934 | | The Tanium application must offload audit records onto a different system or media than the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-254935 | | The Tanium application 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 e... |
| V-254936 | | The Tanium application must provide an immediate real-time alert to the system administrator (SA) and information system security officer (ISSO), at a minimum, of all audit failure events requiring real-time alerts. | 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 a real-time aler... |
| V-254938 | | The Tanium application must prohibit user installation of software without explicit privileged status. | Allowing regular users to install software without explicit privileges creates the risk that untested or potentially malicious software will be instal... |
| V-254939 | | The application must enforce access restrictions associated with changes to application configuration. | Failure to provide logical access restrictions associated with changes to application configuration may have significant effects on the overall securi... |
| V-254942 | | 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 commu... |
| V-254943 | | 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 commu... |
| V-254944 | | Firewall rules must be configured on the Tanium Server for Server-to-Zone Server communications. | If using the Tanium Zone Server to proxy traffic from Tanium-managed computers on less trusted network segments to the Tanium Server on the core netwo... |
| V-254945 | | 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 utilizing encryption to protect data. The application must implement cryptogr... |
| V-254946 | | 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 utilizing encryption to protect data. The application must implement cryptogr... |
| V-254947 | | 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 ... |
| V-254948 | | The Tanium application 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 m... |
| V-254949 | | The Tanium application 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 discovere... |
| V-254950 | | Tanium must alert the ISSO, ISSM, and other individuals designated by the local organization when the following Indicators of Compromise (IOCs) or potential compromise are detected: real time intrusion detection; threats identified by authoritative sources (e.g., CTOs); and Category I, II, IV, and VII incidents in accordance with CJCSM 6510.01B. | When a security event occurs, the application that has detected the event must immediately notify the appropriate support personnel so they can respon... |
| V-254951 | | The application must, at a minimum, offload interconnected systems in real time and offload standalone systems weekly. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-254952 | | Tanium Client processes must be excluded from on-access scan. | Similar to any other host-based applications, the Tanium Client is subject to the restrictions other system-level software may place on an operating e... |
| V-254953 | | Tanium Client directory and subsequent files must be excluded from on-access scan. | Similar to any other host-based applications, the Tanium Client is subject to the restrictions other system-level software may place on an operating e... |
| V-254954 | | 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 e... |
