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: Tenable license discussion - Nessus engine |
|---|---|
| Date: | Wed, 26 Jan 2005 23:27:20 +0100 |
On Wed, Jan 26, 2005 at 05:02:09PM -0500, Jonathan Jesse wrote:
It might be an interesting experience to hear what actually happens on Microsoft Patch Tuesday. How many open source submissions do you actually receive on that day?
Recently, zero.
How soon after a patch is released does a test get deployed?
It depends on the patch. Basically, we do two things: - When the bulletins are published, we immediately make registry checks. They are usually done within 30 minutes after the bulletins have been made public (testing included) ; - Then, for remote flaws (ie: WINS, for Decembers' Microsoft day) we reverse engineer the patch to produce a network-check (no credentials required). That is, if it's possible to do so. It took a few hours for WINS - I think around 12 hours.
Then how long do we have to wait until it is part of the feed? I think the answer to the last question is 7 days if I recall from an earlier post.
Correct.
-- Renaud
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Tenable license discussion - Nessus engine, Jonathan Jesse |
|---|---|
| Next by Date: | Re: Tenable license discussion - Nessus engine, Jason Haar |
| Previous by Thread: | RE: Tenable license discussion - Nessus engine, Ron Gula |
| Next by Thread: | Re: Tenable license discussion - Nessus engine, rgula@tenablesecurity.com |
| Indexes: | [Date] [Thread] [Top] [All Lists] |