Check: RHEL-09-411090
RHEL 9 STIG:
RHEL-09-411090
(in versions v1 r3 through v1 r1)
Title
RHEL 9 must maintain an account lock until the locked account is released by an administrator. (Cat II impact)
Discussion
By limiting the number of failed logon 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
Check Content
Verify RHEL 9 is configured to lock an account until released by an administrator after three unsuccessful logon attempts with the command: $ grep 'unlock_time =' /etc/security/faillock.conf unlock_time = 0 If the "unlock_time" option is not set to "0", the line is missing, or commented out, this is a finding.
Fix Text
Configure RHEL 9 to lock an account until released by an administrator after three unsuccessful logon attempts with the command: $ authselect enable-feature with-faillock Then edit the "/etc/security/faillock.conf" file as follows: unlock_time = 0
Additional Identifiers
Rule ID: SV-258057r926158_rule
Vulnerability ID: V-258057
Group Title: SRG-OS-000329-GPOS-00128
Expert Comments
CCIs
| Number | Definition |
|---|---|
| CCI-000044 |
The information system enforces the organization-defined limit of consecutive invalid logon attempts by a user during the organization-defined time period. |
| 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 |