Login or Register to Ask a Question and Join Our Community


Cybersecurity

Failed SSHD Login Attempts (15,000 per day) - Is that a lot compared to your server?

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums Cybersecurity Failed SSHD Login Attempts (15,000 per day) - Is that a lot compared to your server?
# 1  
Old 09-28-2019
FYI.

Normally, I do not run automatic banning systems, but after reviewing fail2ban again, I see the ban is configured out-of-the-box to only ban for a short period.

So, am testing fail2ban on all my Linux servers.

However, I agree with you stomp, that changing the sshd port from 22 to another value is one of the best deterrents agains these bots.

The same is also true for web software, for example Word Press. The best way to stop bot registrations, bot logins and spam posts is to change the URL of the registration, log in or posting scripts.

Also, having said that, I was hoping not to quickly get into remediation and risk management; but to get more people to post their FLAPM stats; using our simple method, so we could gather more stats.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Solaris logs - Tracking failed attempts from my host

Hey all I'm having a big problem here. Someone is attempting an SSH to a destination host on which an account resides and locking the account. I'm trying to determine who is performing the SSH attempts from my host. For instance they're logged in as their standard account but then (I'm assuming)... (13 Replies)
Discussion started by: MaindotC
13 Replies

2. UNIX for Dummies Questions & Answers

TCP failed connection attempts from netstat -s

Dear experts, I am seeing a lot of TCP failed connection attempts from "netstat -s" on one of our servers. How can I pin point what connection failed and what are the ports involved? Any tools/commands I can dig in deeper to diag. what went wrong on these "failed connection attempts"? ... (2 Replies)
Discussion started by: cache51
2 Replies

3. Shell Programming and Scripting

Shell script in tracking both the passed and failed login in a unix server

Can you help me in providing the following output or a quite similar to this from a shell script ? *** Logins Summary Information ***** ---------------------------------- Failed Login Attempts for Invalid Accounts Date Time IP-ADD Account ... (0 Replies)
Discussion started by: linuxgeek
0 Replies

4. AIX

Invalid login attempts

How can I see the number of invalid login attempts of a user? Thanks, (9 Replies)
Discussion started by: agasamapetilon
9 Replies

5. Solaris

Number of login attempts on solaris 10

Hi, I want to sent number of login attempts ,so that after that much attempts user account should be locked on solaris 10 (2 Replies)
Discussion started by: manoj.solaris
2 Replies

6. AIX

ftp check for failed attempts

Hi, I have created the below ftp script to put files over to our capacity server, the check at the end works if ftp fails to run however if the script cannot login or the transfer itself failed there is no warnings. Does anyone know the syntax to trap the erorr codes or to put a check within... (3 Replies)
Discussion started by: chlawren
3 Replies

7. AIX

Denying IPaddress for Multiple Failed Login Attempts

Hi. I would like to be able to deny IP address for too many failed login attemps (either from ssh, sftp, ftp, etc). The system I wish this to work on is an AIX 5.1 system. I'm new to AIX but I'm a linux user. There is a program for linux called fail2ban which reads from the log files and see if... (1 Reply)
Discussion started by: metzgerh
1 Replies

8. Solaris

invalid login attempts...

I am wondering if solaris captures id's associated w/invalid login attempts? when I try to login as "test1" several (3-5) times, I do not find any userID info under "/var/adm" files: utmpx wtmpx messages lastlog Is there another location/log I should be checking? Is it necessary for... (6 Replies)
Discussion started by: mr_manny
6 Replies

9. UNIX for Advanced & Expert Users

Maximum 3 login attempts

Hi, I notice in my Sun Solaris 8 sparc workstation, if I failed my login in the 5th time, I will be closed the connection from the host. I want to make 3 times. That is, if user fails to login with 3 attempts, he will be closed the connection. How to do it? Of course I am the admin of the... (2 Replies)
Discussion started by: champion
2 Replies
Login or Register to Ask a Question

LEARN ABOUT BSD

login

LOGIN(1)						      General Commands Manual							  LOGIN(1)

NAME

       login - sign on

SYNOPSIS

       login [ -p ] [ username ]

DESCRIPTION

       The  login  command  is	used when a user initially signs on, or it may be used at any time to change from one user to another.	The latter
       case is the one summarized above and described here.  See "How to Get Started" for how to dial up initially.

       If login is invoked without an argument, it asks for a user name, and, if appropriate, a password.  Echoing is  turned  off  (if  possible)
       during the typing of the password, so it will not appear on the written record of the session.

       After  a  successful  login,  accounting  files	are  updated and the user is informed of the existence of mail.  The message of the day is
       printed, as is the time of his last login.  Both are suppressed if he has a ".hushlogin" file in his home directory; this is mostly used to
       make life easier for non-human users, such as uucp.

       Login initializes the user and group IDs and the working directory, then executes a command interpreter (usually csh(1)) according to spec-
       ifications found in a password file.  Argument 0 of the command interpreter is the name of the command  interpreter  with  a  leading  dash
       ("-").

       Login  also  modifies  the environment environ(7) with information specifying home directory, command interpreter, terminal type (if avail-
       able) and user name.  The `-p' argument causes the remainder of the environment to be preserved, otherwise any previous environment is dis-
       carded.

       If the file /etc/nologin exists, login prints its contents on the user's terminal and exits. This is used by shutdown(8) to stop users log-
       ging in when the system is about to go down.

       Login is recognized by sh(1) and csh(1) and executed directly (without forking).

FILES

       /var/run/utmp	  accounting
       /usr/adm/wtmp	  accounting
       /usr/spool/mail/*  mail
       /etc/motd	  message-of-the-day
       /etc/passwd	  password file
       /etc/nologin	  stops logins
       .hushlogin	  makes login quieter

SEE ALSO

       init(8), getty(8), mail(1), passwd(1), passwd(5), environ(7), shutdown(8), rlogin(1c)

DIAGNOSTICS

       "Login incorrect," if the name or the password is bad.
       "No Shell", "cannot open password file", "no directory": consult a programming counselor.

BUGS

       An undocumented option, -r is used by the remote login server, rlogind(8C) to force login to enter into an initial connection protocol.	-h
       is used by telnetd(8C) and other servers to list the host from which the connection was received.

4th Berkeley Distribution					 November 27, 1996							  LOGIN(1)