CIS VMware vCenter 8 Benchmark

Secure configuration guidelines for VMware vCenter Server 8

v1.0.0 May 2026

Overview

▶

This CIS Benchmark provides prescriptive guidance for establishing a secure configuration posture for VMware vCenter Server 8. Recommendations cover SSO policies, role-based access, network security policies, distributed virtual switch hardening, VM isolation settings, syslog forwarding, TLS configuration, certificate management, and service hardening.

~170Recommendations
5Sections
2Profile Levels
SectionAreaFocus
1IdentitySSO policies, roles, permissions
2NetworkSwitch security, VLAN, firewall, SSH
3VM HardeningIsolation, resources, devices
4LoggingSyslog, log level, NTP
5SecurityTLS, certificates, services

Profile Definitions

▶
ProfileDescriptionIntended Use
L1Level 1 — StandardEssential security for all VMware vCenter 8 deployments; minimal performance impact.
L2Level 2 — HardenedAdvanced hardening for PCI-DSS, HIPAA, or high-security environments.

1 — Identity & Access

▶

1.1 SSO & Identity

▶
1.1.1 Ensure SSO Password Policy Enforces Complexity (Automated)
L1 Auto
Description

This recommendation verifies that SSO Password Policy Enforces Complexity on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Connect-SsoAdminServer -Server <vcenter> -User administrator@vsphere.local
Get-SsoPasswordPolicy | Select MinLength, MaxLength, MinAlphabeticCount, MinUppercaseCount, MinLowercaseCount, MinNumericCount, MinSpecialCharCount
Remediation
# PowerCLI — Set SSO password policy:
Get-SsoPasswordPolicy | Set-SsoPasswordPolicy -MinLength 15 -MaxLength 64 -MinUppercaseCount 1 -MinLowercaseCount 1 -MinNumericCount 1 -MinSpecialCharCount 1
1.1.2 Ensure SSO Account Lockout Policy Is Configured (Automated)
L1 Auto
Description

This recommendation verifies that SSO Account Lockout Policy Is Configured on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-SsoLockoutPolicy | Select MaxFailedAttempts, AutoUnlockIntervalInSeconds, FailedAttemptIntervalInSeconds
# MaxFailedAttempts should be <= 5
Remediation
# PowerCLI — Set SSO lockout policy:
Get-SsoLockoutPolicy | Set-SsoLockoutPolicy -MaxFailedAttempts 5 -AutoUnlockIntervalInSeconds 300 -FailedAttemptIntervalInSeconds 180
1.1.3 Ensure SSO Password Expiry Is Configured (Automated)
L1 Auto
Description

This recommendation verifies that SSO Password Expiry Is Configured on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-SsoPasswordPolicy | Select PasswordLifetimeDays, ProhibitedPreviousPasswordsCount
# PasswordLifetimeDays should be <= 90
Remediation
# PowerCLI — Set password expiry:
Get-SsoPasswordPolicy | Set-SsoPasswordPolicy -PasswordLifetimeDays 90 -ProhibitedPreviousPasswordsCount 5
1.1.4 Ensure External Identity Source Is Configured (Manual)
L1 Manual
Description

This recommendation verifies that External Identity Source Is Configured on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# VAMI (https://<vcenter>:5480):
# Administration > Identity Sources
# Verify Active Directory or LDAPS is configured

# PowerCLI:
Get-IdentitySource | Select Name, Type, FriendlyName
Remediation
# PowerCLI — Add AD identity source:
Add-LDAPIdentitySource -Name 'corp.local' -DomainName 'corp.local' -DomainAlias 'CORP' -PrimaryUrl 'ldaps://dc.corp.local:636' -BaseDNUsers 'dc=corp,dc=local' -BaseDNGroups 'dc=corp,dc=local' -ServerType ActiveDirectory -Certificates (Get-Content ad-cert.pem)

1.2 Roles & Permissions

▶
1.2.1 Ensure Administrator Role Membership Is Reviewed (Manual)
L1 Manual
Description

