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

Information

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 and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.

Application servers must log all relevant log data that pertains to application server functionality. Examples of relevant data include, but are not limited to, Java Virtual Machine (JVM) activity, HTTPD activity and application server-related system process activity.

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

Solution

1. Access EM
2. Expand the domain from the navigation tree, and select the server which needs JVM logging configured
3. Use the dropdown to select 'WebLogic Server' -> 'Logs' -> 'Log Configuration'
4. Select the 'Log Levels' tab, and within the table, expand 'Root Logger' node
5. Set 'Oracle Diagnostic Logging Level' value to 'WARNING' and click 'Apply'

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_WebLogic_Server_12c_V2R1_STIG.zip

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-3, CAT|III, CCI|CCI-000130, Rule-ID|SV-235943r628607_rule, STIG-ID|WBLC-02-000074, STIG-Legacy|SV-70489, STIG-Legacy|V-56235, Vuln-ID|V-235943

Plugin: Unix

Control ID: 5a1f1436da03fb4adacf195e5011fbfc917e3873aea451f14636c85be4ef0052