Skip to main content

login on-failure log - not logging?


Recently I needed to enable logging of failed logon attempts in Cisco IOS. There is a "login on-failure log" configuration command which helped me accomplish my goal. While testing I noticed that enabling it on its own didn't produce expected results. Basically failed login attempts didn't show up in the log upon enabling it. In the end I found out that it must be used in conjunction with "login block-for" command to actually log logon attempts.

R3#show login failures
*** No logged failed login attempts with the device.***

This the defualt configuration:

R4#sh login
     No login delay has been applied.
     No Quiet-Mode access list has been configured.


     Router NOT enabled to watch for login Attacks


This is what we see after enabling "login on-failure log":

R3#sh login
     No login delay has been applied.
     No Quiet-Mode access list has been configured.
     All failed login is logged.


     Router NOT enabled to watch for login Attacks


This is configuration that we need in order for the router to actually log failed attempts:

R3#sh login
     A default login delay of 1 seconds is applied.
     No Quiet-Mode access list has been configured.
     All failed login is logged.


     Router enabled to watch for login Attacks.
     If more than 3 login failures occur in 60 seconds or less,
     logins will be disabled for 10 seconds.


     Router presently in Normal-Mode.
     Current Watch Window
         Time remaining: 27 seconds.


To set it up we need to do the following:

1. Create local user:

username test privilege 1 password cisco

2. Force use of local authentication database for vty lines:

line vty 0 4 
login local 

3. Enable logging of failed attempts:

login on-failure log

4. Enable block-for feature:

login block-for 10 attempts 3 within 60


Now the router will log failures:


R3#show login failures
Total failed logins: 1
Detailed information about last 50 failures


Username        SourceIPAddr    lPort Count TimeStamp
test            10.0.0.2        23    1     00:08:40 UTC Fri Mar 1 2002


R3#sh login
     A default login delay of 1 seconds is applied.
     No Quiet-Mode access list has been configured.
     All failed login is logged.


     Router enabled to watch for login Attacks.
     If more than 3 login failures occur in 60 seconds or less,
     logins will be disabled for 10 seconds.


     Router presently in Normal-Mode.
     Current Watch Window
         Time remaining: 27 seconds.
         Login failures for current window: 0.
     Total login failures: 1.


More details on Cisco site: https://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_login_enhance.html

Labels:

Comments

Post a Comment

Popular posts from this blog

x.509 Certificates - Critical vs non-critical extensions

Extensions are used to associate additional information with the user or the key.  Each certificate extension has three attributes - extnID, critical, extnValue extnID - Extension ID - an OID that specifies the format and definitions of the extension critical - Critical flag - Boolean value extnValue - Extension value  Criticality flag specifies whether the information in an extension is important. If an application doesn't recognize the extension marked as critical, the certificate cannot be accepted. If an extension is not marked as critical (critical value False) it can be ignored by an application. In Windows, critical extensions are marked with a yellow exclamation mark,  View certificate extensions using OpenSSL: # openssl x509 -inform pem -in cert.pem -text -noout (output abbreviated)         X509v3 extensions:             X509v3 Key Usage: critical                 Digital Signature, Key Encipherment             X509v3 Subject Key Identifier
Post a Comment
Read more

Count number of lines - 'findstr'

How do I count number of lines in a command output? findstr /r/n "^" | find /c ":" Above commands will display number of lines output by whatever command (well, nearly whatever) you specify in the front.  For example:  C:\>ping localhost | findstr /r/n "^" | find /c ":" FINDSTR: // ignored 12 This comes handy if you want to find out how many OUs you have in Active Directory: dsquery ou  -limit 0 | findstr /r/n "^" | find /c ":" How many user accounts there are: dsquery user -limit 0 | findstr /r/n "^" | find /c ":" Computers: dsquery computer -limit | findstr /r/n "^" | find /c ":"
Post a Comment
Read more

Cisco ASA Certificate Revocation Checking

ASA supports status verification using CRLs and OCSP. CRL can be retrieved using HTTP, LDAP or SCEP. Revocation checking using CRL: Over HTTP: ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-crl)# protocol http By default ASA will use address listed in CDP extension of the certificate that is being validated.  To override default behaviour we need to add the following in the CRL configuration context. ciscoasa(config-ca-crl)# policy static ciscoasa(config-ca-crl)# url 1 http://cdpurl.kp.local/crl.crl Over LDAP: Certificate I'm using for this lab, doesn't have LDAP address in its CDP extension. Therefore I'm using "policy static"  to specify LDAP URL where CRL can be retrieved.  ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-trustpoint)# crl configure ciscoasa
Post a Comment
Read more