Check the length in any input fields from incoming packets
Mitigations:
Select one from each of these categories
* Test-based:
* Run a fuzzer until you get >= X% code coverage, document the tool and the parameters, document any harmless bugs it triggers and why they aren't a problem
* Write your own test with >= Y% code coverage, include the source code of the test? same as above?
* The above but measuring the coverage in the object code using a simulator <- hard for MSA? do we care?
* Actually test 100% of the values, document how to run and source code
* Source code analysis:
* Run a source code analyzer and document why the false positives are false
* Use a memory-safe language and document why any use of unsafe features won't affect safety of this
What about shipping a whole linux?
Is there a use case where we care about glitching of the network interface itself? think about it
----
* Disable all interfaces that intercept incoming packets above data link layer and do not pass them to the to the host
* Check that outgoing packets only contain the data requested to be copied from host
* Don't auto-connect to an network that is not really the same network
# Annex A (informative): Mapping between the present document and CRA requirements
