No profile (default benchmark)
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000168
<GroupDescription></GroupDescription>Group -
The UEM server must enforce password complexity by requiring that at least one numeric character be used.
<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, ...Rule Medium Severity -
SRG-APP-000169
<GroupDescription></GroupDescription>Group -
The UEM server must enforce password complexity by requiring that at least one special character be used.
<VulnDiscussion>Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, ...Rule Medium Severity -
SRG-APP-000170
<GroupDescription></GroupDescription>Group -
The UEM server must require the change of at least 15 of the total number of characters when passwords are changed.
<VulnDiscussion>If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of pass...Rule Medium Severity -
SRG-APP-000171
<GroupDescription></GroupDescription>Group -
For UEM server using password authentication, the application must store only cryptographic representations of passwords.
<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are...Rule Medium Severity -
SRG-APP-000172
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are...Rule High Severity -
SRG-APP-000174
<GroupDescription></GroupDescription>Group -
The UEM server must enforce a 60-day maximum password lifetime restriction.
<VulnDiscussion>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals...Rule Medium Severity -
SRG-APP-000175
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate n...Rule Medium Severity -
SRG-APP-000175
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>When an UEM server accepts an unverified certificate, it may be trusting a malicious actor. For example, messages signed with...Rule Medium Severity -
SRG-APP-000176
<GroupDescription></GroupDescription>Group -
The UEM server, when using PKI-based authentication, must enforce authorized access to the corresponding private key.
<VulnDiscussion>If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the ne...Rule Medium Severity -
SRG-APP-000177
<GroupDescription></GroupDescription>Group -
The UEM server must map the authenticated identity to the individual user or group account for PKI-based authentication.
<VulnDiscussion>Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the indivi...Rule Medium Severity -
SRG-APP-000178
<GroupDescription></GroupDescription>Group -
The UEM server must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
<VulnDiscussion>To prevent the compromise of authentication information such as passwords during the authentication process, the feedback fro...Rule Medium Severity -
SRG-APP-000179
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Nonlocal ma...Rule High Severity -
SRG-APP-000191
<GroupDescription></GroupDescription>Group -
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].
<VulnDiscussion>Examples of authorized IT entities: audit server, Active Directory, software update server, and database server. Without con...Rule Medium Severity -
SRG-APP-000191
<GroupDescription></GroupDescription>Group -
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].
<VulnDiscussion>Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote...Rule Medium Severity -
SRG-APP-000191
<GroupDescription></GroupDescription>Group -
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].
<VulnDiscussion>Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote...Rule Medium Severity -
SRG-APP-000219
<GroupDescription></GroupDescription>Group -
The UEM server must protect the authenticity of communications sessions.
<VulnDiscussion>Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false in...Rule Medium Severity -
SRG-APP-000220
<GroupDescription></GroupDescription>Group -
The UEM server must invalidate session identifiers upon user logout or other session termination.
<VulnDiscussion>Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries from capturing and co...Rule Medium Severity -
SRG-APP-000223
<GroupDescription></GroupDescription>Group -
The UEM server must recognize only system-generated session identifiers.
<VulnDiscussion>Applications utilize sessions and session identifiers to control application behavior and user access. If an attacker can gue...Rule Medium Severity -
SRG-APP-000224
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generatio...Rule High Severity -
SRG-APP-000225
<GroupDescription></GroupDescription>Group -
The UEM server must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
<VulnDiscussion>Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized acces...Rule Medium Severity -
SRG-APP-000226
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Fa...Rule Medium Severity -
SRG-APP-000251
<GroupDescription></GroupDescription>Group -
The UEM server must check the validity of all data inputs.
<VulnDiscussion>Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application ...Rule Medium Severity -
SRG-APP-000266
<GroupDescription></GroupDescription>Group -
The UEM server must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.
<VulnDiscussion>Any application providing too much information in error messages risks compromising the data and security of the application ...Rule Medium Severity -
SRG-APP-000267
<GroupDescription></GroupDescription>Group -
The UEM server must reveal error messages only to the Information System Security Manager (ISSM) and Information System Security Officer (ISSO).
<VulnDiscussion>Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an orga...Rule Medium Severity -
SRG-APP-000275
<GroupDescription></GroupDescription>Group -
The application must notify the Information System Security Manager (ISSM) and Information System Security Officer (ISSO) of failed security verification tests.
<VulnDiscussion>If personnel are not notified of failed security verification tests, they will not be able to take corrective action and the ...Rule Medium Severity
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.