This recommendation verifies that Administrator Role Membership Is Reviewed on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VIPermission | Where-Object {$_.Role -eq 'Admin'} | Select Principal, Entity, Propagate | Format-Table
# Review users with Administrator role — should be minimal
Remediation
# PowerCLI — Remove unnecessary admin permissions:
Get-VIPermission | Where-Object {$_.Principal -eq 'DOMAIN\\user' -and $_.Role -eq 'Admin'} | Remove-VIPermission -Confirm:$false

# Create custom role with least privilege:
New-VIRole -Name 'CustomVMAdmin' -Privilege (Get-VIPrivilege -Id 'VirtualMachine.Interact.*')
1.2.2 Ensure No Permissions Are Assigned to Everyone (Automated)
L1 Auto
Description

This recommendation verifies that No Permissions Are Assigned to Everyone on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VIPermission | Where-Object {$_.Principal -eq 'Everyone'} | Format-Table
# No permissions should be assigned to 'Everyone'
Remediation
# PowerCLI — Remove 'Everyone' permissions:
Get-VIPermission | Where-Object {$_.Principal -eq 'Everyone'} | Remove-VIPermission -Confirm:$false
1.2.3 Ensure Custom Roles Follow Least Privilege (Manual)
L1 Manual
Description

This recommendation verifies that Custom Roles Follow Least Privilege on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VIRole | Where-Object {$_.IsSystem -eq $false} | Select Name, PrivilegeList | Format-Table
# Review custom roles for excessive privileges
Remediation
# PowerCLI — Remove excessive privileges from a role:
Set-VIRole -Role 'CustomRole' -RemovePrivilege (Get-VIPrivilege -Id 'Host.Config.*')

2 — Network Security

▶

2.1 Network Configuration

▶
2.1.1 Ensure Promiscuous Mode Is Rejected (Automated)
L1 Auto
Description

This recommendation verifies that Promiscuous Mode Is Rejected on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VMHost | Get-VirtualSwitch -Standard | Get-SecurityPolicy | Select VirtualSwitch, AllowPromiscuous, ForgedTransmits, MacChanges
# AllowPromiscuous should be false
Remediation
# PowerCLI — Reject promiscuous mode:
Get-VMHost | Get-VirtualSwitch -Standard | Get-SecurityPolicy | Set-SecurityPolicy -AllowPromiscuous $false -ForgedTransmits $false -MacChanges $false
2.1.2 Ensure VDS Security Policies Reject Promiscuous Mode (Automated)
L1 Auto
Description

This recommendation verifies that VDS Security Policies Reject Promiscuous Mode on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VDSwitch | Get-VDSecurityPolicy | Select VDSwitch, AllowPromiscuous, ForgedTransmits, MacChanges
# All should be false
Remediation
# PowerCLI — Set VDS security policy:
Get-VDSwitch | Get-VDSecurityPolicy | Set-VDSecurityPolicy -AllowPromiscuous $false -ForgedTransmits $false -MacChanges $false
2.1.3 Ensure VMs Are Not on Native VLAN (Manual)
L1 Manual
Description

This recommendation verifies that VMs Are Not on Native VLAN on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VMHost | Get-VirtualSwitch -Standard | Get-VirtualPortGroup | Select Name, VLanId
# Verify no VMs on VLAN 1 (default/native VLAN)
Remediation
# PowerCLI — Change VLAN assignment from native VLAN:
Get-VirtualPortGroup -Name 'VM Network' | Set-VirtualPortGroup -VLanId 100

2.2 Firewall & Services

▶
2.2.1 Ensure Unnecessary Firewall Rules Are Disabled (Manual)
L1 Manual
Description

This recommendation verifies that Unnecessary Firewall Rules Are Disabled on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VMHost | Get-VMHostFirewallException | Where-Object {$_.Enabled} | Select Name, ServiceRunning, IncomingPorts, OutgoingPorts | Format-Table
# Review enabled firewall rules
Remediation
# PowerCLI — Disable unnecessary firewall rules:
Get-VMHost | Get-VMHostFirewallException -Name 'SSH Server' | Set-VMHostFirewallException -Enabled $false
2.2.2 Ensure SSH Service Is Disabled (Automated)
L1 Auto
Description

This recommendation verifies that SSH Service Is Disabled on the VMware vCenter 8 virtualization management platform. Disabling or removing unnecessary components reduces the attack surface and limits potential vectors for exploitation.

