UCF STIG Viewer Logo

The SUSE operating system must generate audit records for all modifications to the faillog file.


Overview

Finding ID Version Rule ID IA Controls Severity
V-217257 SLES-12-020760 SV-217257r854151_rule Medium
Description
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215
STIG Date
SLES 12 Security Technical Implementation Guide 2022-12-06

Details

Check Text ( C-18485r369927_chk )
Verify the SUSE operating system generates an audit record when all modifications to the "faillog" file occur.

Check that the following is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":

# sudo grep -i faillog /etc/audit/audit.rules

-w /var/log/faillog -p wa -k logins

If the command does not return a line, or the line is commented out, this is a finding.
Fix Text (F-18483r369928_fix)
Configure the SUSE operating system to generate an audit record for any all modifications to the "faillog" file occur.

Add or update the following rule to "/etc/audit/rules.d/audit.rules":

-w /var/log/faillog -p wa -k logins

The audit daemon must be restarted for the changes to take effect.

# sudo systemctl restart auditd.service