Detections
Analytics
OH12-1X-000068 - OHS must have a log file defined for each site/virtual host to produce log records that contain sufficient information to establish the outcome (success or failure) of events.
Information
Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined.Ascertaining the success or failure of an event is important during forensic analysis. Correctly determining the outcome will add information to the overall reconstruction of the logable event. By determining the success or failure of the event correctly, analysis of the enterprise can be undertaken to determine if events tied to the event occurred in other areas within the enterprise.
Without sufficient information establishing the success or failure of the logged event, investigation into the cause of event is severely hindered. The success or failure also provides a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, or flow control rules invoked.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
1. Open $DOMAIN_HOME/config/fmwconfig/components/OHS/<componentName>/httpd.conf and every .conf file (e.g., ssl.conf) included in it with an editor that contains a '<VirtualHost>' directive.2. Search for the 'CustomLog' directive at the OHS server and virtual host configuration scopes.
3a. If the virtual host is NOT configured for SSL, set the 'CustomLog' directive to ''||${PRODUCT_HOME}/bin/odl_rotatelogs <DESIRED_DIRECTORY_AND_FILE_NAME> 43200' dod', add the directive if it does not exist unless inherited from a larger scope.
3b. If the virtual host is configured for SSL, set the 'CustomLog' directive to ''||${PRODUCT_HOME}/bin/odl_rotatelogs <DESIRED_DIRECTORY_AND_FILE_NAME> 43200' dod_ssl', add the directive if it does not exist unless inherited from a larger scope.
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_HTTP_Server_12-1-3_V2R2_STIG.zip
Item Details
Audit Name: DISA STIG Oracle HTTP Server 12.1.3 v2r2
Category: AUDIT AND ACCOUNTABILITY
References: 800-53|AU-3, CAT|II, CCI|CCI-000134, Rule-ID|SV-221330r879567_rule, STIG-ID|OH12-1X-000068, STIG-Legacy|SV-78717, STIG-Legacy|V-64227, Vuln-ID|V-221330
Plugin: Unix
Control ID: c192d6fca917a3c1cbf7f03e3bd679e43519065cedf52398984cf6a468667340