STIGhubSTIGhub
STIGsSearchCompare

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
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to VMware vSphere 7.0 VAMI Security Technical Implementation Guide

V-256650

CAT II (Medium)

VAMI must produce log records containing sufficient information to establish what type of events occurred.

Rule ID

SV-256650r888472_rule

STIG

VMware vSphere 7.0 VAMI Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000130, CCI-000131, CCI-000132, CCI-000133, CCI-000134, CCI-001487, CCI-001889, CCI-001890

Discussion

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 Content

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 Text

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