What problem does it solve?
Creating .tm7 files by hand is error-prone because the Microsoft Threat Modeling Tool uses a strict WCF DataContractSerializer XML format, and any structural mistake causes the tool to reject the file as corrupted. This Skill produces files that open cleanly in the tool v7.3+.
Core Features & Use Cases
- Valid .tm7 Generation: Serializes threat models using the exact DataContract namespaces, wrapper elements, and element ordering the tool expects.
- STRIDE Threat Modeling: Maps processes, data stores, external interactors, trust boundaries, and data flows to Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege threats.
- Reference Integrity: Ensures every stencil, flow, and threat GUID resolves correctly and every z:Id is unique to avoid deserialization failures.
- Use Case: Describe your system architecture (web app, SQL database, browser client) and receive a ready-to-open .tm7 file with a diagram and prioritized STRIDE threats.
Quick Start
Ask the assistant to create a .tm7 threat model for your system, listing its components, data stores, external users, and data flows.