Virtual machines (VMs) must configure log size.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-258718	VMCH-80-000205	SV-258718r959010_rule		Medium

Description
The ESXi hypervisor maintains logs for each individual VM by default. These logs contain information including but not limited to power events, system failure information, tools status and activity, time sync, virtual hardware changes, vMotion migrations, and machine clones. By default, the size of these logs is unlimited, and they are only rotated on vMotion or power events. This can cause storage issues at scale for VMs that do not vMotion or power cycle often.

Description

The ESXi hypervisor maintains logs for each individual VM by default. These logs contain information including but not limited to power events, system failure information, tools status and activity, time sync, virtual hardware changes, vMotion migrations, and machine clones. By default, the size of these logs is unlimited, and they are only rotated on vMotion or power events. This can cause storage issues at scale for VMs that do not vMotion or power cycle often.

STIG	Date
VMware vSphere 8.0 Virtual Machine Security Technical Implementation Guide	2024-07-11

Details

Check Text ( C-62458r933213_chk )
For each virtual machine do the following: From the vSphere Client, right-click the Virtual Machine and go to Edit Settings >> Advanced Parameters. Verify the "log.rotateSize" value is set to "2048000". 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 log.rotateSize If the virtual machine advanced setting "log.rotateSize" is not set to "2048000", this is a finding. If the virtual machine advanced setting "log.rotateSize" does NOT exist, this is NOT a finding.

Check Text ( C-62458r933213_chk )

For each virtual machine do the following:

From the vSphere Client, right-click the Virtual Machine and go to Edit Settings >> Advanced Parameters.

Verify the "log.rotateSize" value is set to "2048000".

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 log.rotateSize

If the virtual machine advanced setting "log.rotateSize" is not set to "2048000", this is a finding.

If the virtual machine advanced setting "log.rotateSize" does NOT exist, this is NOT a finding.

Fix Text (F-62367r933214_fix)
For each virtual machine do the following: From the vSphere Client, right-click the Virtual Machine and go to Edit Settings >> Advanced Parameters. Find the "log.rotateSize" value and set it to "2048000". If the setting does not exist no action is needed. 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 log.rotateSize \| Set-AdvancedSetting -Value 2048000 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.

Fix Text (F-62367r933214_fix)

For each virtual machine do the following:

From the vSphere Client, right-click the Virtual Machine and go to Edit Settings >> Advanced Parameters.

Find the "log.rotateSize" value and set it to "2048000".

If the setting does not exist no action is needed.

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 log.rotateSize | Set-AdvancedSetting -Value 2048000

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.