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. |

| Subject: | [Snort-sigs] confused over thresholds |
|---|---|
| Date: | Fri, 04 Aug 2006 10:29:23 +1200 |
Hi Folk,
I clearly don't understand this properly, sigh...
I am getting lots (tens of thousands) of hits on the bleeding VNC rule:
:alert tcp $EXTERNAL_NET any -> $HOME_NET 5900:5920 (msg: "BLEEDING-EDGE
SCAN Potential VNC Scan 5900-5920"; flags:S; threshold: type threshold,
track by_src, count 50, seconds 900; classtype:attempted-recon;
sid:2002911; rev:1;)
Astute people will notice that I have raised both the count and the
seconds parameters to threshold in an attempt to cut down the number of
alerts.
My understanding is that I should get just one alert every 900 seconds
per source but instead I get:
Timestamp Signature IP Src IP Dst
2006-08-03 12:24:18 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.140.37 6 48
2006-08-03 12:24:19 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.140.125 6 48
2006-08-03 12:24:20 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.140.178 6 48
2006-08-03 12:24:20 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.140.32 6 48
2006-08-03 12:24:21 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.140.239 6 48
2006-08-03 12:24:21 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.140.106 6 48
2006-08-03 12:24:22 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.140.137 6 48
2006-08-03 12:24:22 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.141.82 6 48
2006-08-03 12:24:23 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.141.124 6 48
2006-08-03 12:24:24 BLEEDING-EDGE SCAN Potential V 218.21.72.202
130.216.140.237 6 48
(apologies for the line wrap TB won't let me turn it on and off easily :( )
In this case the threshold does not seem to have any effect at all,
clearly I've screwed something up!
Any ideas what?
Russell
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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> |
|---|---|---|
| ||
| Previous by Date: | [Snort-sigs] Bleedingsnort.com Daily Update, bleeding |
|---|---|
| Next by Date: | Re: [Snort-sigs] confused over thresholds, Jeff Kell |
| Previous by Thread: | [Snort-sigs] Simple CMS admin access rule, Ureleet Ureleet |
| Next by Thread: | Re: [Snort-sigs] confused over thresholds, Jeff Kell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |