The SUSE operating system must lock an account after three consecutive invalid logon attempts.

From SLES 12 Security Technical Implementation Guide

Part of SRG-OS-000021-GPOS-00005

Associated with: CCI-000044

SV-91767r2_rule The SUSE operating system must lock an account after three consecutive invalid logon attempts.

Vulnerability discussion

By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account.

Check content

Verify the SUSE operating system locks a user account until the locked account is released by an administrator after three consecutive failed logon attempts. Check that the systems locks a user account after three consecutive failed login attempts with the following command: # grep pam_tally2.so /etc/pam.d/login auth required pam_tally2.so deny=3 If the "deny" option is greater than "3" or is missing, this is a finding.

Fix text

Configure the SUSE operating system to lock a user account until the locked account is released by an administrator after three consecutive failed logon attempts. Add or modify the following line in the auth section of the "/etc/pam.d/login" file (or other services being used) to match the following: auth required pam_tally2.so deny=3

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer