Ensure login and logout events are collected


Monitor login and logout events. The parameters below track changes to files associated with login/logout events.

/var/log/lastlog - maintain records of the last time a user successfully logged in.

/var/run/faillock - directory maintains records of login failures via the pam_faillock module.


Monitoring login/logout events could provide a system administrator with information associated with brute force attacks against user logins.


Edit or create a file in the /etc/audit/rules.d/ directory, ending in .rules extension, with the relevant rules to monitor login and logout events.

# printf '
-w /var/log/lastlog -p wa -k logins
-w /var/run/faillock -p wa -k logins
' >> /etc/audit/rules.d/50-login.rules

Merge and load the rules into active configuration:

# augenrules --load

Check if reboot is required.

# if [[ $(auditctl -s | grep 'enabled') =~ '2' ]]; then printf 'Reboot required to load rules
'; fi

Additional Information:

Potential reboot required

If the auditing configuration is locked (-e 2), then augenrules will not warn in any way that rules could not be loaded into the running configuration. A system reboot will be required to load the rules into the running configuration.

System call structure

For performance (man 7 audit.rules) reasons it is preferable to have all the system calls on one line. However, your configuration may have them on one line each or some other combination. This is important to understand for both the auditing and remediation sections as the examples given are optimized for performance as per the man page.

NIST SP 800-53 Rev. 5:



See Also