Skip to content

Unified Endpoint Management Server Security Requirements Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • 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 in...
    Rule Medium Severity
  • SRG-APP-000509

    Group
  • 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 in...
    Rule Medium Severity
  • SRG-APP-000514

    Group
  • 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 providi...
    Rule High Severity
  • SRG-APP-000515

    Group
  • 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. S...
    Rule Medium Severity
  • SRG-APP-000516

    Group
  • 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 baselin...
    Rule Medium Severity
  • SRG-APP-000516

    Group
  • 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 proficien...
    Rule Medium Severity
  • SRG-APP-000555

    Group
  • SRG-APP-000560

    Group
  • 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 requ...
    Rule Medium Severity
  • SRG-APP-000580

    Group
  • SRG-APP-000585

    Group
  • 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-shar...
    Rule Medium Severity
  • SRG-APP-000605

    Group
  • SRG-APP-000610

    Group
  • 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...
    Rule High Severity
  • SRG-APP-000427

    Group
  • 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 t...
    Rule High Severity
  • SRG-APP-000427

    Group
  • SRG-APP-000427

    Group
  • 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...
    Rule High Severity
  • 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 li...
    Rule Medium Severity
  • 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 temporar...
    Rule Medium Severity
  • 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 temporar...
    Rule Medium Severity
  • 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 com...
    Rule Medium Severity
  • 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...
    Rule Medium Severity
  • 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...
    Rule Medium Severity
  • 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 ...
    Rule Medium Severity
  • 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 ...
    Rule Medium Severity
  • 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 i...
    Rule Medium Severity
  • 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 proficien...
    Rule Medium Severity
  • 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 provid...
    Rule Medium Severity
  • 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 with...
    Rule Medium Severity
  • 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 ...
    Rule Medium Severity
  • 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 audi...
    Rule Medium Severity
  • 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 reco...
    Rule Medium Severity
  • 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...
    Rule Medium Severity
  • 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 protect...
    Rule Medium Severity
  • 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 uniq...
    Rule Medium Severity
  • 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 ...
    Rule High Severity
  • 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 resistin...
    Rule Medium Severity
  • 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 p...
    Rule Medium Severity
  • 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 all...
    Rule Medium Severity
  • 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 act...
    Rule Medium Severity
  • 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 act...
    Rule Medium Severity
  • 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 att...
    Rule High Severity

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.

Capacity
Modules