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

Re: defining 0day

Subject: Re: defining 0day
Date: Tue, 25 Sep 2007 15:15:28 -0500
On 9/25/07, Gadi Evron <ge@linuxbox.org> wrote:

No longer good enough.

We can get a press scare over a public vuln release, or a wake-up call.

I think we can do better as an industry.


Who, then, rewrites all of the reference material? And doesn't any new
definition simply become definition number 2 in Webster?

Is it really the definition that is lacking or is the use of the word
at issue? Seems to me, from the beginning of this debate, that its the
usage. Far easier to reform the "zero day process" (disclosure, etc.)
than to redefine the term "zero day". The term is owned by the public,
the process is owned by those who follow it, the industry.

Couldn't a formal process be developed that does the defining/labeling
of a particular disclosure?

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