Rationale

Running unnecessary components on the VMware vCenter 8 virtualization management platform increases the attack surface and the risk of exploitation. Disabling or removing them follows the principle of least functionality and reduces exposure to known vulnerabilities.

Audit
# PowerCLI:
Get-VMHost | Get-VMHostService | Where-Object {$_.Key -eq 'TSM-SSH'} | Select VMHost, Running, Policy
# SSH should not be running unless needed; Policy should be 'off'
Remediation
# PowerCLI — Disable SSH on all hosts:
Get-VMHost | ForEach-Object {
  Stop-VMHostService -HostService ($_ | Get-VMHostService | Where-Object {$_.Key -eq 'TSM-SSH'}) -Confirm:$false
  Set-VMHostService -HostService ($_ | Get-VMHostService | Where-Object {$_.Key -eq 'TSM-SSH'}) -Policy 'off'
}

3 — VM Hardening

▶

3.1 VM Isolation

▶
3.1.1 Ensure Copy Operations Are Disabled (Automated)
L2 Auto
Description

This recommendation verifies that Copy Operations Are Disabled on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VM | Get-AdvancedSetting -Name 'isolation.tools.copy.disable' | Select Entity, Name, Value
# Value should be TRUE
Remediation
# PowerCLI — Disable copy operations:
Get-VM | New-AdvancedSetting -Name 'isolation.tools.copy.disable' -Value 'TRUE' -Force -Confirm:$false
3.1.2 Ensure Paste Operations Are Disabled (Automated)
L2 Auto
Description

This recommendation verifies that Paste Operations Are Disabled on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VM | Get-AdvancedSetting -Name 'isolation.tools.paste.disable' | Select Entity, Name, Value
# Value should be TRUE
Remediation
# PowerCLI — Disable paste operations:
Get-VM | New-AdvancedSetting -Name 'isolation.tools.paste.disable' -Value 'TRUE' -Force -Confirm:$false
3.1.3 Ensure Disk Shrinking Is Disabled (Automated)
L1 Auto
Description

This recommendation verifies that Disk Shrinking Is Disabled on the VMware vCenter 8 virtualization management platform. Disabling or removing unnecessary components reduces the attack surface and limits potential vectors for exploitation.

Rationale

Running unnecessary components on the VMware vCenter 8 virtualization management platform increases the attack surface and the risk of exploitation. Disabling or removing them follows the principle of least functionality and reduces exposure to known vulnerabilities.

Audit
# PowerCLI:
Get-VM | Get-AdvancedSetting -Name 'isolation.tools.diskShrink.disable' | Select Entity, Name, Value
# Value should be TRUE
Remediation
# PowerCLI — Disable disk shrink:
Get-VM | New-AdvancedSetting -Name 'isolation.tools.diskShrink.disable' -Value 'TRUE' -Force -Confirm:$false
3.1.4 Ensure Disk Wiping Is Disabled (Automated)
L1 Auto
Description

This recommendation verifies that Disk Wiping Is Disabled on the VMware vCenter 8 virtualization management platform. Disabling or removing unnecessary components reduces the attack surface and limits potential vectors for exploitation.

Rationale

Running unnecessary components on the VMware vCenter 8 virtualization management platform increases the attack surface and the risk of exploitation. Disabling or removing them follows the principle of least functionality and reduces exposure to known vulnerabilities.

Audit
# PowerCLI:
Get-VM | Get-AdvancedSetting -Name 'isolation.tools.diskWiper.disable' | Select Entity, Name, Value
# Value should be TRUE
Remediation
# PowerCLI — Disable disk wiper:
Get-VM | New-AdvancedSetting -Name 'isolation.tools.diskWiper.disable' -Value 'TRUE' -Force -Confirm:$false
3.1.5 Ensure Console Connection Limit Is Set (Automated)
L1 Auto
Description

This recommendation verifies that Console Connection Limit Is Set on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VM | Get-AdvancedSetting -Name 'RemoteDisplay.maxConnections' | Select Entity, Name, Value
# Value should be <= 2
Remediation
# PowerCLI — Limit console connections:
Get-VM | New-AdvancedSetting -Name 'RemoteDisplay.maxConnections' -Value '2' -Force -Confirm:$false

