Skip to content

I - Mission Critical Sensitive

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000014-AS-000009

    Group
  • Oracle WebLogic must utilize cryptography to protect the confidentiality of remote access management sessions.

    Remote management access is accomplished by leveraging common communication protocols and establishing a remote connection to the application server via a network for the purposes of managing the a...
    Rule Medium Severity
  • SRG-APP-000015-AS-000010

    Group
  • Oracle WebLogic must use cryptography to protect the integrity of the remote access session.

    Encryption is critical for protection of remote access sessions. If encryption is not being used for integrity, malicious users may gain the ability to modify the application server configuration. ...
    Rule Medium Severity
  • SRG-APP-000516-AS-000237

    Group
  • Oracle WebLogic must employ automated mechanisms to facilitate the monitoring and control of remote access methods.

    Remote network access is accomplished by leveraging common communication protocols and establishing a remote connection. Application servers provide remote management access and need to provide t...
    Rule Medium Severity
  • SRG-APP-000016-AS-000013

    Group
  • Oracle WebLogic must ensure remote sessions for accessing security functions and security-relevant information are audited.

    Auditing must be utilized in order to track system activity, assist in diagnosing system issues and provide evidence needed for forensic investigations post security incident. Remote access by ad...
    Rule Medium Severity
  • SRG-APP-000142-AS-000014

    Group
  • Oracle WebLogic must support the capability to disable network protocols deemed by the organization to be non-secure except for explicitly identified components in support of specific operational requirements.

    Some networking protocols may not meet organizational security requirements to protect data and components. Application servers natively host a number of various features such as management inter...
    Rule Medium Severity
  • SRG-APP-000509-AS-000234

    Group
  • Oracle WebLogic must automatically audit account creation.

    Application servers require user accounts for server management purposes, and if the creation of new accounts is not logged, there is limited or no capability to track or alarm on account creation....
    Rule Medium Severity
  • SRG-APP-000509-AS-000234

    Group
  • Oracle WebLogic must automatically audit account modification.

    Once an attacker establishes initial access to a system, they often attempt to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply modify a...
    Rule Medium Severity
  • SRG-APP-000504-AS-000229

    Group
  • Oracle WebLogic must provide access logging that ensures users who are granted a privileged role (or roles) have their privileged activity logged.

    In order to be able to provide a forensic history of activity, the application server must ensure users who are granted a privileged role or those who utilize a separate distinct account when acces...
    Rule Medium Severity
  • SRG-APP-000516-AS-000237

    Group
  • Oracle WebLogic must limit the number of failed login attempts to an organization-defined number of consecutive invalid attempts that occur within an organization-defined time period.

    Anytime an authentication method is exposed so as to allow for the login to an application, there is a risk that attempts will be made to obtain unauthorized access. By limiting the number of fail...
    Rule Medium Severity
  • SRG-APP-000516-AS-000237

    Group
  • Oracle WebLogic must enforce the organization-defined time period during which the limit of consecutive invalid access attempts by a user is counted.

    By limiting the number of failed login attempts, the risk of unauthorized system access via automated user password guessing, otherwise known as brute-forcing, is reduced. Best practice requires a ...
    Rule Medium Severity
  • SRG-APP-000516-AS-000237

    Group
  • Oracle WebLogic must automatically lock accounts when the maximum number of unsuccessful login attempts is exceeded for an organization-defined time period or until the account is unlocked by an administrator.

    Anytime an authentication method is exposed so as to allow for the utilization of an application interface, there is a risk that attempts will be made to obtain unauthorized access. By locking the...
    Rule Medium Severity
  • SRG-APP-000080-AS-000045

    Group
  • Oracle WebLogic must protect against an individual falsely denying having performed a particular action.

    Non-repudiation of actions taken is required in order to maintain application integrity. Examples of particular actions taken by individuals include creating information, sending a message, approvi...
    Rule Medium Severity
  • SRG-APP-000086-AS-000048

    Group
  • Oracle WebLogic must compile audit records from multiple components within the system into a system-wide (logical or physical) audit trail that is time-correlated to within an organization-defined level of tolerance.

    Audit generation and audit records can be generated from various components within the application server. The list of audited events is the set of events for which audits are to be generated. This...
    Rule Low Severity
  • SRG-APP-000091-AS-000052

    Group
  • Oracle WebLogic must generate audit records for the DoD-selected list of auditable events.

    Audit records can be generated from various components within the application server. The list of audited events is the set of events for which audits are to be generated. This set of events is t...
    Rule Low Severity
  • SRG-APP-000095-AS-000056

    Group
  • Oracle WebLogic must produce process events and severity levels to establish what type of HTTPD-related events and severity levels occurred.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes time stamps, source...
    Rule Low Severity
  • SRG-APP-000095-AS-000056

    Group
  • Oracle WebLogic must produce audit records containing sufficient information to establish what type of JVM-related events and severity levels occurred.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes: time stamps, sour...
    Rule Low Severity
  • SRG-APP-000095-AS-000056

    Group
  • Oracle WebLogic must produce process events and security levels to establish what type of Oracle WebLogic process events and severity levels occurred.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes: time stamps, sour...
    Rule Low Severity
  • SRG-APP-000096-AS-000059

    Group
  • Oracle WebLogic must produce audit records containing sufficient information to establish when (date and time) the events occurred.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes time stamps, sourc...
    Rule Low Severity
  • SRG-APP-000097-AS-000060

    Group
  • Oracle WebLogic must produce audit records containing sufficient information to establish where the events occurred.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes time stamps, source...
    Rule Low Severity
  • SRG-APP-000098-AS-000061

    Group
  • Oracle WebLogic must produce audit records containing sufficient information to establish the sources of the events.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, but is not limited...
    Rule Low Severity
  • SRG-APP-000099-AS-000062

    Group
  • Oracle WebLogic must produce audit records that contain sufficient information to establish the outcome (success or failure) of application server and application events.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, but is not limite...
    Rule Low Severity
  • SRG-APP-000100-AS-000063

    Group
  • Oracle WebLogic must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes: time stamps, sour...
    Rule Medium Severity
  • SRG-APP-000515-AS-000203

    Group
  • Oracle WebLogic must provide the ability to write specified audit record content to an audit log server.

    Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, but is not limite...
    Rule Medium Severity
  • SRG-APP-000108-AS-000067

    Group
  • Oracle WebLogic must provide a real-time alert when organization-defined audit failure events occur.

    It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Audit processing failures include software/hardware errors, failures in...
    Rule Low Severity
  • SRG-APP-000108-AS-000067

    Group
  • Oracle WebLogic must alert designated individual organizational officials in the event of an audit processing failure.

    Audit processing failures include, but are not limited to, failures in the application server log capturing mechanisms or audit storage capacity being reached or exceeded. In some instances, it is...
    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