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: exploit to vulnerability |
|---|---|
| Date: | Fri, 19 Aug 2005 10:42:31 -0700 |
Murad, Your question is a business question, not a technology question. The answer therefore is: it depends on the needs of the business. Personally, my opinion is that for *most* companies, it will be cheaper (long term) to immediately deploy security updates and roll them back if problems are encountered, than it would be to do a test pass on the security updates and then deploy and get hit with a worm in the interim. (Segregating high-risk machines from the immediate deployment might be appropriate for some companies as a middle ground: immediately patch all desktops while doing risk analysis/test/staged deployment on the servers, for instance.) Cleaning up from a worm can be very expensive. For reasons unknown to me, all of the "nasty" worms we've seen have been for the most part very benign. Imagine how much worse this situation would be if Zotob/Sasser/Blaster/Slammer authors had put a "Del c:\*.* /s" instruction somewhere in their code. Imagine how much more expensive cleaning up from that worm would be. Many firms, quite honestly, would simply not be able to recover from that. Many firms would go out of business if that were to happen. Ultimately, whether and when to install updates is a decision that management must make based on a risk analysis. Customers not willing or able to do a risk analysis will simply never know the right answer for them. Weigh the costs of patching and the probabilities of incurring those costs. Weigh the costs of not patching and the probabilities of incurring those costs. This is the classic Expected Value principle taught in Economics 101. -Matt -----Original Message----- From: Murad Talukdar [mailto:talukdar_m@subway.com] Sent: Friday, August 19, 2005 1:11 AM To: focus-ms@securityfocus.com Subject: exploit to vulnerability With all the issues highlighting the speed that exploits are now being written (eg http://www.securityfocus.com/news/11285 ) The window between exploit/vuln, appears on average, to be getting tighter. We have an SME network and I used to have a week or so to test patches before rolling them out. This all begs the question now, with limited resources, do I just patch and not worry about testing? I definitely have fewer resources than some of the companies that were hit (CNN et al) and less time to dedicate to patching. Should I just use auto updates/GP to patch everything regardless? What do other SME admins do? Kind Regards Murad Talukdar ------------------------------------------------------------------------ --- ------------------------------------------------------------------------ --- --------------------------------------------------------------------------- ---------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: exploit to vulnerability, Poole, Gary |
|---|---|
| Next by Date: | RE: anti-phishing implementation, Lyal Collins |
| Previous by Thread: | Re: exploit to vulnerability, Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] |
| Next by Thread: | RE: exploit to vulnerability, Smith, Jacqui |
| Indexes: | [Date] [Thread] [Top] [All Lists] |