Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: log monitoring, changing iptables

Subject: Re: log monitoring, changing iptables
Date: Wed, 24 Nov 2004 16:03:51 +0200 (IST)
Hi.

On Tue, 22 Nov 2004, Tom Boulay wrote:
      I'm sorry if this is overly simple, I'm just new to it.  I'm trying to
figure out a way to monitor my system logs and use that information to
ignore traffic from an IP address for, say, 15 minutes after three
failed login attempts.  My machine (2.4.x) only has ssh listening.  My
logs seem to have some marathon repeated root login attempts on the
weekends, and I would like to discourage those by including the 15
minute delay.  How would I monitor the /var/log/messages?  Do I need to
use something like sec?

The topic of these login attempts was discussed here some time ago. Don't
sure what was the conclusion, I guess there are simpler reactions:
 -- make sure that your passwords can't be broken (e.g., use private/public
    key pair for authentication)
 -- move ssh to a non-standard port

Regards,
ASK

<Prev in Thread] Current Thread [Next in Thread>