When it comes to patch management, there’s no one-size-fits-all approach to doing a job no one wants to do: update software for new features, or the more troubling task, fixing a security hole before a hacker or computer worm finds it. By all accounts, patching software is a disruptive, time-consuming process requiring IT departments to test any new software patch before applying it, scheduling downtime for machines to apply the patch and ensuring it doesn’t “break” applications. Patching for security purposes also means managers have to be on constant alert for news of any new holes found in vendor products. This thankless task monopolizes large chunks of IT staff time, in spite of a growing array of products and services that can track machines that need patches and automate patch downloads from vendor sites. At any rate, many organizations say they don’t need commercial patch-management products to do the job. Full Story
About OODA Analyst
OODA is comprised of a unique team of international experts capable of providing advanced intelligence and analysis, strategy and planning support, risk and threat management, training, decision support, crisis response, and security services to global corporations and governments.