1. Home
  2. Security Hardening
  3. Oracle WebLogic Server 12C Windows V2R1
  4. WBLC-02-000062 – Oracle WebLogic must protect against an individual falsely denying having performed a particular action.

WBLC-02-000062 – Oracle WebLogic must protect against an individual falsely denying having performed a particular action.

Details

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, approving information (e.g., indicating concurrence or signing a contract), and receiving a message.

Non-repudiation protects individuals against later claims by an author of not having authored a particular document, a sender of not having transmitted a message, a receiver of not having received a message, or a signatory of not having signed a document.

Typical application server actions requiring non-repudiation will be related to application deployment among developer/users and administrative actions taken by admin personnel.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

1. Access EM
2. Select the domain from the navigation tree, and use the dropdown to select ‘WebLogic Domain’ -> ‘Security’ -> ‘Audit Policy’
3. Select ‘Oracle Platform Security Services’ from the ‘Audit Component Name’ dropdown
4. Beneath ‘Audit Policy Settings’ section, select ‘Custom’ from the ‘Audit Level’ dropdown
5. Once it is enabled, click the ‘Audit All Events’ button and ensure every checkbox is selected under the ‘Select For Audit’ column of the policy category table. Click ‘Apply’
6. If managed server or deployments do not appear in the list of log files, the ‘JRF Template’ must be applied to the server/cluster
7. Access EM
8. Select the server or cluster from the navigation tree
9. If the ‘Apply JRF Template’ button appears, click this button and wait for the confirmation message that the template has been successfully applied
10. Again, select the server or cluster from the navigation tree
11. Click the ‘Shut Down…’ button, and click ‘Shutdown’ in the confirmation popup. Wait for server or cluster to shut down
12. Click the ‘Start Up’ button for the server or cluster to start up again

Supportive Information

The following resource is also helpful.

This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Windows.

References

Source

Updated on July 16, 2022
Was this article helpful?

Related Articles