SQL Server Magazine

You have to download a patch”—few sentences evoke a louder groan from IT pros. Patch management can consume an inordinate amount of your already limited time. Often patches seem to creep in from nowhere—everything is going swimmingly until a zero-day security flaw is discovered and publicized, leaving the vendor scrambling to provide a patch and you scrambling to test it before deploying it to your production systems.

The fact is that patching and all patch-management tasks (downloading, integration into master images, testing) are a necessary evil in today’s IT landscape. Although most of you if presented with the question of “What about patch management do you find annoying?” would answer “Everything!”, I’ve dealt with some specific patching annoyances and figured out how to make them less annoying. I hope that after reading my tips you’ll be able to cross patching off your list of IT annoyances.

Prior Patch Preparation
The first patching annoyance that I’ll cover is the simple problem of finding out what patches are available and what issues they address. IT pros the world over are intimately familiar with Microsoft’s usual patch release day—the second Tuesday of every month, better known as Patch Tuesday. But there’s no reason to blindly check Windows Update on Patch Tuesday and install everything offered on a test machine and hope for the best.

At the Microsoft Web page “Microsoft Technical Security Notifications” (www.microsoft.com/technet/security/bulletin/notify.mspx) you can sign up for the Comprehensive Alerts email notification or the RSS feed (or more likely, you’ll want to sign up for all of the alert services on that page). Doing so provides you with early notification about the number of updates and the severity rating of security updates that Microsoft is planning to release on each Patch Tuesday. These bulletins are released the Thursday before Patch Tuesday.

On Patch Tuesday, you’ll receive another notification that provides further details on the released patches, including how to get more information. Sometimes Microsoft will release an out-of-band update to address an exceptionally dangerous security vulnerability. Notifications of these updates are also included in the alert services offered on the page noted above.

Also be aware of what I like to refer to as Stealth Patch Tuesday. Microsoft sometimes releases nonsecurity updates on Tuesdays other than the second Tuesday of the month. This is why you’ll be working on your computer on, say, the fourth Tuesday of the month and see the “Updates are available” balloon notification pop up.

You should also keep the Microsoft Security Response Center (MSRC) blog (blogs.technet.com/msrc/default.aspx) in your arsenal of Microsoft patch planning. Here, members of the MSRC not only reiterate the information provided by the notification service mentioned above, they also offer additional insight into the security patch release process and address problems that occur after Microsoft releases a patch. If there’s a buzz around a particular Microsoft security patch, be it a stability, deployment, or compatibility issue, you can be sure the MSRC team will address it.

Now that you’re prepared for when Patch Tuesday arrives, how do you know if a security vulnerability is already being exploited in the wild? A quick way to check is to examine the last two FAQ answers under the security bulletin in question.

Let’s take bulletin MS07-051 as an example. The bulletin is located at www.microsoft .com/technet/security/bulletin/ms07-051.mspx and the section we’re interested in is under the Vulnerability Information heading. Expand the section containing the CVE number (in this case it’s “Agent Remote Code Execution Vulnerability - CVE-2007-3040”), then expand the last section containing the FAQs. You’re interested in the answers to the last two questions. Skipping to the FAQ section about possible exploits doesn’t mean that you shouldn’t understand and plan to deploy all relevant patches to bring your systems up-to-date; it simply lets you quickly prioritize your patching schedule to first address those issues which can be exploited and cause you the most pain.

Even though I’m focusing on Microsoft, it’s rare to be in a homogeneous IT environme n t these days. So what about security patches for products not developed by Microsoft? For these you can either look on the vendor’s Web site for a similar security or patch notification service or invest some time daily at Secunia (secunia.com) and SecurityFocus (www.securityfocus.com). Better yet, subscribe to their respective RSS feeds that are relevant to the systems you support.

Your New Best Friend: WindowsUpdate.log
Patch Tuesday has come and gone. You’ve tested a patch and are ready to deploy it into production. In many IT environments these days, you’ll do this using Windows Server Update Services (WSUS). Smaller shops and home office users will likely have the Automatic Updates service turned on.

However, sometimes it might appear that WSUS and Windows Update (including the superset, Microsoft Update) aren’t cooperating with one or more computers. You might find that Windows Update also isn’t much help in providing a solution, offering only a generic error message and a cryptic hexadecimal code. So what should you do?

Take a look at WindowsUpdate.log, located in your Windows installation directory (typically C:\WINDOWS). One way to do so is to go to Start, Run and type

%windir%\windowsupdate.log

You’ll want to search the file for the words FATAL and WARNING, paying careful attention to the lines that immediately precede the FATAL or WARNING message. You’ll also want to note any error codes provided and search on those codes in your favorite Internet search engine and in the Microsoft Support Knowledge Base. (For more information about WindowsUpdate.log, see the Microsoft article, “How to read the Windowsupdate.log file” at support.microsoft.com/kb/902093.)

Continue to next page.

   Prev. page   [1] 2     next page