VAMI 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-256650 | SRG-APP-000095-WSR-000056 | VCLD-70-000006 | SV-256650r888472_rule | 2023-06-15 | 1 |
Description
After a security incident has occurred, investigators will often review log files to determine what happened. Understanding what type of event occurred is critical for investigation of a suspicious event.
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, SRG-APP-000374-WSR-000172, SRG-APP-000375-WSR-000171
ℹ️ Check
At the command prompt, run the following command:
# /opt/vmware/sbin/vami-lighttpd -p -f /opt/vmware/etc/lighttpd/lighttpd.conf 2>/dev/null|grep "accesslog.format"|sed -e 's/^[ ]*//'
The default commented, "accesslog" format is acceptable for this requirement. No output should be returned.
If the command returns any output, this is a finding.
Note: The command must be run from a bash shell and not from a shell generated by the "appliance shell". Use the "chsh" command to change the shell for the account to "/bin/bash". Refer to KB Article 2100508 for more details:
https://kb.vmware.com/s/article/2100508
✔️ Fix
Navigate to and open:
/opt/vmware/etc/lighttpd/lighttpd.conf
Comment any existing "accesslog.format" lines by adding a "#" at the beginning of the line.
Restart the service with the following command:
# vmon-cli --restart applmgmt