Threat models that start from your architecture, not a blank canvas.
The System Mapping Agent reads your diagrams, code, cloud, and documents, then builds an accurate model and adds the components it needs. The work starts from what you already have, not from scratch.
Decomposition is hard, and a blank canvas makes it harder. The agent starts the model for you.
Reads your architecture. Builds the model.
Point the System Mapping Agent at the artifacts you already have. It recognizes the patterns in them and builds an accurate model of the system, then adds the components, threats, and mitigations a complete model needs.
So you begin from your real architecture, not a blank page, and the first draft is ready to refine instead of write.
Everything it builds lands in the GraphEvery way into a model, in one agent
However your teams capture a system, the agent turns it into a model on the Secure Design Graph.
From the diagrams you have
Turn architecture diagrams and infrastructure files into living models, including Terraform, Visio, Draw.io, Miro, Lucidchart, Microsoft Threat Modeling Tool, and image files.
From the source and the cloud
Build from source, APIs, and live cloud through the MCP Server, inside the tools teams already use.
From what is written down
Generate models from product requirements, architecture docs, and policies, before a line of code exists.
Adds what the model needs
Recognizes patterns and creates the components, threats, and mitigations a complete model requires.
Reuse instead of rebuild
Start from prebuilt templates, and nest one model inside another so its threats and controls become part of the model you're building. Model each pattern once, reuse it everywhere.
Or model by hand
A drag-and-drop canvas with smart search and AI suggestions, for when you want to build it yourself.
The model you build today makes tomorrow's faster.
Everything the agent creates is written into the Secure Design Graph. Decomposition stops being a one-off exercise and becomes a reusable part of your practice, applied consistently across teams.
Because it builds on the Graph, every model starts richer than the last. The work compounds.
Explore the Secure Design Graph
One of three agents on the Graph
The System Mapping Agent builds the model. Two more keep it current and turn it into proof.
System Mapping Agent
Reads your architecture, code, cloud, and documents and builds the model, creating what it needs along the way.
You are hereGraph Agent
Connects components, threats, controls, and compliance in the Graph, and keeps it current as the system changes.
Explore the agentReporting Agent
Turns the Graph into audit-ready findings, control recommendations, and compliance reports on demand.
Explore the agent