Manage Learn to apply best practices and optimize your operations.

Step-by-Step Guide: Patch management must-do list

Contributor Brien Posey warns not to rely solely on your patch management software in keeping Windows patched. Even the best tools will miss some security holes. In this step-by-step guide, he offers a must-do list to help you maintain Windows security.

Patching is a necessary evil in the Windows world. It's typically one of the lowest-priority tasks on an administrator's to-do list, yet it must be done or else Windows systems are left vulnerable to potential exploits.

You may choose a patch management tool to get the job done, but that in itself can provide you with a false sense of security: Whether it's free or commercial, no tool is perfect.

For these reasons, you must have the right patching processes in place. In this step-by-step guide, Brien Posey outlines several must-dos to help you ensure the correct patches are applied in a timely manner.

Patch management must-dos

 Home: Introduction
 Step 1: Do understand what is being patched
 Step 2: Do review patches every day
 Step 3: Do make sure patches are actually being applied
 Step 4: Do it yourself when necessary
 Resource kit: Tips for testing, deploying and fixing patches

Brien M. Posey, MCSE, MVP
Brien M. Posey is a Microsoft Most Valuable Professional for his work with Windows 2000 Server and IIS. He has served as CIO for a nationwide chain of hospitals and was once in charge of IT security for Fort Knox. As a freelance technical writer, he has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies.
Copyright 2005 TechTarget

This was last published in May 2005

Dig Deeper on Patches, alerts and critical updates

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.