STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide

V-282362

CAT II (Medium)

TOSS 5 must ensure account lockouts persist.

Rule ID

SV-282362r1200066_rule

STIG

Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000044

Discussion

Lockouts persisting across reboots ensure that the 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.

Check Content

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

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

dir = /var/log/faillock

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

Fix Text

Configure TOSS 5 to maintain the contents of the faillock directory after a reboot.

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

dir = /var/log/faillock