CIS VMware ESXi 8 Benchmark

Secure configuration guidelines for VMware vSphere ESXi 8.0 hypervisor

v1.1.0 January 2025

Overview

▶

This CIS Benchmark provides prescriptive guidance for establishing a secure configuration posture for VMware ESXi 8.0 hypervisors. Recommendations cover installation hardening, network security, logging, access control, virtual machine settings, and storage configuration.

~130Recommendations
6Sections
2Profile Levels
SectionAreaFocus
1InstallationInstall, patching
2CommunicationvSwitch, port groups
3LoggingSyslog, NTP
4Access ControlAuth, SSH, shell
5VM HardeningVM options, devices
6StorageDatastores, console

Profile Definitions

▶
ProfileDescriptionIntended Use
L1Level 1 — CorporateEssential security for all ESXi hosts with minimal operational impact.
L2Level 2 — High SecurityDefense-in-depth for sensitive environments. May limit VM management flexibility.

1 — Installation & Patching

▶

1.1 Installation

▶
1.1.1 Ensure ESXi Is Installed on Supported Hardware (Manual)
L1 Manual
Description

This recommendation verifies that ESXi Is Installed on Supported Hardware on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to eSXi Is Installed on Supported Hardware may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
# Verify against VMware HCL:
esxcli hardware platform get
Remediation
# Install only on hardware listed in the VMware Compatibility Guide
# https://www.vmware.com/resources/compatibility
1.1.2 Ensure the Image Profile Acceptance Level Is Appropriate (Automated)
L1 Auto
Description

This recommendation verifies that the Image Profile Acceptance Level Is Appropriate on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to the Image Profile Acceptance Level Is Appropriate may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli software acceptance get
# Should be PartnerSupported or VMwareCertified
Remediation
esxcli software acceptance set --level=PartnerSupported

1.2 Patching

▶
1.2.1 Ensure ESXi Is Running the Latest Patches (Manual)
L1 Manual
Description

This recommendation verifies that ESXi Is Running the Latest Patches on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to eSXi Is Running the Latest Patches may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli software vib list | head -20
esxcli software profile get
Remediation
# Apply latest patches using vSphere Lifecycle Manager or:
esxcli software vib update -d /vmfs/volumes/datastore/patch.zip

2 — Communication

▶

2.1 Network Security

▶
2.1.1 Ensure ESXi Firewall Is Properly Configured (Automated)
L1 Auto
Description

This recommendation addresses the proper configuration of ESXi Firewall on the VMware ESXi 8 hypervisor. Proper configuration ensures the component operates securely and in accordance with organizational security policies.

Rationale

Misconfiguration of ESXi Firewall can lead to security gaps that may be exploited by attackers. A properly configured VMware ESXi 8 hypervisor reduces exposure to both known vulnerabilities and configuration drift.

Audit
esxcli network firewall get
esxcli network firewall ruleset list
Remediation
esxcli network firewall set --enabled true
esxcli network firewall set --default-action DROP
2.1.2 Ensure Firewall Rules Restrict Access to Management Services (Automated)
L1 Auto
Description

This recommendation verifies that Firewall Rules Restrict Access to Management Services on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to firewall Rules Restrict Access to Management Services may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli network firewall ruleset allowedip list
Remediation
esxcli network firewall ruleset set -r sshServer -a false
esxcli network firewall ruleset allowedip add -r sshServer -i 10.0.0.0/24

2.2 vSwitch & Port Groups

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

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

Rationale

Failure to promiscuous Mode Is Rejected may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli network vswitch standard policy security get --vswitch-name=vSwitch0
# PromiscuousMode should be false
Remediation
esxcli network vswitch standard policy security set --vswitch-name=vSwitch0 --allow-promiscuous=false
2.2.2 Ensure MAC Address Changes Are Rejected (Automated)
L1 Auto
Description

