Skip to content
ATO Pathways
  Log In

I - Mission Critical Sensitive

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000219

    <GroupDescription></GroupDescription>
    Group
    Show

  • The UEM server must protect the authenticity of communications sessions.

    &lt;VulnDiscussion&gt;Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false in...
    Rule Medium Severity
    Show

  • SRG-APP-000220

    <GroupDescription></GroupDescription>
    Group
    Show

  • The UEM server must invalidate session identifiers upon user logout or other session termination.

    &lt;VulnDiscussion&gt;Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries from capturing and co...
    Rule Medium Severity
    Show

  • SRG-APP-000223

    <GroupDescription></GroupDescription>
    Group
    Show

  • The UEM server must recognize only system-generated session identifiers.

    &lt;VulnDiscussion&gt;Applications utilize sessions and session identifiers to control application behavior and user access. If an attacker can gue...
    Rule Medium Severity
    Show

  • SRG-APP-000224

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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.

    &lt;VulnDiscussion&gt;Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generatio...
    Rule High Severity
    Show

  • SRG-APP-000225

    <GroupDescription></GroupDescription>
    Group
    Show

  • The UEM server must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

    &lt;VulnDiscussion&gt;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
    Show

  • SRG-APP-000226

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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.

    &lt;VulnDiscussion&gt;Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Fa...
    Rule Medium Severity
    Show

  • SRG-APP-000251

    <GroupDescription></GroupDescription>
    Group
    Show

  • The UEM server must check the validity of all data inputs.

    &lt;VulnDiscussion&gt;Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application ...
    Rule Medium Severity
    Show

  • SRG-APP-000266

    <GroupDescription></GroupDescription>
    Group
    Show

  • The UEM server must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.

    &lt;VulnDiscussion&gt;Any application providing too much information in error messages risks compromising the data and security of the application ...
    Rule Medium Severity
    Show

  • SRG-APP-000267

    <GroupDescription></GroupDescription>
    Group
    Show

  • The UEM server must reveal error messages only to the Information System Security Manager (ISSM) and Information System Security Officer (ISSO).

    &lt;VulnDiscussion&gt;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
    Show

  • SRG-APP-000268

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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.

    &lt;VulnDiscussion&gt;Predictable failure prevention requires organizational planning to address system failure issues. If components key to mainta...
    Rule Medium Severity
    Show

Node 2

siemur/test-space

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