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

Remote logging for ESXi hosts must be configured.

DISA Rule

SV-239261r674712_rule

Vulnerability Number

V-239261

Group Title

SRG-OS-000032-VMM-000130

Rule Version

ESXI-67-000004

Severity

CAT II

CCI(s)

• CCI-000067 - The information system monitors remote access methods.
• CCI-001851 - The information system off-loads audit records per organization-defined frequency onto a different system or media than the system being audited.

Weight

10

Fix Recommendation

From the vSphere Client, select the ESXi host and go to Configure >> System >> Advanced System Settings.

Click "Edit", select the "Syslog.global.logHost" value, and configure it to a site-specific syslog server.

or

From a PowerCLI command prompt while connected to the ESXi host, run the following commands:

Get-VMHost | Get-AdvancedSetting -Name Syslog.global.logHost | Set-AdvancedSetting -Value "<syslog server hostname>"

Check Contents

From the vSphere Client, select the ESXi host and go to Configure >> System >> Advanced System Settings.

Select the "Syslog.global.logHost" value and verify it is set to a site-specific syslog server hostname.

or

From a PowerCLI command prompt while connected to the ESXi host, run the following command:

Get-VMHost | Get-AdvancedSetting -Name Syslog.global.logHost

If the "Syslog.global.logHost" setting is not set to a site-specific syslog server, this is a finding.

Vulnerability Number

V-239261

Documentable

False

Rule Version

ESXI-67-000004

Severity Override Guidance

From the vSphere Client, select the ESXi host and go to Configure >> System >> Advanced System Settings.

Select the "Syslog.global.logHost" value and verify it is set to a site-specific syslog server hostname.

or

From a PowerCLI command prompt while connected to the ESXi host, run the following command:

Get-VMHost | Get-AdvancedSetting -Name Syslog.global.logHost

If the "Syslog.global.logHost" setting is not set to a site-specific syslog server, this is a finding.

Check Content Reference

M

Target Key

5326

Comments