Skip to content

III - Administrative Classified

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000001

    <GroupDescription></GroupDescription>
    Group
  • The application must provide a capability to limit the number of logon sessions per user.

    &lt;VulnDiscussion&gt;Application management includes the ability to control the number of users and user sessions that utilize an application. Lim...
    Rule Medium Severity
  • SRG-APP-000295

    <GroupDescription></GroupDescription>
    Group
  • The application must clear temporary storage and cookies when the session is terminated.

    &lt;VulnDiscussion&gt;Persistent cookies are a primary means by which a web application will store application state and user information. Since H...
    Rule Medium Severity
  • SRG-APP-000295

    <GroupDescription></GroupDescription>
    Group
  • The application must automatically terminate the non-privileged user session and log off non-privileged users after a 15 minute idle time period has elapsed.

    &lt;VulnDiscussion&gt;Leaving a user’s application session established for an indefinite period of time increases the risk of session hijacking. S...
    Rule Medium Severity
  • SRG-APP-000295

    <GroupDescription></GroupDescription>
    Group
  • The application must automatically terminate the admin user session and log off admin users after a 10 minute idle time period is exceeded.

    &lt;VulnDiscussion&gt;Leaving an admin user's application session established for an indefinite period of time increases the risk of session hijack...
    Rule Medium Severity
  • SRG-APP-000296

    <GroupDescription></GroupDescription>
    Group
  • Applications requiring user access authentication must provide a logoff capability for user initiated communication session.

    &lt;VulnDiscussion&gt;If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker. Applica...
    Rule Medium Severity
  • SRG-APP-000297

    <GroupDescription></GroupDescription>
    Group
  • The application must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions.

    &lt;VulnDiscussion&gt;If a user is not explicitly notified that their application session has been terminated, they cannot be certain that their se...
    Rule Low Severity
  • SRG-APP-000311

    <GroupDescription></GroupDescription>
    Group
  • The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in storage.

    &lt;VulnDiscussion&gt;Without the association of security attributes to information, there is no basis for the application to make security related...
    Rule Medium Severity
  • SRG-APP-000313

    <GroupDescription></GroupDescription>
    Group
  • The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in process.

    &lt;VulnDiscussion&gt;Without the association of security attributes to information, there is no basis for the application to make security related...
    Rule Medium Severity
  • SRG-APP-000314

    <GroupDescription></GroupDescription>
    Group
  • The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission.

    &lt;VulnDiscussion&gt;Without the association of security attributes to information, there is no basis for the application to make security related...
    Rule Medium Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • The application must implement DoD-approved encryption to protect the confidentiality of remote access sessions.

    &lt;VulnDiscussion&gt;Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote...
    Rule Medium Severity
  • SRG-APP-000015

    <GroupDescription></GroupDescription>
    Group
  • The application must implement cryptographic mechanisms to protect the integrity of remote access sessions.

    &lt;VulnDiscussion&gt;Without integrity protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote acces...
    Rule Medium Severity
  • SRG-APP-000015

    <GroupDescription></GroupDescription>
    Group
  • Applications with SOAP messages requiring integrity must include the following message elements:-Message ID-Service Request-Timestamp-SAML Assertion (optionally included in messages) and all elements of the message must be digitally signed.

    &lt;VulnDiscussion&gt;Digitally signed SOAP messages provide message integrity and authenticity of the signer of the message independent of the tra...
    Rule Medium Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • Messages protected with WS_Security must use time stamps with creation and expiration times.

    &lt;VulnDiscussion&gt;The lack of time stamps could lead to the eventual replay of the message, leaving the application susceptible to replay event...
    Rule High Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • Validity periods must be verified on all application messages using WS-Security or SAML assertions.

    &lt;VulnDiscussion&gt;When using WS-Security in SOAP messages, the application should check the validity of the time stamps with creation and expir...
    Rule High Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • The application must ensure each unique asserting party provides unique assertion ID references for each SAML assertion.

    &lt;VulnDiscussion&gt;SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens c...
    Rule Medium Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • The application must ensure encrypted assertions, or equivalent confidentiality protections are used when assertion data is passed through an intermediary, and confidentiality of the assertion data is required when passing through the intermediary.

    &lt;VulnDiscussion&gt;SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens ...
    Rule Medium Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • The application must use the NotOnOrAfter condition when using the SubjectConfirmation element in a SAML assertion.

    &lt;VulnDiscussion&gt;SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens ...
    Rule High Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • The application must use both the NotBefore and NotOnOrAfter elements or OneTimeUse element when using the Conditions element in a SAML assertion.

    &lt;VulnDiscussion&gt;SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens ...
    Rule High Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • The application must ensure if a OneTimeUse element is used in an assertion, there is only one of the same used in the Conditions element portion of an assertion.

    &lt;VulnDiscussion&gt;Multiple &lt;OneTimeUse&gt; elements used in a SAML assertion can lead to elevation of privileges, if the application does no...
    Rule Medium Severity
  • SRG-APP-000014

    <GroupDescription></GroupDescription>
    Group
  • The application must ensure messages are encrypted when the SessionIndex is tied to privacy data.

    &lt;VulnDiscussion&gt;When the SessionIndex is tied to privacy data (e.g., attributes containing privacy data) the message should be encrypted. If ...
    Rule Medium Severity
  • SRG-APP-000023

    <GroupDescription></GroupDescription>
    Group
  • The application must provide automated mechanisms for supporting account management functions.

    &lt;VulnDiscussion&gt;Enterprise environments make application account management challenging and complex. A manual process for account management ...
    Rule Medium Severity
  • SRG-APP-000317

    <GroupDescription></GroupDescription>
    Group
  • Shared/group account credentials must be terminated when members leave the group.

    &lt;VulnDiscussion&gt;If shared/group account credentials are not terminated when individuals leave the group, the user that left the group can sti...
    Rule Medium Severity
  • SRG-APP-000024

    <GroupDescription></GroupDescription>
    Group
  • The application must automatically remove or disable temporary user accounts 72 hours after account creation.

    &lt;VulnDiscussion&gt;If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain...
    Rule Medium Severity
  • SRG-APP-000516

    <GroupDescription></GroupDescription>
    Group
  • The application must have a process, feature or function that prevents removal or disabling of emergency accounts.

    &lt;VulnDiscussion&gt;Emergency accounts are administrator accounts which are established in response to crisis situations where the need for rapid...
    Rule Low Severity
  • SRG-APP-000025

    <GroupDescription></GroupDescription>
    Group
  • The application must automatically disable accounts after a 35 day period of account inactivity.

    &lt;VulnDiscussion&gt;Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an applicatio...
    Rule Low 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