The sites error logs must log the correct format.

From APACHE 2.2 Site for UNIX Security Technical Implementation Guide

SV-33203r1_rule The sites error logs must log the correct format.

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. The LogFormat directive defines the format and information to be included in the access log entries.

Check content

Enter the following command: grep "LogFormat" /usr/local/apache2/conf/httpd.conf. The command should return the following value: LogFormat "%a %A %h %H %l %m %s %t %u %U \"%{Referer}i\" " combined. If the above value is not returned, this is a finding.

Fix text

Edit the httpd.conf file and add LogFormat "%a %A %h %H %l %m %s %t %u %U \"%{Referer}i\" " combined

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.