Apache Server 2.4 UNIX Server STIG:
(in versions v2 r4 through v1 r3)
The Apache web server must have system logging enabled. (Cat II impact)
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 CustomLog directive specifies the log file, syslog facility, or piped logging utility.
Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file: # httpd -V | egrep -i 'httpd_root|server_config_file' -D HTTPD_ROOT="/etc/httpd" -D SERVER_CONFIG_FILE="conf/httpd.conf" Search for the directive "CustomLog" in the "httpd.conf" file: # cat /<path_to_file>/httpd.conf | grep -i "CustomLog" If the "CustomLog" directive is missing, this is a finding: An example CustomLog directive would be as follows: CustomLog "logs/access_log" common or CustomLog “log/access_log” combined (May also be "Logs/access_log")
Edit the "httpd.conf" file and enter the name, path and level for the CustomLog.
Rule ID: SV-214231r612240_rule
Vulnerability ID: V-214231
Group Title: SRG-APP-000516-WSR-000174
The organization implements the security configuration settings.