The LogLevel directive must be enabled.

From APACHE SITE 2.2 for Unix Security Technical Implementation Guide

Associated with IA controls: ECAR-1

SV-33207r1_rule The LogLevel directive must be enabled.

Vulnerability discussion

The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as “not found” or “unauthorized” errors that may be an evidence of attack attempts. Failure to enable error logging can significantly reduce the ability of Web Administrators to detect or remediate problems. While the ErrorLog directive configures the error log file name, the LogLevel directive is used to configure the severity level for the error logs. The log level values are the standard syslog levels: emerg, alert, crit, error, warn, notice, info and debug.

Check content

Enter the following command: grep "LogLevel" /usr/local/apache2/conf/httpd.conf The command should return the following value: LogLevel warn If the above value is not returned, this is a finding. Note: If LogLevel is set to error, crit, alert, or emerg which are higher thresholds this is not a finding.

Fix text

Edit the httpd.conf file and add the value LogLevel warn.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.