Fuzz Testing
This section includes topics that cover how to perform fuzz testing on various devices and protocols with beSTORM.
Overview
beSTORM's fuzzing sequences are deterministic and can be replayed by telling beSTORM to start from the beginning, or from any other attack vector (position) you provide to beSTORM.
You can monitor beSTORM's progress by viewing the Progress Information section by selecting Preview. This displays the dataset currently being sent by beSTORM to the tested product, or you can look up the Detailed Log to view the current speed beSTORM is testing the product.
Even though beSTORM has predefined buffers which it fuzzes, you have complete control over the types of data it fuzzes and the type of data it generates (for example, long buffers, overflowing integers, etc.). Changing these predefined buffers, or even adding additional buffers, can greatly enhance the performance and the usability of beSTORM as it allows it to find more exceptions quickly, as well as find exceptions that might be specifically relevant to your product.
The following fuzz testing topics are available: