Tools / Microsoft Threat Modeling Tool (TMT) Interview questions
How can you optimize threat modeling for a large microservices architecture using TMT?
TMT models one architecture per file and has no cross-model dashboard, so trying to draw every service and every call in one diagram quickly becomes unreadable and slow to regenerate.
A more workable approach is modeling at bounded-context granularity: one diagram per service, or per a small cluster of tightly related services, treating everything else that service calls as an external entity at the boundary rather than expanding every downstream dependency inline. Standardizing a shared custom template across teams keeps threat wording, priorities, and custom properties consistent so reports from different services can actually be compared. Since TMT won't stitch separate models together for you, maintaining a lightweight index mapping services to their model files (and who owns each) fills the gap that a native multi-model view would otherwise cover.
More Related questions...