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]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Snort-sigs] OSSRC Rules Overlap Committee

from [Chris Baker] Network Security [Permanent Link]
Subject: Re: [Snort-sigs] OSSRC Rules Overlap Committee
Date: Wed, 1 Feb 2006 13:23:04 -0600 
I like the idea of vendor namespace, or numberspace.

However, the issue that weighs the heaviest for me is when should a rule be
promoted to a more authoritative namespace, and who has the highest
authority. We should have provisions for keeping vendor specific variants
within their namespace in addition to the community approved rule. I hope
that all rules can be eventually promoted to the Community Rules. Rules that
have no conflictions throughout other vendorspace do not have to be
promoted.
[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Snort-sigs] OSSRC Rules Overlap Committee, Erik Fichtner
Next by Date:  [Snort-sigs] Snort Community Rules Update, Sourcefire VRT
Previous by Thread:  Re: [Snort-sigs] OSSRC Rules Overlap Committee, Erik Fichtner
Next by Thread:  [Snort-sigs] Snort Community Rules Update, Sourcefire VRT
Indexes:  [Date] [Thread] [Top] [All Lists]