Channels ▼
RSS

Parallel

Fuzzing Security Testing Tool Released



Codenomicon has released a general-purpose fuzzing tool for testing all communication interfaces. The DEFENSICS Traffic Capture Fuzzer loads threat vectors from sources like network analyzers and vulnerability feeds, and automatically generates extensive tests to find zero-day threats in protocol implementations.

The Traffic Capture Fuzzer reads files in PCAP format, which is supported by all network analyzers and which is generally accepted as a standard for storing network flows. The Traffic Capture Fuzzer is software-based solution, and therefore, it is easy to use at every stage of the software development lifecycle. Programmers can start testing their protocol stacks immediately after the protocol interface is up and running. Penetration testers can go to any test setup, and have their fuzz tests running minutes after the initial analysis of the system.

Fuzzing is a versatile and comprehensive security testing technique making it a most suitable tool for testing the reliability of novel communication devices or business critical systems and applications. The most effective fuzzing techniques are based on protocol models, but traffic capture based solutions complement these approaches. Traffic Capture Fuzzing is essentially black-box testing -- that is, no access to the source code is needed in order for the tests to find new vulnerabilities. In contrast to security scanners and vulnerability scanners, fuzzing can find and eliminate zero-day exposures in any communication software, network equipment or complex network service.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video