This recommendation verifies that MAC Address Changes Are Rejected on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to mAC Address Changes Are Rejected may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli network vswitch standard policy security get --vswitch-name=vSwitch0
# MacChanges should be false
Remediation
esxcli network vswitch standard policy security set --vswitch-name=vSwitch0 --allow-mac-change=false
2.2.3 Ensure Forged Transmits Are Rejected (Automated)
L1 Auto
Description

This recommendation verifies that Forged Transmits Are Rejected on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to forged Transmits Are Rejected may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli network vswitch standard policy security get --vswitch-name=vSwitch0
# ForgedTransmits should be false
Remediation
esxcli network vswitch standard policy security set --vswitch-name=vSwitch0 --allow-forged-transmits=false
2.2.4 Ensure VLAN IDs Are Properly Configured (Manual)
L1 Manual
Description

This recommendation addresses the proper configuration of VLAN IDs on the VMware ESXi 8 hypervisor. Proper configuration ensures the component operates securely and in accordance with organizational security policies.

Rationale

Misconfiguration of VLAN IDs can lead to security gaps that may be exploited by attackers. A properly configured VMware ESXi 8 hypervisor reduces exposure to both known vulnerabilities and configuration drift.

Audit
esxcli network vswitch standard portgroup list
Remediation
# Assign appropriate VLAN IDs; do not use VLAN 4095 (trunk) or native VLAN 1:
esxcli network vswitch standard portgroup set -p "VM Network" --vlan-id 100

3 — Logging & Auditing

▶

3.1 Syslog

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

This recommendation addresses the proper configuration of Remote Syslog on the VMware ESXi 8 hypervisor. Proper configuration ensures the component operates securely and in accordance with organizational security policies.

Rationale

Misconfiguration of Remote Syslog can lead to security gaps that may be exploited by attackers. A properly configured VMware ESXi 8 hypervisor reduces exposure to both known vulnerabilities and configuration drift.

Audit
esxcli system syslog config get
Remediation
esxcli system syslog config set --loghost=tcp://siem.example.com:514
esxcli system syslog reload
3.1.2 Ensure Persistent Logging Is Configured (Automated)
L1 Auto
Description

This recommendation addresses the proper configuration of Persistent Logging on the VMware ESXi 8 hypervisor. Proper configuration ensures the component operates securely and in accordance with organizational security policies.

Rationale

Misconfiguration of Persistent Logging can lead to security gaps that may be exploited by attackers. A properly configured VMware ESXi 8 hypervisor reduces exposure to both known vulnerabilities and configuration drift.

Audit
esxcli system syslog config get | grep logdir
# Should point to a persistent datastore, not scratch
Remediation
esxcli system syslog config set --logdir=/vmfs/volumes/datastore1/logs
esxcli system syslog reload

3.2 NTP & Time Sync

▶
3.2.1 Ensure NTP Is Configured and Running (Automated)
L1 Auto
Description

This recommendation verifies that NTP Is Configured and Running on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to nTP Is Configured and Running may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli system ntp get
esxcli system ntp config get
Remediation
esxcli system ntp set --enabled=true --server=ntp1.example.com --server=ntp2.example.com

4 — Access Control

▶

4.1 Authentication

▶
4.1.1 Ensure Password Complexity Policy Is Set (Automated)
L1 Auto
Description

This recommendation verifies that Password Complexity Policy Is Set on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to password Complexity Policy Is Set may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli system security password get
Remediation
esxcli system security password set --min-length=14 --min-uppercase=1 --min-lowercase=1 --min-numeric=1 --min-special=1
4.1.2 Ensure Account Lockout Is Configured (Automated)
L1 Auto
Description

This recommendation addresses the proper configuration of Account Lockout on the VMware ESXi 8 hypervisor. Proper configuration ensures the component operates securely and in accordance with organizational security policies.

Rationale

Misconfiguration of Account Lockout can lead to security gaps that may be exploited by attackers. A properly configured VMware ESXi 8 hypervisor reduces exposure to both known vulnerabilities and configuration drift.

Audit
esxcli system security account lockout get
Remediation
esxcli system security account lockout set --max-failures=5 --unlock-time=900
4.1.3 Ensure Active Directory Authentication Is Configured (Manual)
L2 Manual
Description

