The ESXi host must verify the DCUI.Access list.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-256376 | ESXI-70-000002 | SV-256376r959010_rule | CCI-000366 | medium |
| Description | ||||
| Lockdown mode disables direct host access, requiring that administrators manage hosts from vCenter Server. However, if a host becomes isolated from vCenter, the administrator is locked out and can no longer manage the host. The "DCUI.Access" advanced setting allows specified users to exit lockdown mode in such a scenario. If the Direct Console User Interface (DCUI) is running in strict lockdown mode, this setting is ineffective. | ||||
| STIG | Date | |||
| VMware vSphere 7.0 ESXi Security Technical Implementation Guide | 2025-02-11 | |||
Details
Check Text (C-256376r959010_chk)
For environments that do not use vCenter server to manage ESXi, this is not applicable.
From the vSphere Client, go to Hosts and Clusters.
Select the ESXi Host >> Configure >> System >> Advanced System Settings.
Select the "DCUI.Access" value and verify only the root user is listed.
or
From a PowerCLI command prompt while connected to the ESXi host, run the following command:
Get-VMHost | Get-AdvancedSetting -Name DCUI.Access and verify it is set to root.
If the "DCUI.Access" is not restricted to "root", this is a finding.
Note: This list is only for local user accounts and should only contain the root user.
Fix Text (F-59994r885908_fix)
From the vSphere Client, go to Hosts and Clusters.
Select the ESXi Host >> Configure >> System >> Advanced System Settings.
Click "Edit". Select the "DCUI.Access" value and configure it to "root".
or
From a PowerCLI command prompt while connected to the ESXi host, run the following command:
Get-VMHost | Get-AdvancedSetting -Name DCUI.Access | Set-AdvancedSetting -Value "root"