Update threat model #603
Description
Why
Citing OWASP on threat modeling:
Threat modeling is best applied continuously throughout a software development project. The process is essentially the same at different levels of abstraction, although the information gets more and more granular throughout the lifecycle. Ideally, a high-level threat model should be defined early on in the concept or planning phase, and then refined throughout the lifecycle. As more details are added to the system, new attack vectors are created and exposed. The ongoing threat modeling process should examine, diagnose, and address these threats.
We had written up threat models throughout the R&D phase (tech report #1, #2 and threat-model.md), and should keep up the practice by updating the threat model to our latest understanding. Also, 2-3 prominent threats are often discussed and influence our technical design - we should describe them in detail.
What
- Highlight key threats and risks in the technical design document
- Update the threat model
- TBD: do updates about performance and quality assurance as part of this (as mitigations)?