STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Red Hat Enterprise Linux 10 Security Technical Implementation Guide

V-281197

CAT II (Medium)

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

Rule ID

SV-281197r1166543_rule

STIG

Red Hat Enterprise Linux 10 Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-002238CCI-000044

Discussion

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

Check Content

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

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