The vCenter Server must produce audit records containing information to establish what type of events occurred.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-256321 | VCSA-70-000034 | SV-256321r885574_rule | CCI-000130 | medium |
| Description | ||||
| Without establishing what types of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. | ||||
| STIG | Date | |||
| VMware vSphere 7.0 vCenter Security Technical Implementation Guide | 2023-12-21 | |||
Details
Check Text (C-256321r885574_chk)
From the vSphere Client, go to Host and Clusters.
Select a vCenter Server >> Configure >> Settings >> Advanced Settings.
Verify the "config.log.level" value is set to "info".
or
From a PowerCLI command prompt while connected to the vCenter server, run the following command:
Get-AdvancedSetting -Entity <vcenter server name> -Name config.log.level and verify it is set to "info".
If the "config.log.level" value is not set to "info" or does not exist, this is a finding.
Fix Text (F-59939r885573_fix)
From the vSphere Client, go to Host and Clusters.
Select a vCenter Server >> Configure >> Settings >> Advanced Settings.
Click "Edit Settings" and configure the "config.log.level" setting to "info".
or
From a PowerCLI command prompt while connected to the vCenter server, run the following command:
Get-AdvancedSetting -Entity <vcenter server name> -Name config.log.level | Set-AdvancedSetting -Value info