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

Re: [Snort-users] Unified Log Format

Subject: Re: [Snort-users] Unified Log Format
Date: Tue, 28 Jun 2005 22:35:03 -0400
Hi Mario,

That's pretty cool, nice idea!

If you want a comprehensive map of the SIDs (Snort ID's) of GID 1, you should look at the sid-msg.map file in the etc directory of your Snort distribution. SID 527 is a bad-traffic.rules detect for same source/dest IP in a packet. Typically you'll get these listening on loopback...

Basically you can infer the structure of the packet data that's stored in a unified log record based on the GID of the event. Typically the log data will be a standard Snort packet, but on aggregate event like a portscan you'll get our crammed packet type that we're overloading the field with. GIDs 100, 117, 121 and 122 are all various portscan detectors that have been built for Snort over the years, you might just want to skip those records...

      -Marty


On Jun 28, 2005, at 3:52 PM, Mario D. Santana wrote:


Hi, all. I've written a patch to Ethereal to allow it to load unified output and display the alert information as a top-level protocol. This lets you do things like search agains snort.sig_generator, etc.


I'm not sure if this email should go to snort-dev, but I thought I'd give it a shot here first. BTW, if anyone wants to try out the patch, let me know off-list.

The patch is pretty functional, but I've run into a couple of snags. One of these seems to be related to the "fake" packets generated by snort to identify port scans. But sometimes strange things happen, such as finding signal IDs of 527 for generator ID 1 -- is this valid?

I've looked through the snort manual, the code, and other likely places. Any help or pointers would be appreciated.

TIA,
mds


------------------------------------------------------- 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-users mailing list Snort-users@lists.sourceforge.net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.php3?list=snort-users



--
Martin Roesch - Founder/CTO, Sourcefire Inc. - +1-410-290-1616
Sourcefire - Network Defense for the Real World - http:// www.sourcefire.com
Snort: Open Source Intrusion Detection and Prevention - http:// www.snort.org






-------------------------------------------------------
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-users mailing list
Snort-users@lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users

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