| Finding ID |
Severity |
Title |
Description |
|
V-253877
|
High |
The SSLCipherSuite registry value must be set. |
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 applications that are either distributed or can allow access to data nonlocally. Use of this requirement will be limited to situations where... |
|
V-253876
|
High |
The SchUseStrongCrypto registry value must be set. |
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 applications that are either distributed or can allow access to data nonlocally. Use of this requirement will be limited to situations where... |
|
V-253875
|
High |
The Tanium Application, SQL, and Module servers must all be configured to communicate using TLS 1.2 Strict Only. |
Disabling feedback to senders when there is a failure in protocol validation format prevents adversaries from obtaining information that would otherwise be unavailable. |
|
V-253821
|
High |
Multifactor authentication must be enabled on the Tanium Server for network access with privileged accounts. |
The Tanium application must be configured to use multifactor authentication. Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased.
Multifactor authentication requires using two or more factors to achieve authentication.
Factors include:
1. Something a user knows (e.g., password/PIN);
2. Something a user... |
|
V-253874
|
Medium |
The Tanium application service must be protected from being stopped by a nonprivileged user. |
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 applications to mitigate the impact of DoS attacks that have occurred or... |
|
V-253873
|
Medium |
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 application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can ensure sessions that are not closed when the user... |
|
V-253872
|
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, intrusion prevention system (IPS), encryption, or other security and management stack software may disallow the Tanium Server from working as expected.
For more information, refer to... |
|
V-253871
|
Medium |
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 must operate at degraded capacity.
This requirement addresses the configuration of applications to mitigate the impact of DoS attacks that have occurred or are ongoing on... |
|
V-253870
|
Medium |
Tanium Comply must be configured to receive Open Vulnerability and Assessment Language (OVAL) feeds only from trusted sources. |
OVAL XML documents are provided from several possible sources such as the Community Intercomparison Suite (CIS) open-source repository and vendor/third-party paid repositories. These documents are used to automate the passive validation of vulnerabilities on systems and therefore require a reasonable level of confidence in their origin. Nonapproved OVAL definitions lead... |
|
V-253869
|
Medium |
Tanium Comply must be configured to receive Security Content Automation Protocol (SCAP) content only from trusted sources. |
SCAP XML documents validated by the National Institute of Standards and Technology (NIST) are provided from several possible sources such as DISA, NIST, and other nongovernment entities. These documents are used as the basis of compliance definitions leveraged to automate compliance auditing of systems. These documents are updated on different... |
|
V-253868
|
Medium |
The Tanium documentation identifying recognized and trusted Open Vulnerability and Assessment Language (OVAL) feeds must be maintained. |
OVAL XML documents are provided from several possible sources such as the Community Intercomparison Suite (CIS) open-source repository and vendor/third-party paid repositories. These documents are used to automate the passive validation of vulnerabilities on systems and therefore require a reasonable level of confidence in their origin. Nonapproved OVAL definitions lead... |
|
V-253867
|
Medium |
The Tanium documentation identifying recognized and trusted Security Content Automation Protocol (SCAP) sources must be maintained. |
SCAP XML documents validated by the National Institute of Standards and Technology (NIST) are provided from several possible sources such as DISA, NIST, and nongovernment entities. These documents are used as the basis of compliance definitions leveraged to automate compliance auditing of systems. These documents are updated on different frequencies... |
|
V-253866
|
Medium |
The Tanium Threat Response Local Directory Source must be configured to restrict access to only authorized maintainers of threat intel. |
Using trusted and recognized indicator of compromise (IOC) sources may detect and prevent systems from becoming compromised. An IOC stream is a series or stream of intel that is imported from a vendor based on a subscription service or manually downloaded and placed in a folder. Threat Response can be... |
|
V-253865
|
Medium |
The Tanium documentation identifying recognized and trusted folders for Threat Response Local Directory Source must be maintained. |
Using trusted and recognized indicator of compromise (IOC) sources may detect and prevent systems from becoming compromised. 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. Threat Response can be... |
|
V-253864
|
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 denial-of-service attacks.
This requirement may be met via the application or by using information system... |
|
V-253863
|
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 denial-of-service attacks.
This requirement may be met via the application or by using information system,... |
|
V-253862
|
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 assurance they have been tested and validated. |
|
V-253861
|
Medium |
Tanium Server directory and subsequent files must be excluded from On-Access scan. |
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, intrusion prevention system (IPS), encryption, or other security and management stack software may disallow the Tanium Server from working as expected.
For more information, refer to:... |
|
V-253860
|
Medium |
The Tanium Server certificate must be signed by a DoD certificate authority (CA). |
The Tanium Server has the option to use a "self-signed" certificate or a trusted CA signed certificate for SSL connections. During evaluations of Tanium in lab settings, customers often conclude that a "self-signed" certificate is an acceptable risk. However, in production environments it is critical that an SSL certificate signed... |
|
V-253859
|
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 assurance they have been tested and validated. |
|
V-253858
|
Medium |
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 network, the Tanium Zone Server Hub, typically installed to the Tanium Server device, must be able to connect to the Zone Server(s) in the DMZ. This... |
|
V-253857
|
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 Tanium Module Server, access to the system capabilities could... |
|
V-253856
|
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 Tanium Module Server, access to the system capabilities could... |
|
V-253855
|
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 as a consequence of creating the object or via... |
|
V-253854
|
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 as a consequence of creating the object or via... |
|
V-253853
|
Medium |
The Tanium Server http directory and subdirectories 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 as a consequence of creating the object or via... |
|
V-253852
|
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 as a consequence of creating the object or via... |
|
V-253851
|
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. |
Restricting this setting limits the user's ability to change their password. Passwords must be changed at specific policy-based intervals; however, if the application allows the user to immediately and continually change their password, it could be changed repeatedly in a short period of time to defeat the organization's policy regarding... |
|
V-253850
|
Medium |
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 Category Assurance List (CAL) and vulnerability assessments. |
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 ports/protocols on information systems.
Applications are capable of providing a wide variety of functions and services. Some of... |
|
V-253849
|
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. Without proper firewall configurations, proper TCP communications may not take place as necessary... |
|
V-253848
|
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. Without proper firewall configurations, proper TCP communications may not take place as necessary for application functionality. The Tanium environment can perform hundreds or thousands of times... |
|
V-253847
|
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 files are not accessible to nonauthorized functions, the files must be relocated... |
|
V-253846
|
Medium |
The Tanium Server must be configured to allow only 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 software has not been tampered with and that it has been provided by a... |
|
V-253845
|
Medium |
The Tanium cryptographic signing capabilities must be enabled on 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 ability of an attacker to conduct man-in-the-middle (MitM) attacks for remote code execution and precludes... |
|
V-253844
|
Medium |
The Tanium applications must be configured to filter audit records for events of interest based on organization-defined criteria. |
The ability to specify the event criteria that are of interest enables those reviewing the logs to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation. Without this capability, forensic investigations are impeded.
Events of interest can be... |
|
V-253843
|
Medium |
Tanium Threat Response must be configured to receive IOC streams only from trusted sources. |
Using trusted and recognized IOC sources may detect compromise and prevent systems from becoming compromised. An IOC stream is a series or stream of intel that is imported from a vendor based on a subscription service or manually downloaded and placed in a folder. Threat Response can be configured to... |
|
V-253842
|
Medium |
The Tanium documentation identifying recognized and trusted indicator of compromise (IOC) streams must be maintained. |
Using trusted and recognized IOC sources may detect compromise and prevent systems from becoming compromised. 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... |
|
V-253841
|
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 two-person integrity 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 user will require a second Tanium console user with a... |
|
V-253840
|
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 computer's standard output channel. The Tanium Client captures that output and forwards the results... |
|
V-253839
|
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 computer's standard output channel. The Tanium Client captures that output and forwards the results... |
|
V-253838
|
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 computer's standard output channel. The Tanium Client captures that output and forwards the results... |
|
V-253837
|
Medium |
The Tanium Application Server console must be configured to initiate a session lock after a 15-minute period of inactivity. |
When multifactor authentication is enabled, the Tanium Console will initiate a session lock based on the ActivClient or other smartcard software.
By initiating the session lock, the console will be locked and not allow unauthorized access by anyone other than the original user.
Although this setting does not apply when... |
|
V-253836
|
Medium |
Firewall rules must be configured on the Tanium Server for server-to-database communications. |
The Tanium Server can use either a SQL Server relational database management system (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 firewall rules since all... |
|
V-253835
|
Medium |
The Tanium Server installer's account database permissions must be reduced to an appropriate level. |
Creating the "tanium" and "tanium_archive" databases through the Tanium Server installer program or using the database to create SQL scripts requires Sysadmin-level permissions. Once the databases have been created, the Tanium Server services must be configured to execute under an account that holds at least the Database Owner (dbo) role... |
|
V-253834
|
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 Server needs to access the SQL Server database. |
|
V-253833
|
Medium |
The Tanium application database must be dedicated to only the Tanium application. |
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, for example, limiting the types of responses provided to database queries; limiting the number/frequency of database... |
|
V-253832
|
Medium |
The Tanium database(s) 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, for example, limiting the types of responses provided to database queries; limiting the number/frequency of database... |
|
V-253831
|
Medium |
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 a manner inconsistent with its design. Explicit privileges (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceed the rights of a regular user.
Application... |
|
V-253830
|
Medium |
Tanium must notify system administrators 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 processes. Sending notification of account removal events to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that application accessibility... |
|
V-253829
|
Medium |
Tanium must notify system administrators 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 application processes. Sending notification of account disabling events to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that application... |
|
V-253828
|
Medium |
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 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... |
|
V-253827
|
Medium |
Tanium must notify the system administrator 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 reestablishing access. One way to accomplish this is for the attacker to enable a new or disabled account. Sending notification of account enabling events to the system administrator and ISSO is one... |
|
V-253826
|
Medium |
Tanium must notify system administrators 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 application processes. Sending notification of account modification events to the system administrator and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that application... |
|
V-253825
|
Medium |
Tanium must notify system administrator and 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 reestablishing access. One way to accomplish this is for the attacker to create a new account. Notification of account creation is one method for mitigating this risk. A comprehensive account management... |
|
V-253824
|
Medium |
The Tanium application must alert the information system security officer and system administrator (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 operation may be adversely affected.
Audit processing... |
|
V-253823
|
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, policies, regulations, standards, and guidance.
System use notifications are required only for access via logon interfaces with human... |
|
V-253822
|
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 HTTP and SOAP requests on port 443. Without a... |
|
V-253820
|
Medium |
Documentation identifying Tanium console users and their respective Computer Group rights must be maintained. |
System access should be reviewed periodically to verify all Tanium users are assigned the appropriate computer groups, with the least privileged access possible to perform assigned tasks. Users who have been removed from the documentation should no longer be configured as a Tanium Console User. |
|
V-253819
|
Medium |
The Tanium application must be configured to use Tanium User Groups in a manner consistent with the model outlined in 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. Misaligned implementation of User Groups grants excessive access and results in potential compromise of "need-to-know" for information access. |
|
V-253818
|
Medium |
Documentation identifying Tanium console users, their respective User Groups, Computer Groups, and Roles must be maintained. |
System access should be reviewed periodically to verify that all Tanium users are assigned the appropriate functional role, with the least privileged access possible to perform assigned tasks being the recommended best practice to avoid unauthorized access. |
|
V-253817
|
Medium |
Tanium Computer Groups must be used to restrict console users from effecting 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 server.
For large sites, it is crucial to have the Computer... |
|
V-253816
|
Medium |
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 of a potential oversight or other error.
To reduce risk, the Tanium application must be configured to allow for LDAP to provide account management functions that immediately enforce the organization's current... |
|
V-253815
|
Medium |
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. Account management will be under the operational responsibility of the system administrator for the Windows Operating System Active Directory.
Satisfies: SRG-APP-000317 |
|
V-253814
|
Medium |
The Tanium application must retain the session lock until the user reestablishes access using established identification and authentication procedures. |
Unattended systems are susceptible to unauthorized use and should be locked when unattended. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the system. |
|
V-253813
|
Medium |
Tanium endpoint files must be excluded from host-based intrusion prevention system (HIPS) 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, intrusion prevention system (IPS), encryption, or other security and management stack software may disallow the Tanium Server from working as expected.
For more information, refer to... |
|
V-253812
|
Medium |
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 environment. Antivirus, intrusion prevention system (IPS), encryption, or other security and management stack software may disallow the Client from working as expected.
For more information, refer to https://docs.tanium.com/platform_deployment_reference/platform_deployment_reference/security_exceptions.html?Highlight=exclusion. |
|
V-253811
|
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. |
|
V-253810
|
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 displayed in the client's Add/Remove Programs will lessen... |
|
V-253809
|
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 on 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 service. |
|
V-253808
|
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. Without proper firewall configurations, proper TCP communications may not take place as necessary for application functionality.
The Tanium environment can perform hundreds or thousands of times... |
|
V-253807
|
Medium |
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 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 removes the ability of an attacker to conduct man-in-the-middle (MitM) attacks for remote code execution and precludes the modification... |
|
V-253806
|
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 applied, will ensure directory permissions are in place. |
|
V-253805
|
Medium |
The Tanium endpoint must have the Tanium Server's pki.db in its installation. |
Without cryptographic integrity protections in the Tanium Client, information could be altered by unauthorized users without detection.
Cryptographic mechanisms used for protecting the integrity of Tanium communications information include signed hash functions using asymmetric cryptography, enabling distribution of the public key to verify the hash information while maintaining the confidentiality... |
|
V-253804
|
Medium |
The Tanium application must authenticate endpoint devices (servers) before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based. |
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk, such as remote connections.
This requires device-to-device authentication. Information systems must use IEEE 802.1x, Extensible Authentication Protocol... |
|
V-253803
|
Medium |
Tanium Server processes must be excluded from On-Access scan. |
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, intrusion prevention system (IPS), encryption, or other security and management stack software may disallow the Tanium Server from working as expected.
For more information, refer to... |
|
V-253802
|
Medium |
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 respond appropriately.
Alerts may be generated from a variety of sources, including audit records or inputs from malicious code protection mechanisms, intrusion detection, or prevention mechanisms. Alerts may... |
|
V-253801
|
Medium |
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 discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous... |
|
V-253800
|
Medium |
The Tanium application must accept Personal Identity Verification (PIV) credentials from other federal agencies. |
Access may be denied to authorized users if federal agency PIV credentials are not accepted.
PIV credentials are issued by federal agencies and conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 requires federal agencies to continue implementing the requirements specified in HSPD-12 to enable agencywide use... |
|
V-253799
|
Medium |
The Tanium application must electronically verify Personal Identity Verification (PIV) credentials. |
The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.
DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under HSPD 12 and as a primary component of layered protection for national security systems. |
|
V-253798
|
Medium |
The Tanium application must accept Personal Identity Verification (PIV) credentials. |
The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.
DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under HSPD 12 and as a primary component of layered protection for national security systems. |
|
V-253797
|
Medium |
The application must employ a deny-all, permit-by-exception (allowlist) policy to allow the execution of authorized software programs. |
Using an allowlist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.
The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that... |
|
V-253796
|
Medium |
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 security of the system.
When dealing with access restrictions pertaining to change control, any changes to the hardware, software, and/or firmware components of the information system and/or application can have significant... |
|
V-253795
|
Medium |
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 installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceeds the rights of a regular user.
Application functionality will... |
|
V-253794
|
Medium |
The Tanium application must provide an immediate real-time alert to the system administrator and information system security officer, 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 alert, security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.
Alerts provide... |
|
V-253793
|
Medium |
The Tanium application must provide an immediate warning to the system administrator and information system security officer (at a minimum) when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity. |
If security personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. |
|
V-253792
|
Medium |
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 systems with limited audit storage capacity. |
|
V-253791
|
Medium |
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 must be able to allocate audit record storage capacity.
The task of allocating audit record storage capacity is usually performed during initial installation of the application and is closely associated with the database administrator... |
|
V-253789
|
Medium |
The Tanium application must reveal error messages only to the information system security officer (ISSO), information system security manager (ISSM), and system administrator (SA). |
Only authorized personnel must be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the application. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated... |
|
V-253788
|
Medium |
The Tanium application must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. |
Any application providing too much information in error messages risks compromising the data and security of the application and system. The structure and content of error messages must be carefully considered by the organization and development team.
Organizations carefully consider the structure/content of error messages. The extent to which information... |
|
V-253787
|
Medium |
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 must operate at degraded capacity.
In the case of application DoS attacks, care must be taken when designing the application to ensure the application makes the... |
|
V-253786
|
Medium |
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 possibility of error for critical operations and DoS conditions.
When this feature is enabled, an action configured by one Tanium console user will require a second Tanium console... |
|
V-253785
|
Medium |
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 state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system.... |
|
V-253784
|
Medium |
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 to access application management functionality capabilities increases the risk that nonprivileged users may obtain elevated privileges.
The separation of user functionality from information system management functionality is either physical or logical and is accomplished... |
|
V-253783
|
Medium |
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 provides an opportunity for intruders to compromise resources within the application or information system.
Nonorganizational users include all information system users other than organizational users, which includes organizational employees or... |
|
V-253782
|
Medium |
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 not be available for forensic analysis. |
|
V-253781
|
Medium |
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 environment. Antivirus, intrusion prevention system (IPS), encryption, or other security and management stack software may disallow the Client from working as expected.
For more information, refer to https://docs.tanium.com/platform_deployment_reference/platform_deployment_reference/security_exceptions.html?Highlight=exclusion. |
|
V-253780
|
Medium |
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 systems with limited audit storage capacity. |
|
V-253779
|
Medium |
The Tanium application must be configured to send audit records from multiple components within the system to a central location for review and analysis. |
Successful incident response and auditing relies on timely, accurate system information and analysis to allow the organization to identify and respond to potential incidents in a proficient manner. If the application does not provide the ability to centrally review the application logs, forensic analysis is negatively impacted.
Segregation of logging... |
