STIGQter STIGQter: STIG Summary: VMware vSphere 8.0 ESXi Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 31 Oct 2023:

The ESXi host must enable strict x509 verification for SSL syslog endpoints.

DISA Rule

SV-258789r933428_rule

Vulnerability Number

V-258789

Group Title

SRG-OS-000480-VMM-002000

Rule Version

ESXI-80-000234

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

From the vSphere Client, go to Hosts and Clusters.

Select the ESXi Host >> Configure >> System >> Advanced System Settings.

Click "Edit". Select the "Syslog.global.certificate.strictX509Compliance" value and configure it to "true".

or

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

Get-VMHost | Get-AdvancedSetting -Name Syslog.global.certificate.strictX509Compliance | Set-AdvancedSetting -Value "true"

Check Contents

If SSL is not used for a syslog target, this is not applicable.

From the vSphere Client, go to Hosts and Clusters.

Select the ESXi Host >> Configure >> System >> Advanced System Settings.

Select the "Syslog.global.certificate.strictX509Compliance" value and verify it is set to "true".

or

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

Get-VMHost | Get-AdvancedSetting -Name Syslog.global.certificate.strictX509Compliance

If the "Syslog.global.certificate.strictX509Compliance" setting is not set to "true", this is a finding.

Vulnerability Number

V-258789

Documentable

False

Rule Version

ESXI-80-000234

Severity Override Guidance

If SSL is not used for a syslog target, this is not applicable.

From the vSphere Client, go to Hosts and Clusters.

Select the ESXi Host >> Configure >> System >> Advanced System Settings.

Select the "Syslog.global.certificate.strictX509Compliance" value and verify it is set to "true".

or

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

Get-VMHost | Get-AdvancedSetting -Name Syslog.global.certificate.strictX509Compliance

If the "Syslog.global.certificate.strictX509Compliance" setting is not set to "true", this is a finding.

Check Content Reference

M

Target Key

5562