Skip to main content
CUI

STIG Rule - V-265976

V-265976

SV-265976r1003584_rule

Deprecated CAT II

This rule has been deprecated. Deprecated on 2026-04-07. It is no longer included in the current version of this STIG.

The ESXi host must deny shell access for the dcui account.

From: VMware vSphere 8.0 ESXi Security Technical Implementation Guide (V2R3)

Description

<VulnDiscussion>The dcui user is used for process isolation for the DCUI itself. The account has shell access which can be deactivated to reduce attack surface.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

Check Procedure

From an ESXi shell, run the following command: # esxcli system account list or From a PowerCLI command prompt while connected to the ESXi host, run the following commands: $esxcli = Get-EsxCli -v2 $esxcli.system.account.list.Invoke() | Where-Object {$_.UserID -eq 'dcui'} If shell access is not disabled for the dcui account, this is a finding.

Fix Text

From an ESXi shell, run the following command: # esxcli system account set -i dcui -s false or From a PowerCLI command prompt while connected to the ESXi host, run the following commands: $esxcli = Get-EsxCli -v2 $arguments = $esxcli.system.account.set.CreateArgs() $arguments.id = "dcui" $arguments.shellaccess = "false" $esxcli.system.account.set.invoke($arguments)

CCI Reference

CCI-000366
Created
2026-04-07 20:08:40
Last Updated
2026-04-07 20:09:49
CUI