SV-281252r1166708: RHEL 10 must configure SELinux context type to allow the use of a nondefault faillock tally directory. | Red Hat Enterprise Linux 10 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

RHEL 10 must configure SELinux context type to allow the use of a nondefault faillock tally directory.

Description

Discussion Text

Not having the correct SELinux context on the faillock directory may lead to unauthorized access to the directory.

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-000044

References

DPMS Target Red Hat Enterprise Linux 10 DISA DPMS Target Red Hat Enterprise Linux 10 5733

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

#!/bin/bash
# Reconstructed from oval:mil.disa.stig.rhel10os:def:281252
# RHEL 10 must configure SELinux context type to allow the use of a nondefault faillock tally directory.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.
#
# MANUAL REVIEW REQUIRED -- the module(s) below could not be reconstructed
# into working code from curated SCC reference data, and are excluded from
# the automated result:
#   - selinuxsecuritycontext_object (selinuxsecuritycontext_test) -- configured faillock directory has correct selinux context: no extractor for field "type"

# /etc/security/faillock.conf dir option exists
# textfilecontent54_object (textfilecontent54_test)
test_2() {
  grep -Pq '^\s*dir\s*=\s*(.*)\s*$' '/etc/security/faillock.conf' &>/dev/null
}

if test_2; then
  echo "PASS (automated portion only -- MANUAL REVIEW still required, see notes above)"
else
  echo "FAIL (or see MANUAL REVIEW note above)"
fi

Assessment Script Powered by AISandbox-executed

A standalone Shell script to assess this control automatically. Review before running it in your environment.

Syntax-checked and actually executed in an isolated sandbox (not the real system this checks) — confirmed to run without errors.

#!/bin/sh
# DISA STIG RHEL 10 must configure SELinux context type to allow the use of a nondefault faillock tally directory (oval:mil.disa.stig.rhel10os:def:281252)


if [ ! -f "/etc/security/faillock.conf" ]; then echo "FAIL"; exit 1; fi

if ! grep -q "^\\s*dir\\s*=\\s*/var/log/faillock\\s*$" /etc/security/faillock.conf; then echo "FAIL"; exit 1; fi

if [ ! -d "/var/log/faillock" ]; then echo "FAIL"; exit 1; fi

if ! stat -c "%d" /var/log/faillock &> /dev/null && ! grep -q "^faillog_t" $(find /etc/selinux/targeted/contexts/files/file_contexts.local -name "*faillock*"); then echo "FAIL"; exit 1; fi

echo "PASS"; exit 0

Remediation

Configure RHEL 10 to allow the use of a nondefault faillock tally directory while SELinux enforces a targeted policy.

Enable the feature using the following command:

$ sudo authselect enable-feature with-faillock

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

$ sudo mkdir /var/log/faillock

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

dir = /var/log/faillock

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

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

Update the context type of the nondefault faillock directory/subdirectories and files with the following command:

$ sudo restorecon -R -v /var/log/faillock