The sites error logs must log the correct format.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-26280 | WA00612 A22 | SV-33203r1_rule | - | medium |
| Description | ||||
| 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. | ||||
| STIG | Date | |||
| APACHE 2.2 Site for UNIX Security Technical Implementation Guide | 2019-01-07 | |||
Details
Check Text (C-33203r1_chk)
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 (F-29379r1_fix)
Edit the httpd.conf file and add LogFormat "%a %A %h %H %l %m %s %t %u %U \"%{Referer}i\" " combined