Skip to content

I - Mission Critical Sensitive

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000025

    Group
  • Unnecessary application accounts must be disabled, or deleted.

    Test or demonstration accounts are sometimes created during the application installation process. This creates a security risk as these accounts often remain after the initial installation process ...
    Rule Medium Severity
  • SRG-APP-000026

    Group
  • The application must automatically audit account creation.

    Once an attacker establishes initial 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 simpl...
    Rule Medium Severity
  • SRG-APP-000027

    Group
  • The application must automatically audit account modification.

    One way for an attacker to establish persistent access is for the attacker to modify or copy an existing account. Auditing of account modification is one method for mitigating this risk. A comprehe...
    Rule Medium Severity
  • SRG-APP-000028

    Group
  • The application must automatically audit account disabling actions.

    When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. I...
    Rule Medium Severity
  • SRG-APP-000029

    Group
  • The application must automatically audit account removal actions.

    When application accounts are removed, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In...
    Rule Medium Severity
  • SRG-APP-000291

    Group
  • The application must notify system administrators (SAs) and information system security officers (ISSOs) when accounts are created.

    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 create...
    Rule Low Severity
  • SRG-APP-000292

    Group
  • The application must notify system administrators (SAs) and information system security officers (ISSOs) when accounts are modified.

    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 create...
    Rule Low Severity
  • SRG-APP-000293

    Group
  • The application must notify system administrators (SAs) and information system security officers (ISSOs) of account disabling actions.

    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 create...
    Rule Low Severity
  • SRG-APP-000294

    Group
  • The application must notify system administrators (SAs) and information system security officers (ISSOs) of account removal actions.

    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 remove an acc...
    Rule Low Severity
  • SRG-APP-000319

    Group
  • The application must automatically audit account enabling actions.

    When application accounts are enabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In...
    Rule Medium Severity
  • SRG-APP-000320

    Group
  • The application must notify system administrators (SAs) and information system security officers (ISSOs) of account enabling actions.

    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 enable an acc...
    Rule Low Severity
  • SRG-APP-000323

    Group
  • Application data protection requirements must be identified and documented.

    Failure to protect organizational information from data mining may result in a compromise of information. In order to assign the appropriate data protections, application data must be identified an...
    Rule Medium Severity
  • SRG-APP-000324

    Group
  • The application must utilize organization-defined data mining detection techniques for organization-defined data storage objects to adequately detect data mining attempts.

    Failure to protect organizational information from data mining may result in a compromise of information. Data mining occurs when the application is programmatically probed and data is automatical...
    Rule Medium Severity
  • SRG-APP-000033

    Group
  • The application must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

    To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., networks, web servers, and web porta...
    Rule High Severity
  • SRG-APP-000328

    Group
  • The application must enforce organization-defined discretionary access control policies over defined subjects and objects.

    Discretionary Access Control allows users to determine who is allowed to access their data. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued ce...
    Rule Medium Severity
  • SRG-APP-000038

    Group
  • The application must enforce approved authorizations for controlling the flow of information within the system based on organization-defined information flow control policies.

    A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, ...
    Rule Medium Severity
  • SRG-APP-000039

    Group
  • The application must enforce approved authorizations for controlling the flow of information between interconnected systems based on organization-defined information flow control policies.

    A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, ...
    Rule Medium Severity
  • SRG-APP-000340

    Group
  • The application must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.

    Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. Privileg...
    Rule Medium Severity
  • SRG-APP-000342

    Group
  • The application must execute without excessive account permissions.

    Applications are often designed to utilize a user account. The account represents a means to control application permissions and access to OS resources, application resources or both. When the ...
    Rule High Severity
  • SRG-APP-000343

    Group
  • The application must audit the execution of privileged functions.

    Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and...
    Rule Medium Severity
  • SRG-APP-000065

    Group
  • The application must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.

    By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the ...
    Rule High Severity
  • SRG-APP-000345

    Group
  • The application administrator must follow an approved process to unlock locked user accounts.

    Once a user account has been locked, it must be unlocked by an administrator. An ISSM and ISSO approved process must be created and followed to ensure the user requesting access is properly authen...
    Rule Medium Severity
  • SRG-APP-000068

    Group
  • The application 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 Low Severity
  • SRG-APP-000069

    Group
  • The application must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access.

    The banner must be acknowledged by the user prior to allowing the user access to the application. This provides assurance that the user has seen the message and accepted the conditions for access. ...
    Rule Low Severity
  • SRG-APP-000070

    Group
  • The publicly accessible application must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the application.

    Display of a standardized and approved use notification before granting access to the publicly accessible application ensures privacy and security notification verbiage used is consistent with appl...
    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