This collection of storage-related components were most valuable in extending a security assurance program into the area of black-box security testing for a NAS appliance.

Whatever the test suit they give, it is intelligent. It will understand the protocol and it will generate the test cases based on the protocol: protocol, message sequence, protocol, message structure. That intelligence is very good. Because of that, we can eliminate a lot of unwanted test cases, so we can execute the tests and complete them very quickly.

The product is related to US usage with TLS contact fees, how more data center connections will help lower networking costs.

• Test cases are not generated on the fly (which means that it isn't really fuzzing per se). They are organized in groups and defined according to the type of message and the tested part of the message. Compared to more random tools, fuzzing sessions can take less time and be more relevant.
• Simple and straightforward GUI.
• Context-sensitive helps in describing every configuration field along with their CLI equivalent.
• You can set a test sequence and thus test several protocols without any user interaction, and it can be sequential or in parallel.
• Interoperability feature which enables the user to ensure that the SUT supports the various types of tested protocols' messages. If a type of message failed the interoperability test, it won't be included in the fuzzing session, unless you want them to be included.
• Instrumentation capabilities (valid cases, ping, custom command) and actions (execution of a restart script of a device after a given number of failed instrumentation steps) upon instrumentation results.
• Reproduction of single test cases or along with the rest of the test case group.
• Network capture during fuzzing session as well as during the reproduction.
• Top 100 of the test cases which caused an important delay on the SUT response. Those cases are reproducible in order to check that the same test cases caused the unwanted behavior. This is useful for covering not well processed frames that don't necessarily make the SUT crash.
• Different sets to use depending on the available time and the coverage wanted (Full, Unlimited, Quick Run, Sample, etc.).
• We can create custom test cases by setting a value or a range of values on particular fields of a protocol.