This recommendation addresses the proper configuration of Active Directory Authentication on the VMware ESXi 8 hypervisor. Proper configuration ensures the component operates securely and in accordance with organizational security policies.

Rationale

Misconfiguration of Active Directory Authentication can lead to security gaps that may be exploited by attackers. A properly configured VMware ESXi 8 hypervisor reduces exposure to both known vulnerabilities and configuration drift.

Audit
esxcli system account list
# Check for AD-joined domain
Remediation
# Join ESXi to AD domain via vSphere Client:
# Host → Configure → Authentication Services → Join Domain

4.2 SSH & Shell

▶
4.2.1 Ensure SSH Is Disabled Unless Required (Automated)
L1 Auto
Description

This setting enforces that SSH Is Disabled Unless is required on the VMware ESXi 8 hypervisor. Making this mandatory ensures consistent security policy enforcement across the environment.

Rationale

Failure to sSH Is Disabled Unless Required may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli system maintenanceMode get
/etc/init.d/SSH status
Remediation
# Disable SSH:
esxcli system ssh set --enable=false

# Or via policy — auto-stop after timeout:
vim-cmd hostsvc/advopt/update UserVars.SuppressShellWarning long 0
4.2.2 Ensure ESXi Shell Is Disabled (Automated)
L1 Auto
Description

This setting controls whether ESXi Shell is disabled on the VMware ESXi 8 hypervisor. Disabling this feature reduces the attack surface by removing unnecessary functionality that could be exploited by an attacker.

Rationale

Leaving ESXi Shell enabled when it is not required unnecessarily expands the attack surface. An attacker could leverage this feature to gain unauthorized access or escalate privileges on the VMware ESXi 8 hypervisor.

Audit
/etc/init.d/ESXShell status
Remediation
vim-cmd hostsvc/enable_esx_shell 0
vim-cmd hostsvc/start_esx_shell 0
4.2.3 Ensure Shell Timeout Is Set (Automated)
L1 Auto
Description

This recommendation configures the timeout for Shell on the VMware ESXi 8 hypervisor. Appropriate timeout values limit the window of opportunity for attacks and ensure resources are released in a timely manner.

Rationale

Failure to shell Timeout Is Set may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli system settings advanced list -o /UserVars/ESXiShellInteractiveTimeOut
Remediation
esxcli system settings advanced set -o /UserVars/ESXiShellInteractiveTimeOut -i 900

5 — Virtual Machine Hardening

▶

5.1 VM Options

▶
5.1.1 Ensure VM Copy/Paste Operations Are Disabled (Automated)
L2 Auto
Description

This setting controls whether VM Copy/Paste Operations is disabled on the VMware ESXi 8 hypervisor. Disabling this feature reduces the attack surface by removing unnecessary functionality that could be exploited by an attacker.

Rationale

Leaving VM Copy/Paste Operations enabled when it is not required unnecessarily expands the attack surface. An attacker could leverage this feature to gain unauthorized access or escalate privileges on the VMware ESXi 8 hypervisor.

Audit
# In .vmx file or via PowerCLI:
Get-VM | Get-AdvancedSetting -Name "isolation.tools.copy.disable"
Remediation
Get-VM | New-AdvancedSetting -Name "isolation.tools.copy.disable" -Value "TRUE" -Force
Get-VM | New-AdvancedSetting -Name "isolation.tools.paste.disable" -Value "TRUE" -Force
5.1.2 Ensure VM Drag & Drop Is Disabled (Automated)
L2 Auto
Description

This setting controls whether VM Drag & Drop is disabled on the VMware ESXi 8 hypervisor. Disabling this feature reduces the attack surface by removing unnecessary functionality that could be exploited by an attacker.

Rationale

Leaving VM Drag & Drop enabled when it is not required unnecessarily expands the attack surface. An attacker could leverage this feature to gain unauthorized access or escalate privileges on the VMware ESXi 8 hypervisor.

