| Finding ID |
Severity |
Title |
Description |
|
V-234093
|
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 private key is stolen, this will lead... |
|
V-234056
|
High |
Common Access Card (CAC)-based authentication must be enabled on the Tanium Server for network access with 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 organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of... |
|
V-234052
|
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 functional roles, a combination of User Role(s), and Content Set(s) assigned through User Group membership. Functional roles are assigned to users via Active Directory Group membership.
System access should be reviewed periodically to verify that... |
|
V-234132
|
Medium |
The Tanium application 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 distributed or can allow access to data non-locally. Use of this requirement will be limited to situations... |
|
V-234131
|
Medium |
The Tanium application 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 distributed or can allow access to data non-locally. Use of this requirement will be limited to situations... |
|
V-234130
|
Medium |
The Tanium application, SQL and Module servers must all 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 distributed or can allow access to data non-locally. Use of this requirement will be limited to situations... |
|
V-234129
|
Medium |
The Tanium web server must be tuned to handle the operational requirements of the hosted application. |
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-234128
|
Medium |
The Tanium application 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 mitigate the impact of DoS attacks that have occurred or are ongoing on... |
|
V-234127
|
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 make certain that sessions that are not closed through... |
|
V-234126
|
Medium |
The Tanium application 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, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses... |
|
V-234125
|
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 Tanium Server from working as expected.
https://docs.tanium.com/platform_install/platform_install/reference_host_system_security_exceptions.html. |
|
V-234124
|
Medium |
The Tanium Application 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 promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous... |
|
V-234123
|
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-234122
|
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/platform_install/reference_host_system_sizing_guidelines.html to determine how much free space should be allocated. |
|
V-234121
|
Medium |
The bandwidth consumption for the Tanium Application 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 designing the application to ensure the application makes the... |
|
V-234120
|
Medium |
The Tanium application 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 information system or a component of the system.... |
|
V-234119
|
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 therefore require a reasonable level of confidence in their origin. Non-approved OVAL... |
|
V-234118
|
Medium |
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 non-government 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 and must be manually downloaded on regular... |
|
V-234117
|
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 therefore require a reasonable level of confidence in their origin. Non-approved OVAL... |
|
V-234116
|
Medium |
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 non-government 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 and must be manually downloaded on... |
|
V-234115
|
Medium |
The Tanium Detect Local Directory Source must be configured to restrict access to only authorized maintainers of Intel. |
An IOC stream is a series or ""stream"" of intel that are imported from a vendor based on a subscription service or manually downloaded and placed in a folder. Detect can be configured to retrieve the IOC content on a regularly scheduled basis. The items in an IOC stream can... |
|
V-234114
|
Medium |
The Tanium documentation identifying recognized and trusted folders for Detect Local Directory Source 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. Detect can be configured to retrieve the IOC content on a regularly scheduled basis. The items in an IOC stream can... |
|
V-234113
|
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 be met via the application or by utilizing information system... |
|
V-234112
|
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 be met via the application or by utilizing information system... |
|
V-234111
|
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 be met via the application or by utilizing information system,... |
|
V-234110
|
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 utilizing 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-234109
|
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 Tanium Server from working as expected.
https://docs.tanium.com/platform_install/platform_install/reference_host_system_security_exceptions.html. |
|
V-234108
|
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 Tanium Server from working as expected.
https://docs.tanium.com/platform_install/platform_install/reference_host_system_security_exceptions.html. |
|
V-234107
|
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 or modifications compromise the confidentiality or integrity of the information.
This requirement applies only to those applications that are either distributed... |
|
V-234106
|
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 acceptable risk. However, in production environments it is critical that a SSL certificate... |
|
V-234105
|
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 utilizing 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-234104
|
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 able to connect to the Zone Server(s) in... |
|
V-234103
|
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-234102
|
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-234101
|
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 Security System (HBSS) or similar security suites with FIM capability. These... |
|
V-234100
|
Medium |
A Tanium connector must be configured to send log data to an external audit log reduction capable system. |
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 retrieval and aggregation efficiently. Consult documentation at https://docs.tanium.com/connect/connect/index.html for supported... |
|
V-234099
|
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 industry standard OpenSSL libraries used by Tanium ever come to light, no privileged account... |
|
V-234098
|
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-234097
|
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-234096
|
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 as a consequence of creating the object or via... |
|
V-234095
|
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-234094
|
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 Tanium Server, the Tanium Module server must be... |
|
V-234092
|
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 compromise the confidentiality or integrity of the information.
This requirement applies only to those applications that are either distributed or can... |
|
V-234091
|
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 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 ports/protocols on information systems.
Applications are capable of providing a wide variety of functions and services.... |
|
V-234090
|
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://docs.tanium.com/platform_install/platform_install/reference_network_ports.html |
|
V-234089
|
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 security or systems management tools because the Tanium Clients communicate in secure, linearly-controlled... |
|
V-234088
|
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 non-authorized functions, the files must be re-located... |
|
V-234087
|
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 software has not been tampered with and that it has been provided by a... |
|
V-234086
|
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 the purposes... |
|
V-234085
|
Medium |
The Tanium Connect module must be configured to forward Tanium Detect events to identified destinations. |
Indicators of Compromise (IOC) are artifacts, which are observed on the network or system that indicates computer intrusion. The Tanium Detect module detects, manages, and analyzes systems intrusion in real time. The module also responds to those detections.
By forwarding Detect events using Tanium Connect, the necessary forensic evidence supporting... |
|
V-234084
|
Medium |
The Tanium Detect must be configured to receive IOC streams only from trusted sources. |
An IOC stream is a series or stream of intel that are imported from a vendor based on a subscription service or manually downloaded and placed in a folder. Detect can be configured to retrieve the IOC content on a regularly scheduled basis. The items in an IOC stream can... |
|
V-234083
|
Medium |
The Tanium documentation identifying recognized and trusted Intel 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 imported. |
|
V-234082
|
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 user will require a second Tanium console user with a role... |
|
V-234081
|
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-234080
|
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-234079
|
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-234078
|
Medium |
The Tanium Application 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 user.
Although this setting does not apply when... |
|
V-234077
|
Medium |
The Tanium Server must protect the confidentiality and integrity of transmitted information, in preparation to be transmitted and data at rest, with cryptographic signing capabilities enabled to protect 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.
This requirement applies only to those applications that are either distributed or can allow access to data non-locally. Use of this requirement will be limited to situations... |
|
V-234076
|
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, for example: limiting the types of responses provided to database queries; limiting the number/frequency of database... |
|
V-234075
|
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 firewall rules since all communication remains on the... |
|
V-234074
|
Medium |
The Tanium Server installers 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 create SQL scripts requires Sysadmin-level permissions. Once the databases have been created, the Tanium Server and Apache services must be configured to execute under an account that holds at least the dbo role on... |
|
V-234073
|
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. |
|
V-234072
|
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-234071
|
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-234070
|
Medium |
Documentation defining Tanium functional 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 documentation should no longer be configured as a Tanium Console User.... |
|
V-234069
|
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-234068
|
Medium |
Tanium must notify SA and ISSO for account removal actions. |
When application accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves.
In order to detect and respond to events that affect user accessibility and application processing, applications must audit account removal actions and, as required, notify the... |
|
V-234067
|
Medium |
Tanium must notify SA and ISSO for account disabling actions. |
When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves.
In order to detect and respond to events that affect user accessibility and application processing, applications must audit account disabling actions and, as required, notify the... |
|
V-234066
|
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 organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of... |
|
V-234065
|
Medium |
The Tanium enterprise audit log reduction option must be configured to provide alerts based off Tanium audit data. |
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-234064
|
Medium |
The Tanium application must provide an immediate warning to the SA and ISSO (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-234063
|
Medium |
The Tanium application must notify 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 account enabling is one method for mitigating this risk. A... |
|
V-234062
|
Medium |
Tanium must notify SA 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 modification is one method for mitigating this risk. A comprehensive account... |
|
V-234061
|
Medium |
Tanium must notify SA 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 is one method for mitigating this risk. A comprehensive account... |
|
V-234060
|
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 remediation application may have automated mechanisms that perform automated scans for security-relevant software... |
|
V-234059
|
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 operation may be adversely affected.
Audit processing... |
|
V-234058
|
Medium |
The publicly accessible Tanium application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application. |
|
|
V-234057
|
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... |
|
V-234055
|
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 documentation should no longer be configured as a Tanium Console User.... |
|
V-234054
|
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 documentation should no longer be configured as a Tanium Console User.... |
|
V-234053
|
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 documentation should no longer be configured as a Tanium Console User.... |
|
V-234051
|
Medium |
Documentation identifying Tanium console users, their respective functional roles, and computer groups 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. Users who have been removed from the documentation should no longer be configured as a Tanium Console... |
|
V-234050
|
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 server.
For large sites, it is crucial to have the... |
|
V-234049
|
Medium |
The Tanium Application 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 Operation System Active Directory. |
|
V-234048
|
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 Operation System Active Directory.
Satisfies: SRG-APP-000233, SRG-APP-000317 |
|
V-234047
|
Medium |
The Tanium application must retain the session lock until the user reestablishes access using established identification and authentication procedures. |
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not want to log out because of the temporary nature of the absence.
The session lock is implemented at the point where session... |
|
V-234046
|
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 Tanium Server from working as expected.
https://docs.tanium.com/platform_install/platform_install/reference_host_system_security_exceptions.html. |
|
V-234045
|
Medium |
The Tanium application 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 adversaries that have successfully breached the information system and are using the... |
|
V-234044
|
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 may disallow the Client from working as expected.
https://docs.tanium.com/platform_install/platform_install/reference_host_system_security_exceptions.html. |
|
V-234043
|
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 psexec method of deployment must not be used. |
|
V-234042
|
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 software may disallow the Client from working as expected.
https://docs.tanium.com/platform_install/platform_install/reference_host_system_security_exceptions.html. |
|
V-234041
|
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-234040
|
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-234039
|
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 service. |
|
V-234038
|
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 security or systems management tools because the Tanium Clients communicate in secure, linearly-controlled... |
|
V-234037
|
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 does away with the ability of an attacker to conduct Man in the Middle (MitM) attacks for the purposes... |
|
V-234036
|
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-234035
|
Medium |
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 nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms used for... |
|
V-234034
|
Medium |
The vulnerability scanning application must implement privileged access authorization to all Tanium information systems and infrastructure components for selected organization-defined vulnerability scanning activities. |
In certain situations, the nature of the vulnerability scanning may be more intrusive, or the information system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system components facilitates more thorough vulnerability scanning and also protects the sensitive nature of such... |
|
V-234033
|
Medium |
Tanium must employ a deny-all, permit-by-exception (whitelist) policy to allow the execution of authorized software programs. |
Utilizing a whitelist 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-234032
|
Medium |
Tanium must implement organization-defined automated security responses if baseline configurations are changed in an unauthorized manner. |
Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the system. Changes to information system configurations can have unintended side effects, some of which may be relevant to security.
Detecting such changes and providing an automated response can help avoid... |
|
V-234031
|
Medium |
Tanium must 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 to centrally review the application logs, forensic analysis is negatively impacted.
Segregation... |
