Unified Endpoint Management Server Security Requirements Guide

Description

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

Details

Version / Release: V1R1

Published: 2020-12-14

Updated At: 2021-02-04 18:26:54

Actions

Download

Filter

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

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-234275r617395_rule SRG-APP-000001-UEM-000001 CCI-000054 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
    SV-234276r617355_rule SRG-APP-000002-UEM-000002 CCI-000060 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 implemente
    SV-234277r617355_rule SRG-APP-000003-UEM-000003 CCI-000057 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
    SV-234278r617355_rule SRG-APP-000004-UEM-000004 CCI-000058 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
    SV-234279r617355_rule SRG-APP-000005-UEM-000005 CCI-000056 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
    SV-234283r617355_rule SRG-APP-000014-UEM-000009 CCI-000068 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
    SV-234286r617355_rule SRG-APP-000023-UEM-000012 CCI-000015 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 inc
    SV-234287r617355_rule SRG-APP-000024-UEM-000013 CCI-000016 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 creatio
    SV-234288r617355_rule SRG-APP-000025-UEM-000014 CCI-000017 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 t
    SV-234289r617355_rule SRG-APP-000026-UEM-000015 CCI-000018 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
    SV-234290r617355_rule SRG-APP-000027-UEM-000016 CCI-001403 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
    SV-234291r617355_rule SRG-APP-000028-UEM-000017 CCI-001404 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.
    SV-234292r617355_rule SRG-APP-000029-UEM-000018 CCI-001405 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. A
    SV-234310r617396_rule SRG-APP-000065-UEM-000036 CCI-000044 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-43102
    SV-234311r617355_rule SRG-APP-000068-UEM-000037 CCI-000048 MEDIUM The UEM server must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application. Display of the DoD-approved use notification before granting access to the application ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and
    SV-234312r617355_rule SRG-APP-000069-UEM-000038 CCI-000050 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
    SV-234315r617355_rule SRG-APP-000075-UEM-000041 CCI-000052 MEDIUM The UEM server must notify the user, upon successful logon (access) to the application, of the date and time of the last logon (access). Users need to be aware of activity that occurs regarding their application account. Providing users with information regarding the date and time of their last successful login allows the user to determine if any unauthorized activity has occurred and give
    SV-234316r617355_rule SRG-APP-000076-UEM-000042 CCI-000053 MEDIUM The UEM server must notify the user, upon successful logon (access), of the number of unsuccessful logon (access) attempts since the last successful logon (access). Users need to be aware of activity that occurs regarding their application account. Providing users with information regarding the number of unsuccessful attempts made to log in to their account allows the user to determine if any unauthorized activity ha
    SV-234318r617355_rule SRG-APP-000080-UEM-000044 CCI-000166 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
    SV-234323r617355_rule SRG-APP-000089-UEM-000049 CCI-000169 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
    SV-234324r617355_rule SRG-APP-000089-UEM-000050 CCI-000169 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
    SV-234325r617355_rule SRG-APP-000090-UEM-000051 CCI-000171 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 th
    SV-234326r617355_rule SRG-APP-000091-UEM-000052 CCI-000172 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 rec
    SV-234327r617355_rule SRG-APP-000092-UEM-000053 CCI-001464 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.
    SV-234328r617355_rule SRG-APP-000095-UEM-000055 CCI-000130 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 require
    SV-234329r617355_rule SRG-APP-000096-UEM-000056 CCI-000131 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 personne
    SV-234330r617355_rule SRG-APP-000097-UEM-000057 CCI-000132 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
    SV-234331r617355_rule SRG-APP-000098-UEM-000058 CCI-000133 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 audi
    SV-234332r617355_rule SRG-APP-000099-UEM-000059 CCI-000134 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 succ
    SV-234333r617355_rule SRG-APP-000100-UEM-000060 CCI-001487 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
    SV-234334r617355_rule SRG-APP-000101-UEM-000061 CCI-000135 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 requ
    SV-234335r617355_rule SRG-APP-000108-UEM-000062 CCI-000139 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 opera
    SV-234340r617403_rule SRG-APP-000116-UEM-000067 CCI-000159 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
    SV-234341r617355_rule SRG-APP-000118-UEM-000068 CCI-000162 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 at
    SV-234342r617355_rule SRG-APP-000119-UEM-000069 CCI-000163 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
    SV-234343r617355_rule SRG-APP-000120-UEM-000070 CCI-000164 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
    SV-234347r617355_rule SRG-APP-000125-UEM-000074 CCI-001348 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
    SV-234349r617355_rule SRG-APP-000131-UEM-000076 CCI-001749 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 softwa
    SV-234351r617355_rule SRG-APP-000133-UEM-000078 CCI-001499 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 applie
    SV-234352r617355_rule SRG-APP-000141-UEM-000079 CCI-000381 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
    SV-234353r617355_rule SRG-APP-000142-UEM-000080 CCI-000382 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 ap
    SV-234354r617397_rule SRG-APP-000142-UEM-000081 CCI-000382 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.
    SV-234355r617404_rule SRG-APP-000148-UEM-000082 CCI-000764 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 org
    SV-234356r617405_rule SRG-APP-000149-UEM-000083 CCI-000765 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 r
    SV-234358r617355_rule SRG-APP-000151-UEM-000085 CCI-000767 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 r
    SV-234360r617406_rule SRG-APP-000153-UEM-000087 CCI-000770 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
    SV-234361r617355_rule SRG-APP-000154-UEM-000088 CCI-001936 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 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
    SV-234363r617407_rule SRG-APP-000156-UEM-000090 CCI-001941 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 cryptogra
    SV-234364r617408_rule SRG-APP-000157-UEM-000091 CCI-001942 MEDIUM The UEM server must implement replay-resistant authentication mechanisms for network access to non-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. An authentication process
    SV-234366r617355_rule SRG-APP-000163-UEM-000093 CCI-000795 MEDIUM The UEM server must disable identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. Inactive identifiers pose a risk to systems and applications. Attackers that are able to exploit an inactive identifier can potentially obtain and maintain undetected access to the application. Owners of inactive accounts will not notice if unauthorized a
    SV-234367r617355_rule SRG-APP-000164-UEM-000094 CCI-000205 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 bru
    SV-234368r617355_rule SRG-APP-000165-UEM-000095 CCI-000200 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
    SV-234369r617355_rule SRG-APP-000166-UEM-000096 CCI-000192 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
    SV-234370r617355_rule SRG-APP-000167-UEM-000097 CCI-000193 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
    SV-234371r617355_rule SRG-APP-000168-UEM-000098 CCI-000194 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
    SV-234372r617355_rule SRG-APP-000169-UEM-000099 CCI-001619 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
    SV-234373r617355_rule SRG-APP-000170-UEM-000100 CCI-000195 MEDIUM The UEM server must require the change of at least 15 of the total number of characters when passwords are changed. 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 c
    SV-234374r617355_rule SRG-APP-000171-UEM-000101 CCI-000196 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
    SV-234375r617355_rule SRG-APP-000172-UEM-000102 CCI-000197 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
    SV-234376r617355_rule SRG-APP-000173-UEM-000103 CCI-000198 MEDIUM The UEM server must enforce 24 hours/1 day as the minimum password lifetime. Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. Restricting this setting limits the user's ability to change their password. Passwords need to be changed at sp
    SV-234377r617355_rule SRG-APP-000174-UEM-000104 CCI-000199 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
    SV-234378r617412_rule SRG-APP-000175-UEM-000105 CCI-000185 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 re
    SV-234379r617355_rule SRG-APP-000175-UEM-000106 CCI-000185 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
    SV-234380r617355_rule SRG-APP-000176-UEM-000107 CCI-000186 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 priva
    SV-234381r617409_rule SRG-APP-000177-UEM-000108 CCI-000187 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
    SV-234382r617355_rule SRG-APP-000178-UEM-000109 CCI-000206 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 m
    SV-234383r617355_rule SRG-APP-000179-UEM-000110 CCI-000803 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.
    SV-234390r617355_rule SRG-APP-000191-UEM-000117 CCI-001135 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.
    SV-234391r617355_rule SRG-APP-000191-UEM-000118 CCI-001135 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 eit
    SV-234392r617355_rule SRG-APP-000191-UEM-000119 CCI-001135 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 eit
    SV-234405r617355_rule SRG-APP-000219-UEM-000132 CCI-001184 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.
    SV-234406r617355_rule SRG-APP-000220-UEM-000133 CCI-001185 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 sessio
    SV-234407r617355_rule SRG-APP-000223-UEM-000134 CCI-001664 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 I
    SV-234408r617355_rule SRG-APP-000224-UEM-000135 CCI-001188 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 sess
    SV-234409r617355_rule SRG-APP-000225-UEM-000136 CCI-001190 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 ho
    SV-234410r617413_rule SRG-APP-000226-UEM-000137 CCI-001665 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
    SV-234421r617398_rule SRG-APP-000251-UEM-000148 CCI-001310 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 i
    SV-234424r617355_rule SRG-APP-000266-UEM-000151 CCI-001312 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.
    SV-234425r617355_rule SRG-APP-000267-UEM-000152 CCI-001314 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 operatio
    SV-234426r617355_rule SRG-APP-000268-UEM-000153 CCI-001328 MEDIUM The UEM server must, when a component failure is detected, activate an organization-defined alarm and/or automatically shut down the application or the component. Predictable failure prevention requires organizational planning to address system failure issues. If components key to maintaining systems security fail to function, the system could continue operating in an insecure state. The organization must be prepar
    SV-234430r617355_rule SRG-APP-000275-UEM-000157 CCI-001294 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 sy
    SV-234438r617355_rule SRG-APP-000291-UEM-000165 CCI-001683 MEDIUM The UEM server must notify system administrators 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 crea
    SV-234439r617355_rule SRG-APP-000292-UEM-000166 CCI-001684 MEDIUM The UEM server must notify system administrators and the Information System Security Officer (ISSO) when accounts are modified. When application accounts are modified, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the application processes themselves. Sending notification of account modification events to the system admin
    SV-234440r617355_rule SRG-APP-000293-UEM-000167 CCI-001685 MEDIUM The UEM server must notify system administrators and the Information System Security Officer (ISSO) for account disabling actions. When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual users or for identifying the application processes themselves. Sending notification of account disabling events to the system administ
    SV-234441r617414_rule SRG-APP-000294-UEM-000168 CCI-001686 MEDIUM The UEM server must notify system administrators and the Information System Security Officer (ISSO) for account removal actions. When application accounts are removed, user accessibility is affected. Accounts are utilized for identifying users or for identifying the application processes themselves. Sending notification of account removal events to the system administrator and ISSO
    SV-234442r617355_rule SRG-APP-000295-UEM-000169 CCI-002361 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, net
    SV-234443r617355_rule SRG-APP-000296-UEM-000170 CCI-002363 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
    SV-234444r617355_rule SRG-APP-000297-UEM-000171 CCI-002364 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
    SV-234465r617355_rule SRG-APP-000319-UEM-000192 CCI-002130 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 a
    SV-234466r617399_rule SRG-APP-000320-UEM-000193 CCI-002132 MEDIUM The UEM server must notify system administrator and Information System Security Officer (ISSO) of account enabling actions. Once an attacker establishes access to an application, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Sending notification of
    SV-234473r617355_rule SRG-APP-000327-UEM-000200 CCI-002186 MEDIUM The UEM server must employ an audited override of automated access control mechanisms under organization-defined conditions. 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. Actions that could adversely impact the system m
    SV-234475r617355_rule SRG-APP-000329-UEM-000202 CCI-002169 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 anot
    SV-234489r617355_rule SRG-APP-000343-UEM-000216 CCI-002234 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
    SV-234491r617355_rule SRG-APP-000345-UEM-000218 CCI-002238 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
    SV-234500r617411_rule SRG-APP-000358-UEM-000228 CCI-001851 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 tr
    SV-234516r617355_rule SRG-APP-000374-UEM-000244 CCI-001890 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 G
    SV-234517r617355_rule SRG-APP-000375-UEM-000245 CCI-001889 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 synchr
    SV-234519r617355_rule SRG-APP-000377-UEM-000247 CCI-001811 MEDIUM The UEM server must verify the digital signature of software before installation and alert the Information System Security Officer (ISSO), Information System Security Manager (ISSM), and other designated personnel if unauthorized software is detected. Unauthorized software not only increases risk by increasing the number of potential vulnerabilities, it also can contain malicious code. Sending an alert (in real time) when unauthorized software is detected allows designated personnel to take action on t
    SV-234520r617355_rule SRG-APP-000378-UEM-000248 CCI-001812 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 use
    SV-234521r617355_rule SRG-APP-000378-UEM-000249 CCI-001812 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
    SV-234523r617355_rule SRG-APP-000380-UEM-000251 CCI-001813 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 note
    SV-234524r617355_rule SRG-APP-000381-UEM-000252 CCI-001814 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.
    SV-234526r617355_rule SRG-APP-000383-UEM-000254 CCI-001762 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
    SV-234532r617355_rule SRG-APP-000389-UEM-000260 CCI-002038 MEDIUM The UEM server must require users (administrators) to reauthenticate when roles change. Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical th
    SV-234533r617355_rule SRG-APP-000390-UEM-000261 CCI-002039 MEDIUM The UEM server must require end-point devices to reauthenticate when organization-defined circumstances or situations requiring reauthentication. This requirement refers to the end-point device user reauthenticating to the device. The following are examples of organization-defined circumstances or situations requiring reauthentication: (i) After a screen lock; (ii) After device reboot; (iii) B
    SV-234538r617415_rule SRG-APP-000395-UEM-000266 CCI-001967 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
    SV-234543r617355_rule SRG-APP-000400-UEM-000271 CCI-002007 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
    SV-234544r617355_rule SRG-APP-000401-UEM-000272 CCI-001991 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).
    SV-234555r617355_rule SRG-APP-000412-UEM-000283 CCI-003123 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 eit
    SV-234556r617355_rule SRG-APP-000413-UEM-000284 CCI-002891 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 mainte
    SV-234573r617355_rule SRG-APP-000427-UEM-000298 CCI-002470 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
    SV-234574r617355_rule SRG-APP-000427-UEM-000299 CCI-002470 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
    SV-234575r617355_rule SRG-APP-000427-UEM-000300 CCI-002470 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
    SV-234588r617355_rule SRG-APP-000439-UEM-000313 CCI-002418 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
    SV-234596r617355_rule SRG-APP-000447-UEM-000321 CCI-002754 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
    SV-234603r617355_rule SRG-APP-000454-UEM-000328 CCI-002617 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
    SV-234605r617355_rule SRG-APP-000456-UEM-000330 CCI-002605 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:F
    SV-234622r617355_rule SRG-APP-000472-UEM-000347 CCI-002696 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
    SV-234623r617355_rule SRG-APP-000473-UEM-000348 CCI-002699 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
    SV-234624r617355_rule SRG-APP-000474-UEM-000349 CCI-002702 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
    SV-234629r617355_rule SRG-APP-000479-UEM-000354 CCI-002740 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 certificate
    SV-234642r617355_rule SRG-APP-000492-UEM-000367 CCI-000172 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
    SV-234645r617401_rule SRG-APP-000495-UEM-000370 CCI-000172 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 rec
    SV-234646r617355_rule SRG-APP-000496-UEM-000371 CCI-000172 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 rec
    SV-234649r617355_rule SRG-APP-000499-UEM-000374 CCI-000172 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 rec
    SV-234651r617355_rule SRG-APP-000501-UEM-000376 CCI-000172 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 rec
    SV-234653r617355_rule SRG-APP-000503-UEM-000378 CCI-000172 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 rec
    SV-234654r617355_rule SRG-APP-000504-UEM-000379 CCI-000172 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 rec
    SV-234655r617355_rule SRG-APP-000505-UEM-000380 CCI-000172 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 rec
    SV-234656r617355_rule SRG-APP-000506-UEM-000381 CCI-000172 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 rec
    SV-234657r617355_rule SRG-APP-000507-UEM-000382 CCI-000172 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 rec
    SV-234658r617355_rule SRG-APP-000508-UEM-000383 CCI-000172 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 rec
    SV-234659r617355_rule SRG-APP-000509-UEM-000384 CCI-000172 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 rec
    SV-234664r617355_rule SRG-APP-000514-UEM-000389 CCI-002450 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, th
    SV-234665r617355_rule SRG-APP-000515-UEM-000390 CCI-001851 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
    SV-234666r617355_rule SRG-APP-000516-UEM-000391 CCI-000366 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 p
    SV-234667r617355_rule SRG-APP-000516-UEM-000392 CCI-000366 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
    SV-234668r617355_rule SRG-APP-000555-UEM-000393 CCI-002450 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)
    SV-234669r617355_rule SRG-APP-000560-UEM-000394 CCI-001453 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
    SV-234673r617355_rule SRG-APP-000580-UEM-000398 CCI-001967 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 gre
    SV-234674r617355_rule SRG-APP-000585-UEM-000399 CCI-001967 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
    SV-234676r617355_rule SRG-APP-000605-UEM-000401 CCI-000185 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 entit
    SV-234677r617355_rule SRG-APP-000610-UEM-000402 CCI-000803 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 u