Check: VCTR-67-000047
VMware vSphere 6.7 vCenter STIG:
VCTR-67-000047
(in versions v1 r4 through v1 r1)
Title
The vCenter Server must require an administrator to unlock an account locked due to excessive login failures. (Cat II impact)
Discussion
By requiring that SSO accounts be unlocked manually, the risk of unauthorized access via user password guessing, otherwise known as brute forcing, is reduced. When the account unlock time is set to zero, once an account is locked it can only be unlocked manually by an administrator.
Check Content
From the vSphere Client, go to Administration >> Single Sign-On >> Configuration >> Policies >> Lockout Policy. View the values for the lockout policies. The following lockout policy should be set at follows: Unlock time: 0 If this account lockout policy is not configured as stated, this is a finding.
Fix Text
From the vSphere Client, go to Administration >> Single Sign-On >> Configuration >> Policies >> Lockout Policy. Click "Edit". Set the "Unlock time" to "0" and click "OK".
Additional Identifiers
Rule ID: SV-243106r879722_rule
Vulnerability ID: V-243106
Group Title: SRG-APP-000345
Expert Comments
CCIs
Number | Definition |
---|---|
CCI-002238 |
The information system automatically locks 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. |
Controls
Number | Title |
---|---|
AC-7 |
Unsuccessful Logon Attempts |