SideBar    Setting Up the Test Network

Given the ever-increasing threats from hackers, viruses, and Internet-based worms, patch management has become a crucial component of enterprise security. Patch management is the process of identifying, verifying, downloading, and distributing security updates. Security updates are special hotfixes or software patches that a software publisher releases to address specific security threats. Microsoft has a well-established system for notifying the public about security vulnerabilities and makes patches available at http://www.microsoft.com/technet/security.

Tracking and assessing security threats, then finding and deploying the correct patches for each environment is a constant administrative challenge. Enterprise patch-management software can help streamline patch management, and the growing number of products in this arena is a testament to the need for easier patch management. Although I welcome all the development in this area, the currently available products still have plenty of room for improvement.

My associates and I tested seven patch-management products to determine their suitability for managing a Windows-based enterprise network. These products are not the only patch-management programs available, but they provide a good overview of the field. (For information about a free OS patch-management tool from Microsoft, see "Secure Your Clients with SUS," page 81.) We configured a complete test network (see the sidebar "Setting Up the Test Network," page 46) that reflected many common and some not-so-common configurations that IT departments must work with. We then installed each product to see how it performed.

We began the testing process with the assumption that enterprise patch-management software should meet certain minimum requirements:

  • It should provide flexible methods for scanning multiple systems, including the ability to scan within and across Active Directory (AD) organizational units (OUs), IP address ranges, and standalone systems.
  • It should accurately detect missing patches but skip obsolete or irrelevant patches.
  • It should allow easy patch deployment across a network.

In addition to testing for these minimum requirements, we reviewed the following additional features:

  • accurate, up-to-date information and analysis of current security patches
  • coverage of the most commonly used OSs and products
  • policy enforcement through custom computer or patch groups
  • a secure mechanism for scanning for, acquiring, and distributing patches
  • scalability to allow for large networks, multiple administrators, and multiple scanning stations
  • flexible scheduling and alerting features
  • flexible and useful reporting options

Our tests produced no clear winners. No one product works best for all environments. Although some products are clear leaders in the field, each has strengths and weaknesses that might make it appropriate or inappropriate for your network. To determine the products that meet your requirements, you must look at their features. Web Table 1 (http://www.winnetmag.com, InstantDoc ID 40710) lists the products we tested, their features, and a summary of their strengths. Because this technology is rapidly changing, check with the vendors for the most recent product information and updates.

   Prev. page   [1] 2 3 4     next page



You must log on before posting a comment.

If you don't have a username & password, please register now.

Reader Comments

A vague narrative of truisms and "what esle is new" commments about patching, mixed with some useful details. A comparison table of specific features for each package would be much better.

Milton F. Lopez

Is there any reason why Microsofts SUS, SMS, and BSA weren't included in the review?

Steve

We have been evaluating a product called Novadigm Patch Manager. Is there a reason why some of the more main stream products were not included in your evaluation? Thank you for your time.

Monique Ludwig

This is an excellent article. I was browsing the net to search for a Microsoft Patch Management Products and accidentally hit this page. I got the information I was looking for except that the article does not have anything about the Microsoft Software Update Services. Good Article indeed...

Thanks Author.

Regards,

C Mugilan

Excellent work. This market needed some more definition. The thoroughness of the feature sets and non-biased presentation is a credit to your publication. Thank you for setting a new standard.

T Wadsworth

Good job. I have just started patch management in our company and it is a big task, with articals like above everything becomes more clear everyday. Thank You for thinking of us.

Madeleine

I've been running HFNetChk Pro for quite a while now, and while it works OK, I still get frustrated with Office patches, especially Office 2K. We have some mixed version clients due to custom Access DBs, and it's virtually impossible to update both versions of office at the same time. From what I see in forums for other products, this is not limited to HFNetChk, but is common on all patch management systems. The requirement for source files from install media is frustrating. Hopefully MS can address this soon... Nice article, though. I plan on evaluating Patchlink since I need an app that's more scalable. I'd also like to work with a console that's multi-threaded, too...

Charlie Kaiser

I may have missed this feature in the products, but I see a need for a "exclusion list" of servers requiring specific sign off before patching. Many of the servers that I have to patch are FDA Validated machines requiring testing on QA machines before ANY patching. The Validated servers require very specific Change Management protocols before changing anything on the production systems. I see this as an important feature for any organization that supports FDA Validated systems.

RON

I use Service Pack Manager 2000 (Gravity Storm Software) works well. Very fast scanning, no agents to install.

leonard

I wanted to post a message about PatchLink I didn't see in the article. It is a great solution, but you cannot use their agent system on multiple computers when those computers were imaged using Norton Ghost, PowerQuest DeployCenter, etc. All computers will hash to the same unique identifier in their system.

Brandon Pack

I missed the editor's choice. Assume you had to pick one product after your comparison, which product would it be? Come on – don't be so shy! Thanks for putting this article and details together. Overall this is a very helpful document.

Michael K

the computer business is finished and is for losers nowadays...i'm going to law school

anonynous

Just a quick response to Brandon Pack's comment....you can use Patchlink with Ghost....there are instructions on the Patchlink site.

Joe Crowe

1) SUS Blows!! All it does it give you your very own copy of http://v4.windowsupdate.microsoft.com/en/default.asp. If you're looking for something more than "Critical Updates" and "Recommended Updates" look somewhere else.

2) Most products either have a prohibitive price tag or a prohibitive feature set. If someone wanted to cash in, they'd have a product with a good feature set, some purchasable add ons (like a good help desk system) and sell it for cheap.

Jimi Thompson

This blows

Anonymous User

See More Comments  1   2