Oracle WebLogic Server 12c Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-APP-000016-AS-000013
Group -
SRG-APP-000153-AS-000104
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
Oracle WebLogic must use internal system clocks to generate time stamps for audit records.
Without the use of an approved and synchronized time source, configured on the systems, events cannot be accurately correlated and analyzed to determine what is transpiring within the application s...Rule Low Severity -
Oracle WebLogic must protect audit tools from unauthorized modification.
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may ...Rule Medium Severity -
Oracle WebLogic must authenticate users individually prior to using a group authenticator.
To assure individual accountability and prevent unauthorized access, application server users (and any processes acting on behalf of application server users) must be individually identified and au...Rule High Severity -
Oracle WebLogic must enforce password complexity by the number of special characters used.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Use of a complex password helps to increase the time a...Rule Medium Severity -
Oracle WebLogic must use cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance when encrypting stored data.
Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon to provide confidentiality or integrity, and D...Rule Medium Severity -
Oracle WebLogic must employ strong identification and authentication techniques when establishing nonlocal maintenance and diagnostic sessions.
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network....Rule Medium Severity -
Oracle WebLogic must utilize NSA-approved cryptography when protecting classified compartmentalized data.
Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data. Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to ...Rule Medium Severity -
Oracle WebLogic must separate hosted application functionality from Oracle WebLogic management functionality.
Application server management functionality includes functions necessary to administer the application server and requires privileged access via one of the accounts assigned to a management role. ...Rule Medium Severity -
Oracle WebLogic must be configured to perform complete application deployments.
Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. When an appli...Rule Medium Severity -
Oracle WebLogic must fail securely in the event of an operational failure.
Fail secure is a condition achieved by the application server in order to ensure that in the event of an operational failure, the system does not enter into an unsecure state where intended securi...Rule Medium Severity -
Oracle WebLogic must employ approved cryptographic mechanisms when transmitting sensitive data.
Preventing the disclosure of transmitted information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over the...Rule Medium Severity -
Oracle WebLogic must only generate error messages that provide information necessary for corrective actions without revealing sensitive or potentially harmful information in error logs and administrative messages.
Any application providing too much information in error logs and in administrative messages to the screen risks compromising the data and security of the application and system. The structure and c...Rule Medium Severity -
Oracle WebLogic must be integrated with a tool to monitor audit subsystem failure notification information that is sent out (e.g., the recipients of the message and the nature of the failure).
It is critical that, when a system is at risk of failing to process audit logs, it detects and takes action to mitigate the failure. As part of the mitigation, the system must send a notification ...Rule Medium Severity -
SRG-APP-000014-AS-000009
Group -
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 -
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 -
SRG-APP-000516-AS-000237
Group -
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 -
SRG-APP-000086-AS-000048
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-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
Node 2
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.