Skip to content

Latest commit

 

History

History
43 lines (31 loc) · 1.89 KB

howto-threatmodeling.md

File metadata and controls

43 lines (31 loc) · 1.89 KB

Practical Threat Modeling

This guide will be focussing on the STRIDE approach for threat modeling and will be using Microsoft's MSTMT app. We have prepared a k8s-stencils-template that could be used with the tool making it easier to model applications, services, agents based on k8s philosophy.

Threat Modeling is handled in following steps:

  1. Tool-Preparation:

  1. MODEL-Preparation: This step involves
    • preparing a system's interaction diagram or deployment architecture
    • specifying the trust boundaries Reuse existing system design diagrams and apply trust boundaries as necessary. Note that it is not necessary to get all the interactions correct in the first phase. You can have a simplistic view and then later keep on adding new entities/components to your model and apply new trust boundaries.

  1. Report Generation: Once the model is prepared click on "Switch to Analysis View" to check all the detected threats.

    To get a detailed report use, "Reports -> Create Full Report...". The report would be saved in an HTML file. For sample report, check here.

  2. Threat analysis: For the reported threats provide an analysis, stating whether

    • the threat needs investigation
    • it is "not applicable" and provide a justification
    • it is Mitigated because of some action taken