The Apache web server must produce log records containing sufficient information to establish what type of events occurred.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-214364	SRG-APP-000095-WSR-000056	AS24-W2-000090	SV-214364r962395_rule	2025-02-12	2

Description
Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. Ascertaining the correct type of event that occurred is important during forensic analysis. The correct determination of the event and when it occurred is important in relation to other events that happened at that same time. Without sufficient information establishing what type of log event occurred, investigation into the cause of event is severely hindered. Log record content that may be necessary to satisfy the requirement of this control includes but is not limited to time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, and flow control rules invoked. Satisfies: SRG-APP-000095-WSR-000056, SRG-APP-000098-WSR-000060, SRG-APP-000099-WSR-000061, SRG-APP-000100-WSR-000064

Description

Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined. Ascertaining the correct type of event that occurred is important during forensic analysis. The correct determination of the event and when it occurred is important in relation to other events that happened at that same time. Without sufficient information establishing what type of log event occurred, investigation into the cause of event is severely hindered. Log record content that may be necessary to satisfy the requirement of this control includes but is not limited to time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, file names involved, access control, and flow control rules invoked. Satisfies: SRG-APP-000095-WSR-000056, SRG-APP-000098-WSR-000060, SRG-APP-000099-WSR-000061, SRG-APP-000100-WSR-000064

ℹ️ Check
Review the access log file. If necessary, review the <'INSTALLED PATH'>\conf\httpd.conf file to determine the location of the logs. Items to be logged are as shown in this sample line in the <'INSTALLED PATH'>\conf\httpd.conf file: <IfModule log_config_module> LogFormat "%a %A %h %H %l %m %s %t %u %U \"%{Referer}i\" " combined </IfModule> If the web server is not configured to capture the required audit events for all sites and virtual directories, this is a finding.

ℹ️ Check

Review the access log file. If necessary, review the <'INSTALLED PATH'>\conf\httpd.conf file to determine the location of the logs. Items to be logged are as shown in this sample line in the <'INSTALLED PATH'>\conf\httpd.conf file: <IfModule log_config_module> LogFormat "%a %A %h %H %l %m %s %t %u %U \"%{Referer}i\" " combined </IfModule> If the web server is not configured to capture the required audit events for all sites and virtual directories, this is a finding.

✔️ Fix
Open the <'INSTALLED PATH'>\conf\httpd.conf file. Configure the "LogFormat" to look like the following within the <IfModule log_config_module> block: LogFormat "%a %A %h %H %l %m %s %t %u %U \"%{Referer}i\" " combined