Cis Ubuntu2004 V300 6 3 3 12

6.3.3.12 Ensure login and logout events are collected (Automated)

Profile

• Level 2 - Server
• Level 2 - Workstation

Description

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.

Rationale

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

Audit Procedure

Command Line

On disk configuration - Run the following command to check the on disk rules:

# awk '/^ *-w/ \
&&(/\/var\/log\/lastlog/ \
  ||/\/var\/run\/faillock/) \
&&/ +-p *wa/ \
&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)' /etc/audit/rules.d/*.rules

Verify the output matches:

-w /var/log/lastlog -p wa -k logins
-w /var/run/faillock -p wa -k logins

Running configuration - Run the following command to check loaded rules:

# auditctl -l | awk '/^ *-w/ \
&&(/\/var\/log\/lastlog/ \
  ||/\/var\/run\/faillock/) \
&&/ +-p *wa/ \
&&(/ key= *[!-~]* *$/||/ -k *[!-~]* *$/)'

Verify the output matches:

-w /var/log/lastlog -p wa -k logins
-w /var/run/faillock -p wa -k logins

Expected Result

Both on disk and running configuration should show login/logout audit rules.

Remediation

Command Line

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.

Example:

# 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\n"; fi

References

1. NIST SP 800-53 Rev. 5: AU-3

CIS Controls

MITRE ATT&CK Mappings: T1562, T1562.006 / TA0001 / M1047