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 Scans

Subject: Re: [Snort-sigs] SSH Scans
Date: Mon, 23 Aug 2004 15:30:00 -0500
On Mon, 2004-08-23 at 15:12, Matthew Jonkman wrote:
Definitely something to adjust locally I think. We have a lot of people 
coming from single sites and IP's as well, but it'd be pretty rare that 
5 new connections to the same box opened up within a minute I'd think.

In case specifically for SSH, sure, there's room to play. My caution was
for general threshold rules. Single IP != Single User  :)

In regards to SSH, though, I would restrict access to SSH with (a)
firewall(s) to those locations that need to log in. (insert your
favorite prevention-cure-quote here ;)  That way you don't even open
yourself to SSH brute force attacks.

Then, having limited the scope for the rule through firewall ACLs, you
can probably even better tune the threshold values.

Cheers,
Frank

Attachment: signature.asc
Description: This is a digitally signed message part

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