Detections
Analytics

OH12-1X-000206 - OHS must have the RewriteLog directive set properly.

Information

Specifying where the log files are written gives the system administrator the capability to store the files in a location other than the default, with system files or in a globally accessible location. The system administrator can also specify a location that is accessible by any enterprise tools that may use the logged data to give a picture of the overall enterprise security posture. If a file is not specified, OHS will still generate the log data, but it is not written and therefore, cannot be used to monitor the system or for forensic analysis.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

1. As required, 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 'RewriteLog' directive at the OHS server and virtual host configuration scopes.

3. Set the 'RewriteLog' directive to the same location as the 'CustomLog' directive; 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_V2R3_STIG.zip

Item Details

Category: CONFIGURATION MANAGEMENT

References: 800-53|CM-6b., CAT|III, CCI|CCI-000366, Rule-ID|SV-221444r961863_rule, STIG-ID|OH12-1X-000206, STIG-Legacy|SV-79141, STIG-Legacy|V-64651, Vuln-ID|V-221444

Plugin: Unix

Control ID: 8ada05787c386314e377425423d2ddf3ea1db2211639c583b9984b9b4d14951b