Search FCW


Subscribe Now!
Table of Contents
Sprint
Business
BPM
CXOs
Columns
Columnists
Defense
E-Government
Elections 2008
Enterprise Architecture
Funding
Homeland Security
Health IT
IPv6
LOB
Management
Procurement
Privacy
Policy
Program Management
State and Local
Security
Technology
Telework
Training and Certification
Workforce

More Topics
resourcecenter
Home
Letters to the Editor
Current Issue/Download
Print/Online Archives
Editorial Calendar
researchstore
resourcecenter
Communications for Continuity Operations

Oracle Resource Center
NEW! Transforming Data Center
Managed Services
Service Oriented Architecture
Training & Simulation
Networking Communications
Security Directives and Compliance
Data Center Virtualization
Air Force ELSG Contract Guide

More >>



Latest News
ADVERTISEMENT





 

Five steps to managing risk

Experts recommend going on the offensive to deal with vulnerabilities

By Brian Robinson
Published on June 27, 2005

Comment

Click here to comment on this article


Related story links

4 must-have security solutions

Finding chinks in the armor

Vulnerability scanning: It's all about control


Newsletters

You might also be interested in these FCW newsletters:

Daily

To learn more, click here.


For government technology managers, keeping pace with software patches and system configuration changes to thwart hackers has become an increasingly difficult job in the past few years. The challenge is causing a radical change in the way many of them manage information technology security.

Instead of waiting until attacks occur and hoping tools such as firewalls and intrusion-detection systems catch them before they inflict serious damage, many agencies have taken the offensive by hunting vulnerabilities before they are exploited.

The catchall phrase for those efforts is vulnerability management. Agencies that are successful at it know that vulnerability management entails the right mix of security tools, policies and procedures, experts say.

Although some agencies are slow to embrace vulnerability management, a number of regulations require them to be more assertive in handling security. In particular, according to the Federal Information Security Management Act (FISMA) of 2002, agencies must develop and enforce policies and procedures to ensure that their systems comply with specific security configurations.

Those requirements are only going to get tougher. The National Institute of Standards and Technology will soon publish a draft of a new document that will mandate a set of no fewer than 17 controls that each agency will have to apply to each of their major applications and general support systems. They must also tailor those controls based on how critical different systems are to an agency's mission.

Compliance with security requirements means a lot of work to accurately assess and then effectively manage vulnerabilities. Those who do it well can reap rewards. In 2003, for example, the U.S. Agency for International Development scored a C-minus on its FISMA score card. For 2004, the first full year it had a vulnerability management program in place, it posted a score of A-plus, the highest of any government agency.

"In our case, vulnerability management was a big help in our FISMA compliance," said Bill Geimer, USAID's program manager for information security.

But what is vulnerability management?

Although several vendors offer what they call vulnerability management solutions, a vulnerability management program often includes a collection of technologies and procedures that form a management process. Program components vary according to specific agency needs. But experts say the core approach usually follows a common path and includes the following steps.



upcoming event

Green Computing Summit, Ronald Reagan Building, Washington, DC
December 2 - December 3, 2008

Trusted Internet Connection and the Comprehensive National Cyber Security Initiative, The Willard Intercontinental Hotel, Washington, DC
December 4, 2008


 

head
fcw
issue
First Name State
Last Name Zip
Title Email