STIGQter: STIG Summary: VMW vSphere 6.5 vCenter Server for Windows Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 22 Jan 2021:

The vCenter Server for Windows must produce audit records containing information to establish what type of events occurred.

DISA Rule

SV-216858r612237_rule

Vulnerability Number

V-216858

Group Title

SRG-APP-000474

Rule Version

VCWN-65-000036

Severity

CAT III

CCI(s)

• CCI-002702 - The information system shuts the information system down, restarts the information system, and/or initiates organization-defined alternative action(s) when anomalies in the operation of the organization-defined security functions are discovered.

Weight

10

Fix Recommendation

From the vSphere Web Client go to Host and Clusters >> Select a vCenter Server >> Configure >> Settings >> Advanced Settings. Click "Edit" and edit the "config.log.level" setting to "info" or if the value does not exist create it by entering the values in the "Key" and "Value" fields and clicking "Add".

or

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

If the setting already exists:
Get-AdvancedSetting -Entity <vcenter server name> -Name config.log.level | Set-AdvancedSetting -Value info

If the setting does not exist:
New-AdvancedSetting -Entity <vcenter server name> -Name config.log.level -Value info

Check Contents

From the vSphere Web Client go to Host and Clusters >> Select a vCenter Server >> Configure >> Settings >> Advanced Settings. Verify that "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.

Vulnerability Number

V-216858

Documentable

False

Rule Version

VCWN-65-000036

Severity Override Guidance

From the vSphere Web Client go to Host and Clusters >> Select a vCenter Server >> Configure >> Settings >> Advanced Settings. Verify that "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.

Check Content Reference

M

Target Key

4030

Comments