Tools / Microsoft Threat Modeling Tool (TMT) Interview questions
Explain the lifecycle of a threat model from creation to mitigation in TMT?
A threat model isn't a one-time deliverable - it's meant to track the system across its life, though TMT itself only actively participates in a few of these stages.
flowchart LR
A[Define scope, pick template] --> B[Build the DFD]
B --> C[Generate All Threats]
C --> D[Triage: set state per threat]
D --> E[Document mitigations/justifications]
E --> F[Re-review after architecture changes]
F --> B
E --> G[Export report for sign-off]
G --> H[Archive .tm7 with architecture docs]
The loop back from re-review to rebuilding the DFD is the part teams most often skip in practice: the model gets built once at design time, triaged, reported, and then treated as finished, even though the whole point of the lifecycle is that step F should trigger again every time the real architecture materially changes - not just at the next scheduled audit.
Which lifecycle step is most commonly skipped in practice?
The lifecycle is best understood as:
More Related questions...
