RHEL 10 must maintain an account lock until the locked account is released by an administrator.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-281197RHEL-10-600425SV-281197r1166543_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. Satisfies: SRG-OS-000329-GPOS-00128, SRG-OS-000021-GPOS-00005
STIGDate
Red Hat Enterprise Linux 10 Security Technical Implementation Guide2026-03-11

Related Frameworks

3 paths across 3 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-002238
1.00
  • DISA · V1R1 · disa_xccdf · related

Details

Check Text (C-281197r1166543_chk)

Verify RHEL 10 is configured to lock an account after three unsuccessful login attempts until released by an administrator with the following command: $ sudo grep 'unlock_time =' /etc/security/faillock.conf unlock_time = 0 If the "unlock_time" option is not set to "0", or the line is missing or commented out, this is a finding.

Fix Text (F-85663r1166542_fix)

Configure RHEL 10 to lock an account after three unsuccessful login attempts until released by an administrator with the following command: $ authselect enable-feature with-faillock Edit the "/etc/security/faillock.conf" file as follows: unlock_time = 0