The vCenter Server must enforce the limit of three consecutive invalid login attempts by a user.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-258905 | VCSA-80-000023 | SV-258905r934373_rule | CCI-000044 | medium |
| Description | ||||
| By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. | ||||
| STIG | Date | |||
| VMware vSphere 8.0 vCenter Security Technical Implementation Guide | 2023-10-11 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
AC-7
1.00
- DISA · V1R1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.1.8
1.00
- DISA · V1R1 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000044
1.00
- DISA · V1R1 · disa_xccdf · related
Details
Check Text (C-258905r934373_chk)
From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Lockout Policy.
The following lockout policy should be set as follows:
Maximum number of failed login attempts: 3
If this account lockout policy is not configured as stated, this is a finding.
Fix Text (F-62554r934372_fix)
From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Lockout Policy.
Click "Edit".
Set the "Maximum number of failed login attempts" to "3" and click "Save".