Professional Documents
Culture Documents
Sixstepsforsecuritypatchmanagementbestpractices
SearchSecurity
+ Show More
1
2
f
Information Security magazine: Dollars and sense: Getting the security budget you need -- and spending it wisely:
C Download
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?
http://searchsecurity.techtarget.com/Sixstepsforsecuritypatchmanagementbestpractices
1/4
4/14/2015
Sixstepsforsecuritypatchmanagementbestpractices
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.
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.
Pro+
Features
E-Handbook
E-Zine
E-Handbook
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 OpenSSH has a vulnerability that may allow a buffer-overflow attack, but from your list of controls you
know you don't allow the SecSH 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.g., is the affected system inside or outside perimeter firewalls?); and the cost of mitigation and/or
recovery.
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.
This was first published in March 2003
http://searchsecurity.techtarget.com/Sixstepsforsecuritypatchmanagementbestpractices
2/4
4/14/2015
Sixstepsforsecuritypatchmanagementbestpractices
m Dig deeper on Security patch management and Windows Patch Tuesday news
AL L
N E WS
G E T S TA R TE D
E V A L U AT E
M AN A G E
P R O BL E M SO L VE
2
2
2
2
Load More
z 0comments
Oldest5
Register or Login
E-Mail
email@techtarget.com
Username / Password
Username
Password
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
-ADS BY GOOGLE
http://searchsecurity.techtarget.com/Sixstepsforsecuritypatchmanagementbestpractices
3/4
4/14/2015
Sixstepsforsecuritypatchmanagementbestpractices
PerformanceManagement
cornerstoneondemand.co.in
Performancemanagementmadefastandeasy.DownloadFreeWhitepaper
CLOUD SECURITY
NETWORKING
CIO
CONSUMERIZATION
ENTERPRISE DESKTOP
CLOUD COMPUTING
COMPUTER WEEKLY
SearchCloudSecurity
CipherCloud launches free cloud compliance resource center
CipherCloud's new Global Compliance Resource Center aims to clear up the confusion around global compliance and data privacy ...
VPN security issues in the cloud aren't uncommon, but they can be easily avoided with a few simple measures. Expert Dejan Lukan ...
About Us
Contact Us
Advertisers
Reprints
Privacy Policy
Business Partners
Archive
Site Map
Videos
Media Kit
Events
Photo Stories
Corporate Site
Guides
Experts
E-Products
All Rights Reserved,
Copyright 2000 - 2015, TechTarget
http://searchsecurity.techtarget.com/Sixstepsforsecuritypatchmanagementbestpractices
4/4