The vCenter Server must set the interval for counting failed login attempts to at least 15 minutes.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-256338VCSA-70-000145SV-256338r885625_ruleCCI-002238medium
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.
STIGDate
VMware vSphere 7.0 vCenter Security Technical Implementation Guide2023-12-21

Related Frameworks

3 paths across 3 frameworks
NIST 800-531 mapping
AC-7
1.00
  • DISA · V1R3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.1.8
1.00
  • DISA · V1R3 · 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-002238
1.00
  • DISA · V1R3 · disa_xccdf · related

Details

Check Text (C-256338r885625_chk)

From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Lockout Policy. Verify the following lockout policy is set as follows: Time interval between failures: 900 seconds If this lockout policy is not configured as stated, this is a finding.

Fix Text (F-59956r885624_fix)

From the vSphere Client, go to Administration >> Single Sign On >> Configuration >> Local Accounts >> Lockout Policy. Click "Edit". Set "Time interval between failures" to "900" and click "Save".