Review and create attack flow (Frederic Bourdelier Submission)

[pbjason9]

Make sure the data output from the sensors as well as control inputs are encrypted at rest and in motion, making sure the handshake/initialization process doesn't leak and/or allow man-in-the-middle, target-spoof, protocol spoof, etc. Need to be sure that source(s) and target(s) are positively identifiable. If the identification or data exchange process for any part of the system (even logging, ID verification, usage billing, maintenance data, etc.) use 3rd party address resolution, then that address resolution must be part of the system testing. If the endpoints are sufficiently verified, then that eliminates the usefulness of any "in-the-middle-redirection" attacks - but that means positive identity of all endpoints within the system scope must be validated from "power on" to "power off" - that means continuous validation protocols are required