I - Mission Critical Sensitive
Rules and Groups employed by this XCCDF Profile
-
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
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.