Attacks/Breaches
6/11/2010
12:54 AM
100%
0%

The Truth About Vulnerability Scanners

Scanning tools can help detect vulnerabilities, but they shouldn't be the only tools on your belt. Here's a look at three areas where scanners fall short

Excerpted from "Scanning Reality: Limits of Automated Vulnerability Scanners," a new report posted today in Dark Reading's Vulnerability Management Tech Center.

In some enterprises, the term "vulnerability management" begins and ends with scanning tools. For these enterprises, improving vulnerability management simply means bringing in more scanners to ensure a broad view.

But are network-based vulnerability scanners and Web application scanning tools enough to ensure that your organization will identify and remediate its security vulnerabilities -- before they are exploited by the bad guys? We submit that most IT organizations have a limited understanding of what these tools can do -- and where they fall short.

There are three key limitations of vulnerability scanners. Some of the risks around these problems can be mitigated by incorporating additional technologies into your vulnerability management program, while others are beyond the scope of any automated technology.

Whatever mitigation strategy is used to fill the gap left by these scanners, the first step is to understand their shortcomings.

The first problem area is authentication. Network-based vulnerability scanners are imperfect tools at best. Even when they are properly configured, they detect only vulnerabilities for which they have signatures. While anonymous (unauthenticated) scanning can provide some benefit, failure to leverage authenticated scanning dramatically reduces scanner effectiveness.

A second key problem is the scanner's inability to work with custom applications. CVE-based, known vulnerabilities are only a small subset of most organizations' overall attack surfaces. Security checks may exist for the most popular applications and operating systems hosted within your network, but what about the custom applications you have written in-house or outsourced to third parties? There are no CVEs for custom apps.

Finally, most vulnerability scanning tools can identify points of weakness, but they can't anticipate complex attack schemes. While vulnerability scanners typically identify and report on issues that can be utilized as the initial point of entry, they are limited in identifying the complex avenues an attacker could take to compromise your network.

Automated vulnerability scanners play a critical role in helping you manage and understand the security risks that may exist within your environment. However, like any tool, the capabilities and results of these tools need to be fully understood and their limitations noted.

To get details on these key limitations, and some recommendations on how to address them, download the full report.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.