|
Mu’s solution helps Government developers as well as their COTS supply chain generate test cases that thoroughly test the resilience aspects of any IP service. Frequently, Government agencies operate significant legacy services dependent upon custom protocols and formats usually unsupported by off-the-shelf test tools. Proprietary protocol implementations (or proprietary extensions to standard protocols) are not tested (or barely tested, respectively) using commercially available test tools. Regardless, software bugs in these implementations have negative effects.
A key application of resilience testing occurs when government agencies are selecting new vendor equipment
for use in their future network planning. In this case, it is essential that they
establish a durable impartial baseline, especially around interoperability of the
protocols they intend to use within their network architectures. One of the
best ways to accomplish this is via fuzzing, either based on open
protocol specifications or on service-specific traffic flows that must
be supported by the operational network. Mu's Protocol Fuzzing and Studio Zx modules simplify the process of comparison since the results of many different target devices can be examined side-by-side to
see which is best able to stand up to invalid or unexpected inputs around
the traffic that must be supported by the network.
The Mu Test Suite performs resilience testing for virtually any IP service traffic captured and generates actionable remediation tools to help the developer or vendor fix the issue. There are few, if any, other tools capable of testing the resilience of proprietary legacy services. Testers now use the Mu Test Suite to generate custom reliability tests based on their specific environment. Mu enables test creation from various types of input such as
Once a basic set of test scenarios are established from prior existing test cases or new ones are identified, the Mu solution auto-generates tens of thousands (to tens of millions) of tests designed to expose resilience weaknesses in the implementation.
|
