Details

The configuration file containing these name-value pairs is limited to a size of 1MB. If not limited, VMware tools in the guest OS 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.

Solution

From the vSphere Client select the Virtual Machine right click and go to Edit Settings >> VM Options Tab >> Advanced >> Configuration Parameters. Find the tools.setinfo.sizeLimit value and set it to 1048576. If the setting does not exist click ‘Add Row’ to add the setting to the virtual machine.

Note: The VM must be powered off to configure the advanced settings through the vSphere Client so it is recommended to configure these settings with PowerCLI as it can be done while the VM is powered on.

or

From a PowerCLI command prompt while connected to the ESXi host or vCenter server run the following command:

If the setting does not exist run:

Get-VM ‘VM Name’ | New-AdvancedSetting -Name tools.setinfo.sizeLimit -Value 1048576

If the setting exists run:

Get-VM ‘VM Name’ | Get-AdvancedSetting -Name tools.setinfo.sizeLimit | Set-AdvancedSetting -Value 1048576

Supportive Information

The following resource is also helpful.

• http://iasecontent.disa.mil/stigs/zip/U_VMware_vSphere_6-0_Virtual_Machine_V1R1_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system VMware.

References

• 800-53|CM-6b.
• CAT|III
• CCI|CCI-000366
• Group-ID|V-64109
• Rule-ID|SV-78599r1_rule
• STIG-ID|VMCH-06-000036
• Vuln-ID|V-64109

Source

• Tenable.com/audits