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: defining 0day |
|---|---|
| Date: | Tue, 25 Sep 2007 15:54:55 -0500 |
On 9/25/07, Adrian Griffis <adriang63@gmail.com> wrote:
I understand why this descriptivist approach is tempting over a prescriptivist approach. But it's important, I think, to keep in mind that the public uses the word "illegal" when they really mean "unlawful" and uses the word "Schizophrenic" when they are talking about multiple personality disorders. All technical fields have their jargon, and the general public is simply not well educated enough about the issues involved to arbitrate disputes over usage. Just as the legal profession needs the word "illegal" with its proper meaning, we also need our jargon to facilitate precise discussions about security matters. The public can't always be the source of our definitions.
I understand and agree. The issue is, that as with those other terms, the industry has allowed the term to be misused long enough that the public now using it wrong as well. However, the "public" I was referring to is reference materials - dictionaries, wikipedia, etc.. If a newcomer to the security field hears the term "zero day" where does he go to find out what a "zero day" exploit is? Most students go to dictionaries or the like... and whats wrong with the current definition of a "zero day"? Okay, dump "zero day" completely and choose a new term for each division of exploit or vulnerability. Blue Sky Rambling: Try to enable a unified method of disclosure for all types of exploits and vulnerabilities via a single medium/site or multiple sites with a unified form or some such. I envision a check list asking things like "is this vulnerability known to the vendor - yes/no" and "does this exploit work against latest versions and all patches - yes/no" or whatever it takes to filter disclosures and allow them to be programatically labeled and disseminated, and the "participating" vendor to be contacted - everything occurring in an orderly, acceptable fashion by way of carved-in-stone rules. Definitions of the labels can't be argued because the rules don't bend for one person's perception. If all of the right check boxes are checked, its zero day, or its not. Oh, and you have to be "certified" to release a disclosure!
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: defining 0day, Adrian Griffis |
|---|---|
| Next by Date: | Re: defining 0day, Andrew Weaver |
| Previous by Thread: | Re: defining 0day, Adrian Griffis |
| Next by Thread: | Re: defining 0day, Andrew Weaver |
| Indexes: | [Date] [Thread] [Top] [All Lists] |