STIGQter: STIG Summary: VMware vSphere 7.0 vCenter Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 24 Jan 2024:

The vCenter Server must require an administrator to unlock an account locked due to excessive login failures.

DISA Rule

SV-256346r885649_rule

Vulnerability Number

V-256346

Group Title

SRG-APP-000345

Rule Version

VCSA-70-000266

Severity

CAT II

CCI(s)

• CCI-002238 - Automatically lock the account or node for either an organization-defined time period, until the locked account or node is released by an administrator, or delays the next logon prompt according to the organization-defined delay algorithm when the maximum number of unsuccessful logon attempts is exceeded.

Weight

10

Fix Recommendation

From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Lockout Policy.

Click "Edit".

Set the "Unlock time" to "0" and click "Save".

Check Contents

From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Lockout Policy.

Verify the following lockout policy is set as follows:

Unlock time: 0

If this account lockout policy is not configured as stated, this is a finding.

Vulnerability Number

V-256346

Documentable

False

Rule Version

VCSA-70-000266

Severity Override Guidance

From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Lockout Policy.

Verify the following lockout policy is set as follows:

Unlock time: 0

If this account lockout policy is not configured as stated, this is a finding.

Check Content Reference

M

Target Key

5517