This 2006 article published in the MSDN Magazine introduced the STRIDE approach to security design and threat modelling which is now part of the Microsoft’s Secure Development Lifecycle (SDL). What is good about it however is that it can be used on its own and serve as a helpful aide memoire when designing and reviewing any kind of system. To make it even easier I have put the following table together. It is pretty self-explanatory but it’s still a good idea to go back to the sources and read the original article, however what follows is a very quick example:
Spoofing threatens (Interactors, Processes) is addressed by Authentication Tampering threatens (Processes, Data flows, Data stores) is addressed by Integrity and so on.