Six steps for security patch management best practices. January's SQL Slammer worm reminded us of the importance of patching vulnerabilities in computer software. Most successful computer attacks exploit well- known vulnerabilities, for which patches exist. The problem is that hundreds of patches are released each month, many of which apply to OSes and applications residing in your organization's network. How do you know which patches to install, and which to ignore? And what's the proper order and process for installing them?
Patch management is a complex process, and I can't cover all the variables here. But I can distill the process into six general steps. The importance of each stage of the patch process- -and the amount of time and resources you should spend on it- -will depend on your organization's infrastructure, requirements and overall security posture.
Windows Patch Management, SMS 2003 Overview By Marcin Policht (Send Email) Posted Jun 16, 2004 Digg; DZone; Reddit; Slashdot; StumbleUpon; del.icio.us; Facebook; FriendFeed; Furl; Twitter; Google.
Understanding Patch and Update Management: Microsoft’s Software Update Strategy. Streamlining the Patch and Update Management Process. Patch Management using Microsoft SMS 2003. Discusses how to update the Advanced Client during the installation initial installation of the client and. Systems Management Server (SMS) 2003 Advanced Client.
Systems Management Server (SMS) 2003 with Service Pack 1. Detailed reports available in SMS 2003 ease the application deployment process. Security patch management. Whitepaper: Transitioning from SMS 2003 Patch Management to Configuration Manager 2007 Software Updates. Clarifying a dramatic shift in a fundamental process in the minds of experienced SMS 2003 administrators. 1 Windows Patch Management, SMS 2.0 SUS Feature Pack. Windows Patch Management, SMS 2003 Overview Page. Symantec Endpoint Management lets you reduce IT costs and the complexities of software and patch management while improving efficiencies. Manual patch management process results in inefficiency and errors. Having worked extensively with ITMU in SMS 2003 for datacenter patch management of servers, I welcomed the new architecture promised for SCCM. If you are using ITMU now and are new to SCCM here is a high level. Maximize the Power of SMS with New Tools for Managing Updates. Microsoft Systems Management Server 2003 : The Four-Phase Patch Management Process (part 2) - The Evaluate & Plan Phase, The Deploy Phase - How To Install Windows Server 2012 On VirtualBox.
Step 1: Develop an up- to- date inventory of all production systems, including OS types (and versions), IP addresses, physical location, custodian and function. Commercial tools ranging from general network scanners to automated discovery products can expedite the process (see Resources, below). You should inventory your network periodically. Step 2: Devise a plan for standardizing production systems to the same version of OS and application software. The smaller the number of versions you have running, the easier your job will be later. Step 3: Make a list of all the security controls you have in place- -routers, firewalls, IDSes, AV, etc.- -as well as their configurations.
Don't forget to include system hardening or nonstandard configurations in your list of controls. This list will help you decide how to respond to a vulnerability alert (if at all). For example, let's say you learn that Open.
SSH has a vulnerability that may allow a buffer- overflow attack, but from your list of controls you know you don't allow the Sec. SH protocol through your firewall.
If nothing else, that knowledge gives you more time to react. Step 4: Compare reported vulnerabilities against your inventory/control list. There are two key components to this. First, you need a reliable system for collecting vulnerability alerts. And second, you need to separate the vulnerabilities that affect your systems from those that don't.
Some companies have staff dedicated to managing this process; others use vulnerability reporting services. Step 5: Classify the risk. Assess the vulnerability and likelihood of an attack in your environment. Perhaps some of your servers are vulnerable, but none of them is mission- critical.
Perhaps your firewall already blocks the service exploited by the vulnerability. In general, to classify and prioritize the risk, consider three factors: the severity of the threat (the likelihood of it impacting your environment, given its global distribution and your inventory/control list); the level of vulnerability (e. Step 6: Apply the patch! OK, so now you have an updated inventory of systems, a list of controls, a system for collecting and analyzing vulnerability alerts and a risk classification system. You've determined which patches you need to install.
Now comes the hard part: deploying them without disrupting uptime or production. Fear not, there are several tools that can help you with the actual patch process (see Resources, below). Evaluate these tools in terms of how well they fit your environment and budget. In some cases, manual patch maintenance may be more cost- effective. But in most cases- -particularly for multiple servers or server farms distributed across multiple locations- -some type of automated patch system will more than pay for itself.
Vulnerability and patch management isn't easy. In fact, in today's computing environment, it's a never- ending cycle. But by following these general steps, you'll be way ahead of the curve when the next worm comes knocking at your network door. About the author: Fred Avolio is president and founder of Avolio Consulting, a Maryland- based computer and network security consulting firm.
Patch Management & Application Management.