STIGQter: STIG Summary: VMware vSphere 6.7 vCenter Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 09 Mar 2021:

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

DISA Rule

SV-243098r719537_rule

Vulnerability Number

V-243098

Group Title

SRG-APP-000474

Rule Version

VCTR-67-000036

Severity

CAT II

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 Client, go to Hosts 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

Check Contents

From the vSphere Client, go to Hosts 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

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-243098

Documentable

False

Rule Version

VCTR-67-000036

Severity Override Guidance

From the vSphere Client, go to Hosts 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

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

5399

Comments