When has the last time that a virus that any of the AV vendors failed to catch had as devestating an effect as many organizations as this malignant AV update did?
And how about 12 hours instead of 24? -ASB: http://XeeSM.com/AndrewBaker On Wed, Apr 21, 2010 at 6:07 PM, Ziots, Edward <[email protected]> wrote: > Given how much AV doesn't catch now, is 24 hrs behind even a choice? > > Z > > Edward Ziots > CISSP,MCSA,MCP+I,Security +,Network +,CCA > Network Engineer > Lifespan Organization > 401-639-3505 > [email protected] > > > -----Original Message----- > From: Joseph L. Casale [mailto:[email protected]] > Sent: Wednesday, April 21, 2010 6:05 PM > To: NT System Admin Issues > Subject: RE: McAfee DAT problems > > >This was posted an hour ago - > > > >McAfee antivirus program goes berserk, freezes PCs > > So like McAfee said, I don't see the problem with Hospitals and Cops not > having service? <grin> > > This has started to become an epidemic it seems with av vendors and > incompetent QA. I > remember years ago after that dodgy win2k terminal server patch I vowed > never to simply > auto approve ms updates and setup a test group, after that incident I had > only seen one > update give me issues in all these years (recent .NET screwup) and that was > more cosmetic. > > The problem with this is av updates are released so frequently it's > impossible to qa them > internally. > > I suppose of you're not high risk in terms of usage/exposure, you could > always lag 24 hours > behind. > > I've never had an issue with Forefront, but I wonder how to automate a > "delay" w/ wsus, if > that's even possible? > > jlc > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
