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 Snort-Signatures
[Top] [All Lists]

Re: [Snort-sigs] SSH brute force attack sig

Subject: Re: [Snort-sigs] SSH brute force attack sig
Date: Wed, 06 Jul 2005 13:49:10 -0500
--On Wednesday, July 06, 2005 13:30:04 -0500 Matt Jonkman <matt@infotex.com> wrote:

Flowbits is part of the standard snort for anything remotely recent.

The basis is you can use a flowbit like a variable, so you can pass
information from one stream or one sig to another.

In this case you could write another sig that only applied when
ssh.brute.attempt was set.

It's not relevant at this point because the sigs we had that did check
that variable we dropped. We thought a while ago we had a lead on the
packet size that we'd see on a successful authentication. So we wanted
to start looking for that packet if there was  a brute going on, that
being a big problem if a brute got a successful auth.

Ahh...that makes sense.

What I wish snort had is something that could track multiple session initiation attempts to multiple hosts. For example, if you could write a rule something like this, it would be very useful.

alert tcp any any -> any any (msg: "Multiple session inits"; flags: S; flowbits:init.host; init.host.connects: 200; rcv.hosts.connects: 200; sig: blah; rev: blah;)

I suppose a simple form of that could be:
alert tcp any any -> any any (msg: "Multiple session inits"; flags: S; threshold: type both, track by_src, count 200, seconds 60; sig: blah; rev: blah;) (I might just play around with this.)


Now *that* would be a useful addition. I have no idea if it could be done, though (codewise). Obviously you'd have to use something to track the initiating host's connections, but if it could be done, it would be a killer keyword for catching bad stuff on your network (or coming in to your network.)

Paul Schmehl (pauls@utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/ir/security/


------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Snort-sigs mailing list Snort-sigs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/snort-sigs

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