System logging must be enabled.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-214309	SRG-APP-000516-WSR-000174	AS24-W1-000065	SV-214309r961863_rule	2025-02-12	3

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 CustomLog directive specifies the log file, syslog facility, or piped logging utility.

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 CustomLog directive specifies the log file, syslog facility, or piped logging utility.

ℹ️ Check
In a command line, navigate to "<'INSTALLED PATH'>\bin\conf". Edit the "httpd.conf" file and search for the directive "CustomLog". If the "CustomLog" directive is missing or does not look like the following, this is a finding: CustomLog "Logs/access_log" common

✔️ Fix
Edit the httpd.conf file and enter the name, path, and level for the CustomLog.