Audit
Get-VM | Get-AdvancedSetting -Name "isolation.tools.dnd.disable"
Remediation
Get-VM | New-AdvancedSetting -Name "isolation.tools.dnd.disable" -Value "TRUE" -Force
5.1.3 Ensure VMs Cannot Modify Host Settings (Automated)
L1 Auto
Description

This recommendation verifies that VMs Cannot Modify Host Settings on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to vMs Cannot Modify Host Settings may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
Get-VM | Get-AdvancedSetting -Name "isolation.tools.setinfo.disable"
Remediation
Get-VM | New-AdvancedSetting -Name "isolation.tools.setinfo.disable" -Value "TRUE" -Force

5.2 Device Security

▶
5.2.1 Ensure Unnecessary Hardware Devices Are Removed (Manual)
L2 Manual
Description

Unnecessary Hardware Devices should be removed from the VMware ESXi 8 hypervisor when not required. Removing unnecessary components reduces the attack surface and limits the number of potential vulnerabilities that need to be managed.

Rationale

Retaining Unnecessary Hardware Devices when it is not needed increases the attack surface. Unpatched or unused components are frequent targets for exploitation and should be removed as part of system hardening.

Audit
# Review VM hardware for unnecessary devices:
# Floppy drives, parallel/serial ports, USB controllers
Remediation
# Remove unnecessary virtual hardware from VM settings:
# Edit Settings → Remove floppy, serial, parallel ports
5.2.2 Ensure CD/DVD Drives Are Disconnected When Not In Use (Automated)
L1 Auto
Description

This recommendation verifies that CD/DVD Drives Are Disconnected When Not In Use on the VMware ESXi 8 hypervisor. Implementing this control strengthens the overall security configuration and reduces exposure to potential threats.

Rationale

Failure to cD/DVD Drives Are Disconnected When Not In Use may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
Get-VM | Get-CDDrive | Where-Object {$_.ConnectionState.Connected -eq $true}
Remediation
Get-VM | Get-CDDrive | Set-CDDrive -NoMedia -Confirm:$false

6 — Storage & Console

▶

6.1 Storage

▶
6.1.1 Ensure iSCSI CHAP Authentication Is Configured (Automated)
L2 Auto
Description

This recommendation addresses the proper configuration of iSCSI CHAP Authentication on the VMware ESXi 8 hypervisor. Proper configuration ensures the component operates securely and in accordance with organizational security policies.

Rationale

Misconfiguration of iSCSI CHAP Authentication can lead to security gaps that may be exploited by attackers. A properly configured VMware ESXi 8 hypervisor reduces exposure to both known vulnerabilities and configuration drift.

Audit
esxcli iscsi adapter auth chap get
Remediation
# Configure mutual CHAP authentication for iSCSI targets

6.2 DCUI & Console

▶
6.2.1 Ensure DCUI Access Is Restricted (Automated)
L1 Auto
Description

This setting ensures that DCUI Access is restricted on the VMware ESXi 8 hypervisor. Restricting this capability limits potential abuse and enforces the principle of least privilege across the environment.

Rationale

Unrestricted DCUI Access could allow unauthorized users or processes to perform actions beyond their intended scope. Applying least-privilege principles to the VMware ESXi 8 hypervisor is essential for defense in depth.

Audit
esxcli system settings advanced list -o /DCUI/Access
Remediation
esxcli system settings advanced set -o /DCUI/Access -s "root"
6.2.2 Ensure DCUI Timeout Is Set (Automated)
L1 Auto
Description

This recommendation configures the timeout for DCUI on the VMware ESXi 8 hypervisor. Appropriate timeout values limit the window of opportunity for attacks and ensure resources are released in a timely manner.

Rationale

Failure to dCUI Timeout Is Set may leave the VMware ESXi 8 hypervisor vulnerable to attack or non-compliant with organizational security policies. This control helps establish a consistent, hardened configuration baseline.

Audit
esxcli system settings advanced list -o /UserVars/DcuiTimeOut
Remediation
esxcli system settings advanced set -o /UserVars/DcuiTimeOut -i 600