3.2 VM Resources

▶
3.2.1 Ensure SetInfo Size Limit Is Configured (Automated)
L2 Auto
Description

This recommendation verifies that SetInfo Size Limit Is Configured on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VM | Get-AdvancedSetting -Name 'tools.setInfo.sizeLimit' | Select Entity, Name, Value
# Value should be 1048576 (1 MB)
Remediation
# PowerCLI — Limit informational setinfo size:
Get-VM | New-AdvancedSetting -Name 'tools.setInfo.sizeLimit' -Value '1048576' -Force -Confirm:$false
3.2.2 Ensure Unnecessary Floppy Devices Are Removed (Automated)
L1 Auto
Description

This recommendation verifies that Unnecessary Floppy Devices Are Removed on the VMware vCenter 8 virtualization management platform. Disabling or removing unnecessary components reduces the attack surface and limits potential vectors for exploitation.

Rationale

Running unnecessary components on the VMware vCenter 8 virtualization management platform increases the attack surface and the risk of exploitation. Disabling or removing them follows the principle of least functionality and reduces exposure to known vulnerabilities.

Audit
# PowerCLI:
Get-VM | Where-Object {$_.ExtensionData.Config.Hardware.Device | Where-Object {$_ -is [VMware.Vim.VirtualFloppy]}} | Select Name
# No VMs should have floppy devices attached
Remediation
# PowerCLI — Remove floppy devices:
Get-VM | ForEach-Object {
  $floppy = $_.ExtensionData.Config.Hardware.Device | Where-Object {$_ -is [VMware.Vim.VirtualFloppy]}
  if ($floppy) {
    $spec = New-Object VMware.Vim.VirtualMachineConfigSpec
    $dev = New-Object VMware.Vim.VirtualDeviceConfigSpec
    $dev.Operation = 'remove'
    $dev.Device = $floppy
    $spec.DeviceChange += $dev
    $_.ExtensionData.ReconfigVM($spec)
  }
}

4 — Logging & Monitoring

▶

4.1 Logging

▶
4.1.1 Ensure Remote Syslog Is Configured (Automated)
L1 Auto
Description

This recommendation verifies that Remote Syslog Is Configured on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-AdvancedSetting -Entity (Get-VMHost) -Name 'Syslog.global.logHost' | Select Entity, Value
# Should show remote syslog server address
Remediation
# PowerCLI — Set remote syslog:
Get-VMHost | ForEach-Object {
  Set-AdvancedSetting -AdvancedSetting ($_ | Get-AdvancedSetting -Name 'Syslog.global.logHost') -Value 'udp://syslog.corp.local:514' -Confirm:$false
}
4.1.2 Ensure Host Log Level Is Set to Info (Automated)
L1 Auto
Description

This recommendation verifies that Host Log Level Is Set to Info on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VMHost | Get-AdvancedSetting -Name 'Config.HostAgent.log.level' | Select Entity, Value
# Should be 'info' or higher
Remediation
# PowerCLI — Set log level:
Get-VMHost | ForEach-Object {
  Set-AdvancedSetting -AdvancedSetting ($_ | Get-AdvancedSetting -Name 'Config.HostAgent.log.level') -Value 'info' -Confirm:$false
}
4.1.3 Ensure vCenter Logs Are Being Collected (Manual)
L1 Manual
Description

This recommendation verifies that vCenter Logs Are Being Collected on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# vCenter Shell or VAMI:
# Check /var/log/vmware/vpxd/vpxd.log exists and is being written
ls -la /var/log/vmware/vpxd/vpxd.log
tail -5 /var/log/vmware/vpxd/vpxd.log
Remediation
# Configure vCenter syslog forwarding:
# Via VAMI (https://<vcenter>:5480):
# Syslog Configuration > Add remote syslog target

# Or via dcli:
/usr/lib/vmware-vmon/vmon-cli --list | grep vpxd

4.2 Time Synchronization

▶
4.2.1 Ensure NTP Is Configured on All Hosts (Automated)
L1 Auto
Description

This recommendation verifies that NTP Is Configured on All Hosts on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# PowerCLI:
Get-VMHost | Get-VMHostNtpServer
# Should return configured NTP servers

