VMware ESXi
TMA-ESXI9-4.11
Host must use strict x509 verification for TLS-enabled remote logging endpoints
Description
When employing remote logging with TLS-enabled endpoints, it is essential to ensure the utmost integrity and authenticity of the certificates in use. The "x509-strict" option provides a higher level of security by performing additional validity checks on CA root certificates during the verification process. The audit reads Syslog.global.certificate.strictX509Compliance with esxcli and requires true (1). Runs in the ESXi Shell (busybox sh) as root.
How it is checked
Audit method: Shell command
out=$(esxcli system settings advanced list -o /Syslog/global/certificate/strictX509Compliance 2>/dev/null) || exit 1
v=$(printf '%s\n' "$out" | awk '$1=="Int" && $2=="Value:" {print $3; exit}')
case "$v" in ''|*[!0-9-]*) echo '/Syslog/global/certificate/strictX509Compliance: no integer value'; exit 1 ;; esac
if [ "$v" -eq 1 ]; then echo compliant; else echo "/Syslog/global/certificate/strictX509Compliance = $v (expected true/1)"; fi- Expected output
compliant
How it is fixed
Fix method: Guidance or infrastructure patch
Utilize PowerCLI to remediate </> Powershell Get-VMHost | Get-AdvancedSetting -Name "Syslog.global.certificate.strictX509Compliance" | Set-AdvancedSetting -Value $true -Confirm:$false Verify with Get-VMHost | Get-AdvancedSetting -Name "Syslog.global.certificate.strictX509Compliance" Expected Calue is: Value = True
Properties
- Operating systems
- Any
- Tags
- vmwareesxilogging
- Reference
- CIS VMware ESXi 9.0 Benchmark v1.0.0 - 4.11 Host must use strict x509 verification for TLS-enabled remote logging endpoints
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
tmaegis scan --target vmware