Details
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-000096-WSR-000057, SRG-APP-000097-WSR-000058, SRG-APP-000098-WSR-000059, SRG-APP-000099-WSR-000061, SRG-APP-000100-WSR-000064
Solution
Configure the ‘LogFormat’ in the ‘httpd.conf’ file to look like the following:
LogFormat ‘%a %A %h %H %l %m %s %t %u %U ‘%{Referer}i’ ‘ combined
Restart the Apache service.
NOTE: Your log format may be using different variables based on your environment, however, it should be verified to be producing the same end result of logged elements.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Windows.
References
- 800-53|AU-3
- CAT|II
- CCI|CCI-000130
- CCI|CCI-000131
- CCI|CCI-000132
- CCI|CCI-000133
- CCI|CCI-000134
- CCI|CCI-001487
- Rule-ID|SV-214311r505936_rule
- STIG-ID|AS24-W1-000090
- STIG-Legacy|SV-102431
- STIG-Legacy|V-92343
- Vuln-ID|V-214311