Get-VMHost | Get-VMHostService | Where-Object {$_.Key -eq 'ntpd'} | Select Running, Policy
Remediation
# PowerCLI — Configure NTP:
Get-VMHost | ForEach-Object {
  Add-VMHostNtpServer -VMHost $_ -NtpServer 'ntp1.corp.local'
  Add-VMHostNtpServer -VMHost $_ -NtpServer 'ntp2.corp.local'
  Get-VMHostService -VMHost $_ | Where-Object {$_.Key -eq 'ntpd'} | Start-VMHostService -Confirm:$false
  Get-VMHostService -VMHost $_ | Where-Object {$_.Key -eq 'ntpd'} | Set-VMHostService -Policy 'on'
}

5 — Security Configuration

▶

5.1 TLS & Certificates

▶
5.1.1 Ensure TLS 1.2 or Later Is Enforced (Automated)
L1 Auto
Description

This recommendation ensures that TLS 1.2 or Later Is Enforced on the VMware vCenter 8 virtualization management platform. Enforcing this requirement establishes a minimum security standard and prevents insecure configurations.

Rationale

Without this enforcement, the VMware vCenter 8 virtualization management platform may accept insecure configurations that weaken overall security posture. Mandating this control ensures consistent protection against common attack vectors.

Audit
# Check TLS version:
openssl s_client -connect <vcenter>:443 -tls1_2 </dev/null 2>/dev/null | grep 'Protocol'
openssl s_client -connect <vcenter>:443 -tls1_1 </dev/null 2>/dev/null | grep 'Protocol'
# TLS 1.1 should fail, TLS 1.2 should succeed
Remediation
# Via vCenter shell:
# Edit /etc/vmware-rhttpproxy/config.xml:
# Set <sslOptions> to disable TLS 1.0/1.1:
# <sslOptions>!SSLv2,!SSLv3,!TLSv1,!TLSv1.1</sslOptions>

service-control --restart vmware-rhttpproxy
5.1.2 Ensure CA-Signed Certificates Are Used (Manual)
L1 Manual
Description

This recommendation verifies that CA-Signed Certificates Are Used on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# Check vCenter certificate:
openssl s_client -connect <vcenter>:443 </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject -dates
# Verify certificate is CA-signed and not expired
Remediation
# Replace with CA-signed certificate:
# 1. Generate CSR:
# /usr/lib/vmware-vmca/bin/certificate-manager
# Option 1: Replace Machine SSL Certificate
# 2. Submit CSR to CA
# 3. Import signed certificate via Certificate Manager

5.2 vCenter Services

▶
5.2.1 Ensure Unnecessary Services Are Disabled (Manual)
L1 Manual
Description

This recommendation verifies that Unnecessary Services Are Disabled on the VMware vCenter 8 virtualization management platform. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to implement this control may leave the VMware vCenter 8 virtualization management platform vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# vCenter shell:
service-control --status --all
# Review running services — disable unnecessary ones
Remediation
# Disable unnecessary services:
service-control --stop vmware-imagebuilder
service-control --stop vmware-netdumper

# Verify:
service-control --status --all
5.2.2 Ensure CEIP Is Disabled (Automated)
L2 Auto
Description

This recommendation verifies that CEIP Is Disabled on the VMware vCenter 8 virtualization management platform. Disabling or removing unnecessary components reduces the attack surface and limits potential vectors for exploitation.

Rationale

Running unnecessary components on the VMware vCenter 8 virtualization management platform increases the attack surface and the risk of exploitation. Disabling or removing them follows the principle of least functionality and reduces exposure to known vulnerabilities.

Audit
# Check CEIP (Customer Experience Improvement Program):
# PowerCLI:
Get-AdvancedSetting -Entity (Get-View -ViewType OptionManager -Filter @{'Name'='VpxSettings'}) -Name 'VirtualCenter.CEIP.JoinEnabled'
Remediation
# Disable CEIP:
# Via vSphere Client:
# Menu > Administration > Customer Experience Improvement Program > Leave

# Or via API:
Get-AdvancedSetting -Entity $global:DefaultVIServer -Name 'VirtualCenter.CEIP.JoinEnabled' | Set-AdvancedSetting -Value $false -Confirm:$false