STIGhubSTIGhub
STIGsSearchCompareAbout

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Apache Server 2.4 Windows Server Security Technical Implementation Guide

V-214309

CAT II (Medium)

System logging must be enabled.

Rule ID

SV-214309r961863_rule

STIG

Apache Server 2.4 Windows Server Security Technical Implementation Guide

Version

V3R4

CCIs

CCI-000366

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

Check Content

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 Text

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