| Finding ID |
Severity |
Title |
Description |
|
V-264369
|
High |
The UEM server, for each unique policy managed, must validate the policy is appropriate for an agent using [selection: a private key associated with an X509 certificate representing the agent, a token issued by the agent] associated with a policy signing key uniquely associated with the policy. |
It is critical that the UEM server sign all policy updates with validated certificate or private keys. Otherwise, there is no assurance that a malicious actor has not inserted itself in the process of packaging the code or policy.
This requirement focuses on communications protection for the application session rather... |
|
V-264368
|
High |
The UEM server must sign policies and policy updates using a private key associated with [selection: an X509 certificate, a public key provisioned to the agent trusted by the agent] for policy verification. |
It is critical that the UEM server sign all policy updates with validated certificate or private keys. Otherwise, there is no assurance that a malicious actor has not inserted itself in the process of packaging the code or policy.
Satisfies - FMT_POL_EXT.1.2
PP-MDM-411070 |
|
V-256892
|
High |
The UEM server must provide digitally signed policies and policy updates to the UEM agent. |
It is critical that the UEM server sign all policy updates with validated certificates. Otherwise, there is no assurance that a malicious actor has not inserted itself in the process of packaging the code or policy.
Satisfies: FMT_POL_EXT.1.1 |
|
V-234677
|
High |
The application must use FIPS-validated SHA-256 or higher hash function for digital signature generation and verification. |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Note: Although allowed by SP800-131Ar1 for some applications, SHA-1 is considered a compromised hashing standard and is being phased out of use by industry and government standards. Unless required for legacy use, DoD systems should not be... |
|
V-234668
|
High |
The UEM server must be configured to implement FIPS 140-2 mode for all server and agent encryption. |
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
Remote access is access to DoD non-public information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network.
A block cipher mode is an algorithm that features the... |
|
V-234664
|
High |
The UEM server must use a FIPS-validated cryptographic module to generate cryptographic hashes. |
FIPS 140-2 precludes the use of invalidated cryptography for the cryptographic protection of sensitive or valuable data within Federal systems. Unvalidated cryptography is viewed by NIST as providing no protection to the information or data. In effect, the data would be considered unprotected plaintext. If the agency specifies that the... |
|
V-234605
|
High |
The UEM server must be maintained at a supported version. |
The UEM vendor maintains specific product versions for a specific period of time. MDM/EMM server versions no longer supported by the vendor will not receive security updates for new vulnerabilities, which leaves them subject to exploitation.
Satisfies:FPT_TUD_EXT.1.1, FPT_TUD_EXT.1.2
Reference:PP-MDM-414005 |
|
V-234588
|
High |
The UEM server must connect to [assignment: [list of applications]] and managed mobile devices with an authenticated and secure (encrypted) connection to protect the confidentiality and integrity of transmitted information. |
Applications may include the following: update server, database, and enterprise directory service. 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... |
|
V-234555
|
High |
The UEM server must configure web management tools with FIPS-validated Advanced Encryption Standard (AES) cipher block algorithm to protect the confidentiality of maintenance and diagnostic communications for nonlocal maintenance sessions. |
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
Nonlocal maintenance and diagnostic activities are activities conducted by individuals communicating through either an external network (e.g., the internet) or an internal network. |
|
V-234538
|
High |
Before establishing a connection to any endpoint device being managed, the UEM server must establish a trusted path between the server and endpoint that provides assured identification of the end point using a bidirectional authentication mechanism configured with a FIPS-validated Advanced Encryption Standard (AES) cipher block algorithm to authenticate with the device. |
Without device-to-device authentication, communications with malicious devices may be established. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. Currently, DoD requires the use of AES for bidirectional authentication since it is the only FIPS-validated AES cipher block algorithm.
For... |
|
V-234408
|
High |
The UEM server must generate unique session identifiers using a FIPS-validated Random Number Generator (RNG) based on the Deterministic Random Bit Generators (DRBG) algorithm. |
Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session identifiers helps to protect against brute-force attacks to determine future session identifiers.
Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a... |
|
V-234383
|
High |
The UEM server must use FIPS-validated SHA-2 or higher hash function to protect the integrity of keyed-hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, and hash-only applications. |
Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Nonlocal maintenance and diagnostic activities are activities conducted by individuals communicating through either an external network (e.g., the internet) or an internal network.
Note: Although allowed by SP800-131Ar1 for some applications, SHA-1 is considered a compromised hashing... |
|
V-234375
|
High |
For UEM server using password authentication, the network element must use FIPS-validated SHA-2 or later protocol to protect the integrity of the password authentication process. |
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.
The information system must specify the hash algorithm used for authenticating passwords. Implementation of this requirement requires... |
|
V-234363
|
High |
The UEM server must use FIPS-validated SHA-2 or higher hash function to provide replay-resistant authentication mechanisms for network access to privileged accounts. |
A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack.
Anti-replay is a cryptographically based mechanism; thus, it must use FIPS-approved algorithms. An authentication process resists... |
|
V-234676
|
Medium |
The UEM server must validate certificates used for Transport Layer Security (TLS) functions by performing RFC 5280-compliant certification path validation. |
A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate.
Certification path validation includes checks such as certificate issuer trust,... |
|
V-234674
|
Medium |
If cipher suites using pre-shared keys are used for device authentication, the UEM server must have a minimum security strength of 112 bits or higher. |
Pre-shared keys are symmetric keys that are already in place prior to the initiation of a Transport Layer Security (TLS) session (e.g., as the result of a manual distribution). In general, pre-shared keys should not be used. However, the use of pre-shared keys may be appropriate for some closed environments... |
|
V-234673
|
Medium |
The UEM server 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-234669
|
Medium |
The UEM server must be configured to prohibit client negotiation to TLS 1.1, TLS 1.0, SSL 2.0, or SSL 3.0. |
Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol.
This requirement applies to Transport Layer Security (TLS) gateways (also known as Secure Sockets Layer [SSL] gateways), web servers, and web applications. Application protocols such as... |
|
V-234667
|
Medium |
The UEM server must be configured to allow authorized administrators to read all audit data from audit records on the server. |
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... |
|
V-234666
|
Medium |
The UEM server must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
Configuring the application to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed that affect the... |
|
V-234665
|
Medium |
The UEM server must, at a minimum, off-load audit logs of interconnected systems in real time and off-load standalone systems weekly. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity.
Satisfies:FMT_SMF.1.1(2) c.8, FAU_STG_EXT.1.1(1)
Reference:PP-MDM-411054 |
|
V-234659
|
Medium |
The UEM server must generate audit records for all account creations, modifications, disabling, and termination events. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234658
|
Medium |
The UEM server must generate audit records for all direct access to the information system. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234657
|
Medium |
The UEM server must generate audit records when successful/unsuccessful accesses to objects occur. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234656
|
Medium |
The UEM server must generate audit records when concurrent logons from different workstations occur. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234655
|
Medium |
The UEM server must generate audit records showing starting and ending time for user access to the system. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234654
|
Medium |
The UEM server must generate audit records for privileged activities or other system-level access. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234653
|
Medium |
The UEM server must generate audit records when successful/unsuccessful logon attempts occur. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234651
|
Medium |
The UEM server must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234649
|
Medium |
The UEM server must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234646
|
Medium |
The UEM server must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234645
|
Medium |
The UEM server must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234642
|
Medium |
The UEM server must generate audit records when successful/unsuccessful attempts to access security objects occur. |
Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g., module or... |
|
V-234629
|
Medium |
The UEM server must be configured to verify software updates to the server using a digital signature mechanism prior to installing those updates. |
Unauthorized modifications to software or firmware may be indicative of a sophisticated, targeted cyber-attack. Cryptographic authentication includes, for example, verifying that software or firmware components have been digitally signed using certificates recognized and approved by organizations. Code signing is an effective method to protect against malicious code.
Satisfies:FPT_TUD_EXT.1.3 |
|
V-234624
|
Medium |
The UEM server must alert the system administrator when anomalies in the operation of security functions are discovered. |
If anomalies are not acted upon, security functions may fail to secure the system.
Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security... |
|
V-234623
|
Medium |
The UEM server must run a suite of self-tests during initial start-up (power on) to demonstrate correct operation of the server. |
Without verification, security functions may not operate correctly and this failure may go unnoticed.
Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security... |
|
V-234622
|
Medium |
The UEM server must be configured with the periodicity of the following commands to the agent of six hours or less: - query connectivity status - query the current version of the managed device firmware/software - query the current version of installed mobile applications - read audit logs kept by the managed device. |
Without verification, security functions may not operate correctly and this failure may go unnoticed.
Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security... |
|
V-234603
|
Medium |
The UEM server must remove old software components after updated versions have been installed. |
Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system.
If the update is due to a security issue with the old... |
|
V-234596
|
Medium |
The UEM server must be configured to write to the server event log when invalid inputs are received. |
A common vulnerability of applications is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.
The behavior will... |
|
V-234575
|
Medium |
The UEM server must be configured to use X.509v3 certificates for code signing for integrity verification. |
It is critical that the UEM server validate code signing certificates for key activities such as code signing for system software updates, code signing for integrity verification, and policy signing. Otherwise, there is no assurance that a malicious actor has not inserted itself in the process of packaging the code... |
|
V-234574
|
Medium |
The UEM server must be configured to use X.509v3 certificates for code signing for system software updates. |
It is critical that the UEM server validate code signing certificates for key activities such as code signing for system software updates, code signing for integrity verification, and policy signing. Otherwise, there is no assurance that a malicious actor has not inserted itself in the process of packaging the code... |
|
V-234573
|
Medium |
The UEM server must only allow the use of DoD PKI established certificate authorities for verification of the establishment of protected sessions. |
Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DoD-approved CA, trust of this CA has not been established.... |
|
V-234556
|
Medium |
The UEM server must verify remote disconnection when non-local maintenance and diagnostic sessions are terminated. |
If the remote connection is not closed and verified as closed, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Remote connections must be disconnected and verified as disconnected when non-local maintenance sessions have been terminated and are no longer... |
|
V-234544
|
Medium |
The UEM server, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. |
Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates). |
|
V-234543
|
Medium |
The UEM server must prohibit the use of cached authenticators after an organization-defined time period. |
If cached authentication information is out-of-date, the validity of the authentication information may be questionable.
According to the CNSS 1253, the IA-5(13) control which is tied to this requirement is not defined at the DoD-level. The organization should specify this value based on numerous factors, including the application in question,... |
|
V-234526
|
Medium |
The UEM server must disable organization-defined functions, ports, protocols, and services (within the application) deemed unnecessary and/or non-secure. |
Removal of unneeded or non-secure functions, ports, protocols, and services mitigate the risk of unauthorized connection of devices, unauthorized transfer of information, or other exploitation of these resources.
Examples include unneeded listening ports.
The organization must perform a periodic scan/review of the application (as required by CCI-000384) and disable functions,... |
|
V-234524
|
Medium |
The UEM server must audit the enforcement actions used to restrict access associated with changes to the application. |
Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks and an audit trail will not be available for forensic investigation for after-the-fact actions.
Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings.... |
|
V-234523
|
Medium |
The UEM server must enforce access restrictions associated with changes to the server 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, it should be noted that any changes to the hardware, software, and/or firmware components of the information system... |
|
V-234521
|
Medium |
The UEM server must be configured to only allow enrolled devices that are compliant with UEM policies and assigned to a user in the application access group to download applications. |
If the application install policy is not enforced, malicious applications and vulnerable applications can be installed on managed mobile devices, which could compromise DOD data.
Satisfies:FMT_MOF.1.1(3)
Reference:PP-MDM-423206 |
|
V-234520
|
Medium |
The UEM server must prohibit user installation of software by an administrator without the appropriate assigned permission for software installation. |
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-234517
|
Medium |
The UEM server must be configured to record time stamps for audit records that meet a granularity of one second for a minimum degree of precision. |
Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records.
Time stamps generated by the application include date and time. Granularity of time measurements refers to the degree of synchronization between information system clocks and reference clocks. |
|
V-234516
|
Medium |
The UEM server must be configured to record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). |
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Time stamps generated by the application include date and time. Time is commonly expressed in UTC, a modern continuation of GMT, or local time with an offset from UTC.... |
|
V-234500
|
Medium |
The UEM server must be configured to transfer UEM server logs to another server for storage, analysis, and reporting. Note: UEM server logs include logs of UEM events and logs transferred to the UEM server by UEM agents of managed devices. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity.
Note: UEM server logs include logs of UEM events and logs transferred to the UEM server by UEM agents of managed devices.
Satisfies:FMT_SMF.1.1(2)... |
|
V-234491
|
Medium |
The UEM server must automatically lock the account until the locked account is released by an administrator when three unsuccessful login attempts in 15 minutes are exceeded. |
By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account.
Satisfies:FMT_SMF.1(2)b
Reference:PP-MDM-431030 |
|
V-234489
|
Medium |
The UEM server must audit the execution of privileged functions. |
Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse, and... |
|
V-234475
|
Medium |
The UEM server must be configured to have at least one user in defined administrator roles. |
Having several administrative roles for the UEM server supports separation of duties. This allows administrator-level privileges to be granted granularly, such as giving application management privileges to one group and security policy privileges to another group. This helps prevent administrators from intentionally or inadvertently altering other settings and configurations of... |
|
V-234466
|
Medium |
The UEM server must notify system administrator (SA) and information system security officer (ISSO) of account enabling actions. |
Once an attacker establishes access to an application, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Sending notification of account enabling events to the SA and ISSO is one... |
|
V-234465
|
Medium |
The UEM server must automatically audit account-enabling actions. |
Once an attacker establishes access to an application, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Automatically auditing account enabling actions provides logging that can be used for forensic... |
|
V-234444
|
Medium |
The UEM server must display an explicit logout message to users indicating the reliable termination of authenticated communications sessions. |
If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Users need to be aware of whether or not the session has been terminated.
Information resources to which users gain access via... |
|
V-234443
|
Medium |
The UEM server must provide logout capability for user-initiated communication sessions. |
If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session.
Information resources to which users gain access via authentication include, for example, local workstations, databases, and password-protected websites/web-based services. However, for some... |
|
V-234442
|
Medium |
The UEM server must automatically terminate a user session after an organization-defined period of user inactivity. |
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-234441
|
Medium |
The UEM server must notify system administrators (SAs) and the information system security officer (ISSO) for account removal actions. |
When application accounts are removed, user accessibility is affected. Accounts are utilized for identifying users or for identifying the application processes themselves. Sending notification of account removal events to the SA and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that application accessibility... |
|
V-234440
|
Medium |
The UEM server must notify system administrators (SAs) and the information system security officer (ISSO) for account disabling actions. |
When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the application processes themselves. Sending notification of account disabling events to the SA and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that application... |
|
V-234439
|
Medium |
The UEM server must notify system administrators (SAs) and the information system security officer (ISSO) when accounts are modified. |
When application accounts are modified, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the application processes themselves. Sending notification of account modification events to the SA and ISSO is one method for mitigating this risk. Such a capability greatly reduces the risk that application... |
|
V-234438
|
Medium |
The UEM server must notify system administrators (SAs) and the information system security officer (ISSO) when accounts are created. |
Once an attacker establishes access to an application, 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. Sending notification of account creation events to the SA and ISSO is one method for... |
|
V-234430
|
Medium |
The application must notify the Information System Security Manager (ISSM) and Information System Security Officer (ISSO) of failed security verification tests. |
If personnel are not notified of failed security verification tests, they will not be able to take corrective action and the unsecure condition(s) will remain.
Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation... |
|
V-234425
|
Medium |
The UEM server must reveal error messages only to the Information System Security Manager (ISSM) and Information System Security Officer (ISSO). |
Only authorized personnel should 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-234424
|
Medium |
The UEM server 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 needs to be carefully considered by the organization and development team.
Organizations carefully consider the structure/content of error messages. The extent to which... |
|
V-234421
|
Medium |
The UEM server must check the validity of all data inputs. |
Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application or information system compromise. Invalid input is one of the primary methods employed... |
|
V-234410
|
Medium |
In the event of a system failure, the UEM server must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes. |
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-234409
|
Medium |
The UEM server must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Applications or systems that fail suddenly and with no incorporated failure state planning may leave the hosting system available but with a reduced security... |
|
V-234407
|
Medium |
The UEM server must recognize only system-generated session identifiers. |
Applications utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the session identifier, or can inject or manually insert session information, the session may be compromised.
Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a... |
|
V-234406
|
Medium |
The UEM server must invalidate session identifiers upon user logout or other session termination. |
Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries from capturing and continuing to employ previously valid session IDs.
This requirement focuses on communications protection for the application session rather than for the network packet. This requirement applies to applications that utilize communications sessions.... |
|
V-234405
|
Medium |
The UEM server must protect the authenticity of communications sessions. |
Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions.
Application communication sessions are protected utilizing transport encryption protocols, such as TLS. TLS provides web applications with a means to be able to authenticate user sessions and encrypt application traffic. Session authentication can be... |
|
V-234392
|
Medium |
The UEM server must be configured to invoke either host-OS functionality or server functionality to provide a trusted communication channel between itself and managed devices that provides assured identification of its endpoints and protection of the communicated data from modification and disclosure using [selection:
-TLS,
-HTTPS]. |
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
Nonlocal maintenance and diagnostic activities are activities conducted by individuals communicating through either an external network (e.g., the internet) or an internal network.
Satisfies: FTP_TRP.1.1(2) Refinement |
|
V-234391
|
Medium |
The UEM server must be configured to invoke either host-OS functionality or server functionality to provide a trusted communication channel between itself and remote administrators that provides assured identification of its endpoints and protection of the communicated data from modification and disclosure using [selection:
-IPsec,
-SSH,
-TLS,
-HTTPS]. |
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
Nonlocal maintenance and diagnostic activities are activities conducted by individuals communicating through either an external network (e.g., the internet) or an internal network.
Satisfies: FTP_TRP.1.1(1) Refinement |
|
V-234390
|
Medium |
The UEM server must be configured to provide a trusted communication channel between itself and authorized IT entities using [selection:
-IPsec,
-SSH,
-mutually authenticated TLS,
-mutually authenticated DTLS,
-HTTPS]. |
Examples of authorized IT entities: audit server, Active Directory, software update server, and database server.
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
Nonlocal maintenance and diagnostic activities are activities conducted by individuals communicating through either an external network (e.g., the... |
|
V-234382
|
Medium |
The UEM server must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
To prevent the compromise of authentication information such as passwords during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism.
Obfuscation of user-provided information when typed into the system is a method used in... |
|
V-234381
|
Medium |
The UEM server must 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.
Satisfies: FIA
Reference:PP-MDM-414003 |
|
V-234380
|
Medium |
The UEM server, when using PKI-based authentication, must enforce authorized access to the corresponding private key. |
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-234379
|
Medium |
When the UEM server cannot establish a connection to determine the validity of a certificate, the server must be configured not to have the option to accept the certificate. |
When an UEM server accepts an unverified certificate, it may be trusting a malicious actor. For example, messages signed with an invalid certificate may contain links to malware, which could lead to the installation or distribution of that malware on DoD information systems, leading to compromise of DoD sensitive information... |
|
V-234378
|
Medium |
When using PKI-based authentication for user access, the UEM server must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. |
Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. To meet this requirement, the information system must create trusted channels between itself and remote trusted authorized IT product (e.g., syslog server) entities that protect the confidentiality... |
|
V-234377
|
Medium |
The UEM server must enforce a 60-day maximum password lifetime restriction. |
Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals.
One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit the lifetime of passwords and force users to change their... |
|
V-234374
|
Medium |
For UEM server using password authentication, the application must store only cryptographic representations of passwords. |
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read and easily compromised. Use of passwords for authentication is intended only for limited situations and should not be used as a replacement for... |
|
V-234373
|
Medium |
UEM server must require the change of at least 50 percent of the previous password's characters. |
If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks.
The number of changed characters refers to the number of changes required with respect to the total... |
|
V-234372
|
Medium |
The UEM server must enforce password complexity by requiring that at least one special character be used. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor in determining how long it takes to... |
|
V-234371
|
Medium |
The UEM server must enforce password complexity by requiring that at least one numeric character be used. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-234370
|
Medium |
The UEM server must enforce password complexity by requiring that at least one lowercase character be used. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-234369
|
Medium |
The UEM server must enforce password complexity by requiring that at least one uppercase character be used. |
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-234368
|
Medium |
The UEM server must prohibit password reuse for a minimum of five generations. |
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
To meet password policy requirements, passwords need to be changed at specific policy-based intervals.
If the information system or application allows the user to consecutively reuse their password when... |
|
V-234367
|
Medium |
The UEM server must enforce a minimum 15-character password length. |
The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that... |
|
V-234364
|
Medium |
The UEM server must implement replay-resistant authentication mechanisms for network access to nonprivileged accounts. |
A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack.
An authentication process resists replay attacks if it is impractical to achieve a successful authentication by... |
|
V-234361
|
Medium |
The UEM server must be configured to use DOD PKI for multifactor authentication. This requirement is included in SRG-APP-000149. |
Using an authentication device, such as a common access card (CAC) or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
Multifactor solutions that require devices separate from information systems gaining... |
|
V-234360
|
Medium |
The UEM server must ensure users are authenticated with an individual authenticator prior to using a group authenticator. |
To ensure individual accountability and prevent unauthorized access, application users must be individually identified and authenticated.
Individual accountability mandates that each user is uniquely identified. A group authenticator is a shared account or some other form of authentication that allows multiple unique individuals to access the application using a single... |
|
V-234358
|
Medium |
All UEM server local accounts created during application installation and configuration must be removed.
Note: In this context local accounts refers to user and or administrator accounts on the server that use user name and password for user access and authentication. |
A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. If an attacker compromises an account, the entire MDM server infrastructure is at risk. Providing automated support functions for the management of accounts will ensure only active accounts... |
|
V-234356
|
Medium |
The UEM server must be configured to use a DoD Central Directory Service to provide multifactor authentication for network access to privileged and non-privileged accounts. |
A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. If an attacker compromises an account, the entire MDM server infrastructure is at risk. Providing automated support functions for the management of accounts will ensure only active accounts... |
|
V-234355
|
Medium |
The UEM server must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
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-234354
|
Medium |
The UEM server must be configured to use only documented platform APIs. |
Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions.
Application communication sessions are protected utilizing transport encryption protocols, such as TLS. TLS provides web applications with a means to authenticate user sessions and encrypt application traffic. Session authentication can be single (one-way) or... |
|
V-234353
|
Medium |
The firewall protecting the UEM server platform must be configured so only DoD-approved ports, protocols, and services are enabled. (See the DoD Ports, Protocols, Services Management [PPSM] Category Assurance Levels [CAL] list for DoD-approved ports, protocols, and services). |
All ports, protocols, and services used on DoD networks must be approved and registered via the DoD PPSM process. This is to ensure a risk assessment has been completed before a new port, protocol, or service is configured on a DoD network and has been approved by proper DoD authorities.... |
|
V-234352
|
Medium |
The UEM server must be configured to disable non-essential capabilities. |
It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Applications are capable of providing a wide variety... |
|
V-234351
|
Medium |
The UEM server must limit privileges to change the software resident within software libraries. |
If the application were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.
This requirement applies to applications with software libraries that are accessible and configurable, as... |
|
V-234349
|
Medium |
The UEM server must prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization. |
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-234347
|
Medium |
The UEM server must back up audit records at least every seven days onto a log management server. |
Protection of log data includes ensuring log data is not accidentally lost or deleted. Backing up audit records to a different system or onto separate media than the system being audited on an organizationally defined frequency helps ensure, in the event of a catastrophic system failure, the audit records will... |
|
V-234343
|
Medium |
The UEM server must protect audit information from unauthorized deletion. |
If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized deletion. This requirement can be achieved... |
|
V-234342
|
Medium |
The UEM server must protect audit information from unauthorized modification. |
If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized modification.
This requirement can be achieved... |
|
V-234341
|
Medium |
The UEM server must protect audit information from any type of unauthorized read access. |
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult if not impossible to achieve. In addition, access to audit records provides information an attacker could potentially use to his or her advantage.
To ensure the... |
|
V-234340
|
Medium |
The UEM server must use host operating system clocks to generate time stamps for audit records. |
Without an internal clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events.... |
|
V-234335
|
Medium |
The UEM SRG 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-234334
|
Medium |
The UEM server must be configured to generate audit records containing the full-text recording of privileged commands or the individual identities of group account users. |
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. The additional information required is dependent on the type of information (i.e., sensitivity of the... |
|
V-234333
|
Medium |
The UEM server must be configured to generate audit records containing information that establishes the identity of any individual or process associated with the event. |
Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event.
Event identifiers (if authenticated or otherwise known) include, but are not limited to, user database tables, primary key... |
|
V-234332
|
Medium |
The UEM server must be configured to produce audit records that contain information to establish the outcome of the events. |
Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system.
Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state... |
|
V-234331
|
Medium |
The UEM server must be configured to produce audit records containing information to establish the source of the events. |
Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
In addition to logging where events occur within the application, the application must also produce audit records that identify the application itself as the source of... |
|
V-234330
|
Medium |
The UEM server must be configured to produce audit records containing information to establish where the events occurred. |
Failure to generate these audit records makes it more difficult to identify or investigate attempted or successful compromises, potentially causing incidents to last longer than necessary.
Satisfies:FAU_GEN.1.2(1)
Reference:PP-MDM-412060 |
|
V-234329
|
Medium |
The UEM server must be configured to produce audit records containing information to establish when (date and time) the events occurred. |
Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident.
In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time).
Associating event types with detected... |
|
V-234328
|
Medium |
The UEM server must be configured to produce audit records containing information to establish what type of events occurred. |
Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit record content that may be necessary to satisfy the requirement of this policy includes, for example, time stamps, source and destination... |
|
V-234327
|
Medium |
The UEM server must initiate session auditing upon startup. |
If auditing is enabled late in the startup process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.
Satisfies:FAU_GEN.1.1(1) |
|
V-234326
|
Medium |
The UEM server must generate audit records when successful/unsuccessful attempts to access privileges occur. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-234325
|
Medium |
The UEM server must be configured to allow only specific administrator roles to select which auditable events are to be audited. |
Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate,... |
|
V-234324
|
Medium |
The UEM server must be configured to provide audit records in a manner suitable for the Authorized Administrators to interpret the information. |
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... |
|
V-234323
|
Medium |
The UEM server must provide audit record generation capability for DoD-defined auditable events within all application components. |
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
Audit records can be generated from various components within the application (e.g., process, module). Certain specific application functionalities may be audited as... |
|
V-234318
|
Medium |
The UEM server must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation. |
Without non-repudiation, it is impossible to positively attribute an action to an individual (or process acting on behalf of an individual).
Non-repudiation services can be used to determine if information originated from a particular individual, or if an individual took specific actions (e.g., sending an email, signing a contract, approving... |
|
V-234311
|
Medium |
The UEM server must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application. |
|
|
V-234310
|
Medium |
The UEM server must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account.
Satisfies:FMT_SMF.1(2)b.
Reference:PP-MDM-431028 |
|
V-234292
|
Medium |
The UEM server must automatically audit account removal actions. |
When application accounts are removed, user accessibility is affected. Once an attacker establishes access to an application, the attacker often attempts to remove authorized accounts to disrupt services or prevent the implementation of countermeasures. Auditing account removal actions provides logging that can be used for forensic purposes.
To address access... |
|
V-234291
|
Medium |
The UEM server must automatically audit account disabling actions. |
When application accounts are disabled, user accessibility is affected. Once an attacker establishes access to an application, the attacker often attempts to disable authorized accounts to disrupt services or prevent the implementation of countermeasures. Auditing account disabling actions provides logging that can be used for forensic purposes.
To address access... |
|
V-234290
|
Medium |
The UEM server must automatically audit account modification. |
Once an attacker establishes 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. Auditing of account creation is one method for mitigating this risk. A comprehensive account management... |
|
V-234289
|
Medium |
The UEM server must automatically audit account creation. |
Once an attacker establishes 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. Auditing of account creation is one method for mitigating this risk. A comprehensive account management... |
|
V-234288
|
Medium |
The UEM server must automatically disable accounts after a 35-day period of account inactivity. |
Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications need to track periods of user inactivity and disable accounts after 35 days... |
|
V-234287
|
Medium |
The UEM server must automatically remove or disable temporary user accounts after 72 hours if supported by the UEM server. |
If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary user accounts must be set upon account creation.
Temporary user accounts are established as part of normal... |
|
V-234286
|
Medium |
The UEM server must provide automated mechanisms for supporting 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.
A comprehensive application account management process that includes automation helps to ensure accounts designated as requiring attention are consistently and promptly addressed. Examples include,... |
|
V-234283
|
Medium |
The UEM server must use TLS 1.2, or higher, to protect the confidentiality of sensitive data during electronic dissemination using remote access. |
Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol.
This requirement applies to Transport Layer Security (TLS) gateways (also known as Secure Sockets Layer [SSL] gateways), web servers, and web applications and is not applicable... |
|
V-234279
|
Medium |
The MDM server 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-234278
|
Medium |
The MDM server must provide the capability for users to directly initiate a session lock. |
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-234277
|
Medium |
The UEM server must initiate a session lock after a 15-minute period of inactivity. |
A session time-out 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 log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their application... |
|
V-234276
|
Medium |
The UEM server must conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
A session time-out 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 log out because of the temporary nature of the absence.
The session lock is implemented at the point where session activity... |
|
V-234275
|
Medium |
The UEM server must limit the number of concurrent sessions per privileged user account to three or less concurrent 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-234312
|
Low |
The UEM server must retain the access banner until the user acknowledges acceptance of the access conditions. |
The banner must be acknowledged by the user prior to allowing the user access to the application. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with... |
