The frequency and severity of cyber attacks are growing rapidly. The number of IT security incidents jumped from 52,658 in 2001 to 82,094 in 2002, according to the Computer Emergency Response Team (CERT) Coordination Center at Carnegie Mellon University.
Network administrators facing a flood of patches from Microsoft must act fast to safeguard corporate information. They need plans for quickly determining which patches apply to their systems and how to roll out them out quickly. They should also learn how the software they purchased for rolling out patches will perform under tight deadlines.
Unfortunately, administrators donít have much time to make an informed decision. If it takes them a couple of days to have a software engineer write the custom code to package and test a new patch Ė a typical timeframe for many patch management solutions Ė they might as well invite hackers to ravage their files.
When Microsoft discovers a security hole, it announces the problem on its security and privacy Web pages and offers a hot fix. But that announcement acts like a starting gun to would-be hackers trying to figure out how to get in. Some industry gurus estimate that as much as 80 percent of Microsoftís customer base wonít download the patch because administrators either donít think it will affect them, or they donít have the resources. So the sooner hackers launch the virus, the more damage they can inflict. Administrators need to act fast to safeguard their networks.
Rapid, successful first-time patch deployment is key to staying ahead of hackers. Rapid deployment depends upon several factors, including the ability to prevent users from downloading bad files, an accurate, near-real-time understanding of system hardware and software configurations, a quick evaluation of which patches are necessary, and patch management tools that automate packaging and delivery while providing high deployment success rates.
Here are a few tips that will help administrators deploy the right patches quickly and efficiently:
- Lock down desktops and devices to prevent bad file downloads. Limit damage at the outset by preventing users from downloading files that could launch worms, viruses and other attacks.
- Formulate a plan. Map out a series of steps for quickly evaluating the patch and its impact, and delegating responsibility for rolling out the patch quickly and efficiently.
- Know your system. This includes servers, PCs, laptops, portable devices, operating systems, applications, etc. If Microsoft issues a hot fix for a scanner driver and a company only has one barely-used scanner, the administrator may determine that patch is unnecessary.
- Carefully read the patch alerts. The majority of the thousands of patches Microsoft issues every year wonít apply to most environments.
- Automate patch packaging. Patch management software should enable network administrators to cut and paste the new hot fixes into the standard Microsoft package format. Doing so cuts packaging time from days to minutes, giving administrators a much better chance of plugging holes before an attack.
- Pull vs. push the patches. Package patches and put them on the corporate LAN where clients that need them can get them. Administrators can give the patch deployment software auto-install permissions to target only the clients that donít have a specific registry key that indicates the need for the patch. Setting up the clients to automatically and seamlessly determine whether or not they need the patch and then pull it to them is much more efficient than pushing the patch out, and it provides a much higher deployment success rate.
- Put out fires quickly. Sometimes simply having the patch on hand isnít enough. If a virus or worm gets in before a patch is fully deployed, time becomes even more critical in minimizing damage. Administrators can help themselves with software that quickly identifies if a virus has already broken through, hunts down the source and destroys it.