VMware vSphere 7.0 Virtual Machine STIG Version Comparison
VMware vSphere 7.0 Virtual Machine Security Technical Implementation Guide
Comparison
There are 2 differences between versions v1 r2 (July 26, 2023) (the "left" version) and v1 r4 (Jan. 30, 2025) (the "right" version).
Check VMCH-70-000015 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.
The regular view of the left check and right check may be easier to read.
Text Differences
Title
Informational messages from the virtual machine to the VMX file must be limited on the virtual machine (VM).
Check Content
From the vSphere Client, right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Verify the "tools.setinfo.sizeLimit" "tools.setInfo.sizeLimit" value is set to "1048576". or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the following command: Get-VM "VM Name" | Get-AdvancedSetting -Name tools.setinfo.sizeLimit If the virtual machine advanced setting "tools.setinfo.sizeLimit" "tools.setInfo.sizeLimit" does not exist or is not set to "1048576", this is a finding.
Discussion
The configuration file containing these name-value pairs is limited to a size of 1MB. If not limited, VMware tools in the guest operating system are capable of sending a large and continuous data stream to the host. This 1MB capacity should be sufficient for most cases, but this value can change if necessary. The value can be increased if large amounts of custom information are being stored in the configuration file. The default limit is 1MB.
Fix
From the vSphere Client, right-click the Virtual Machine and go to Edit Settings >> VM Options >> Advanced >> Configuration Parameters >> Edit Configuration. Find the "tools.setinfo.sizeLimit" "tools.setInfo.sizeLimit" value and set it to "1048576". If the setting does not exist, add the Name and Value setting at the bottom of screen. Note: The VM must be powered off to configure the advanced settings through the vSphere Client. Therefore, it is recommended to configure these settings with PowerCLI as this can be done while the VM is powered on. Settings do not take effect via either method until the virtual machine is cold started, not rebooted. or From a PowerCLI command prompt while connected to the ESXi host or vCenter server, run the provided commands as shown below. If the setting does not exist, run: Get-VM "VM Name" | New-AdvancedSetting -Name tools.setinfo.sizeLimit tools.setInfo.sizeLimit -Value 1048576 If the setting exists, run: Get-VM "VM Name" | Get-AdvancedSetting -Name tools.setinfo.sizeLimit tools.setInfo.sizeLimit | Set-AdvancedSetting -Value 1048576