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: | Re: [Snort-sigs] Suggestions for new attack response rules |
|---|---|
| Date: | Wed, 1 Dec 2004 16:01:44 -0500 |
On Wed, Dec 01, 2004 at 03:51:25PM -0500, Joe Patterson wrote:
alert tcp any $HTTP_PORTS -> any any (msg:"ATTACK-RESPONSES User attack OK response"; flow:from_server,established; pcre:"/^HTTP/1.1 (2|3)\d\d/"; flowbits:isset,http-user-attack; classtype:successful-user;)
Yes, I've thought about this for a long time. Its not anywhere near as simple as you suggest. Look at how nessus handles error codes. MANY websites no longer use 200s for "good", and 300s & 400s for various errors, they use 200s for EVERYTHING. Sure, you might get a good feeling for the one or two sites you are looking at for reducing false positives. In the rest of the world, just looking at HTTP codes is NOT enough. Brian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ 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] Suggestions for new attack response rules, Joe Patterson |
|---|---|
| Next by Date: | [Snort-sigs] Bleedingsnort.com Daily Update, bleeding |
| Previous by Thread: | [Snort-sigs] Suggestions for new attack response rules, Joe Patterson |
| Next by Thread: | RE: [Snort-sigs] Suggestions for new attack response rules, Joe Patterson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |