STIGQter STIGQter: STIG Summary: Cloud Linux AlmaLinux OS 9 Security Technical Implementation Guide Version: 1 Release: 7 Benchmark Date: 01 Jul 2026:

AlmaLinux OS 9 must configure the appropriate SELinux context on the nondefault faillock tally directory.

DISA Rule

SV-269155r1050037_rule

Vulnerability Number

V-269155

Group Title

SRG-OS-000329-GPOS-00128

Rule Version

ALMA-09-008380

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure AlmaLinux OS 9 to allow the use of a nondefault faillock tally directory while SELinux enforces a targeted policy.

Create a nondefault faillock tally directory (if it does not already exist) using the following command:

$ mkdir /var/log/faillock

Update the /etc/selinux/targeted/contexts/files/file_contexts.local file with the "faillog_t" context type for the nondefault faillock tally directory using the following command:

$ semanage fcontext -a -t faillog_t "/var/log/faillock(/.*)?"

Update the context type of the nondefault faillock directory and files within using the following command:

$ restorecon -RFv /var/log/faillock

Check Contents

Note: If the system does not have SELinux enabled and enforcing, a targeted policy, or if the pam_faillock module is not configured for use, this requirement is Not Applicable.

Verify the location of the nondefault tally directory for the pam_faillock module with the following command:

$ grep "dir =" /etc/security/faillock.conf

dir = /var/log/faillock

Check the security context type of the nondefault tally directory with the following command:

$ ls -Zd /var/log/faillock

system_u:object_r:faillog_t:s0 /var/log/faillock

If the security context type of the nondefault tally directory is not "faillog_t", this is a finding.

Vulnerability Number

V-269155

Documentable

False

Rule Version

ALMA-09-008380

Severity Override Guidance

Note: If the system does not have SELinux enabled and enforcing, a targeted policy, or if the pam_faillock module is not configured for use, this requirement is Not Applicable.

Verify the location of the nondefault tally directory for the pam_faillock module with the following command:

$ grep "dir =" /etc/security/faillock.conf

dir = /var/log/faillock

Check the security context type of the nondefault tally directory with the following command:

$ ls -Zd /var/log/faillock

system_u:object_r:faillog_t:s0 /var/log/faillock

If the security context type of the nondefault tally directory is not "faillog_t", this is a finding.

Check Content Reference

M

Target Key

5664