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 signature analysis tools |
|---|---|
| Date: | Fri, 14 Jan 2005 10:58:22 -0500 |
When you talk about intersecting rules, what data would you like to see intersecting? I speculate the critical information would be port/protocol info as well as payload string matches. A simple example is to find all rules that monitor port 80 or look for "package.exe" in the packet data. Seems like you could also achieve this using a grep search of the rule files. Some savvy programming could even process the rules into their respective fields, then import that info to a DB for relational searches. Having said all that, I'll qualify my programming experience ends with the ability to spell programming. ;-) Is this along the lines of what you're looking for Scott? Scott H. -----Original Message----- From: Martin Roesch [mailto:roesch@sourcefire.com] Sent: Tuesday, January 11, 2005 11:01 PM To: Scott Kelly Cc: focus-ids@securityfocus.com Subject: Re: snort signature analysis tools Hi Scott, I don't think there are any tools like that out there currently. -Marty On Jan 7, 2005, at 11:48 AM, Scott Kelly wrote:
-----Original Message----- From: Martin Roesch [mailto:roesch@sourcefire.com] Sent: Friday, January 07, 2005 6:48 AM To: Scott Kelly Cc: focus-ids@securityfocus.com Subject: Re: snort signature analysis tools What do you mean by overlaps/collisions? Rules that cover the same attack, duplicates, rules that will "cover" other rules and prevent them from firing?Maybe "intersecting rules" would be a better description. Is there a way, given an existing rule set, to determine the uniqueness of a proposed rule, to detect (interesting) intersections with other rules? Thanks, Scott
-- Martin Roesch - Founder/CTO, Sourcefire Inc. - +1-410-290-1616 Sourcefire - Discover. Determine. Defend. roesch@sourcefire.com - http://www.sourcefire.com Snort: Open Source Network IDS - http://www.snort.org -------------------------------------------------------------------------- Test Your IDS Is your IDS deployed correctly? Find out quickly and easily by testing it with real-world attacks from CORE IMPACT. Go to http://www.securityfocus.com/sponsor/CoreSecurity_focus-ids_040708 to learn more. --------------------------------------------------------------------------
smime.p7s
Description: S/MIME cryptographic signature
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IDS: Snort detecting distributed syn floods, Tim |
|---|---|
| Next by Date: | RE: Specification-based Anomaly Detection, (infor) urko zurutuza |
| Previous by Thread: | Re: snort signature analysis tools, Martin Roesch |
| Next by Thread: | Re: snort signature analysis tools, Chris Green |
| Indexes: | [Date] [Thread] [Top] [All Lists] |