Red Hat Enterprise Linux 9 Security Technical Implementation Guide

The Red Hat Enterprise Linux 9 Security Technical Implementation Guide (V2 R10) has 445 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

445STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V2 · R10

CurrentPublished Wed Sep 30 2026

RHEL 9 must ensure account lockouts persist.

Red Hat Enterprise Linux 9 Security Technical Implementation Guide

Assessment Title

Rule Text

RHEL 9 must ensure account lockouts persist.

Description

Discussion Text

Having lockouts persist across reboots ensures that account is only unlocked by an administrator. If the lockouts did not persist across reboots, an attacker could simply reboot the system to continue brute force attacks against the accounts on the system.

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-258060

Rule

SV-258060r1045150_rule

Severity

medium

Rule Version

RHEL-09-411105

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Verify the "/etc/security/faillock.conf" file is configured to use a nondefault faillock directory to ensure contents persist after reboot with the following command:

$ sudo grep -w dir /etc/security/faillock.conf

dir = /var/log/faillock

If the "dir" option is not set to a nondefault documented tally log directory or is missing or commented out, this is a finding.

Implementation Procedure

Fix Text

Configure RHEL 9 maintain the contents of the faillock directory after a reboot.

Add/modify the "/etc/security/faillock.conf" file to match the following line:

dir = /var/log/faillock

STIG check 272 of 445 in the Red Hat Enterprise Linux 9 STIG checklist

← Previous · V-258059The root account must be the only account having unrestricted access to RHEL 9 system.Next · V-258061 →RHEL 9 groups must have unique Group ID (GID).