Software and Hardware Testing Function

The parent hardware and firmware corruption technique spans induced corruption as well as latent defect. Testing addresses the latent half only.

Design flaws in hardware and firmware are what end-to-end negative testing in an as-flown configuration is meant to surface before launch, which is the practice's explicit test-as-you-fly requirement.

Malicious use of legitimate hardware commands is a behaviour an abuse-case test campaign would exercise, but the commands are by design valid, so testing documents the exposure rather than removing it.

Negative testing finds a subset of exploitable code flaws, and the as-flown requirement catches the integration-specific ones assurance review misses. It does not reach the class of defect only discoverable by analysis, so this is addresses while MI-SOFT-01 carries the mitigates.

Flooding is an abuse case in the practice's sense, and as-flown testing is where saturation behaviour becomes visible; the practice does not provide the rate limiting that would interdict it.

Erroneous input is the textbook abuse case, and negative testing is the named method. The practice interdicts by finding the handling defect the technique relies on.