.svg)
SECURITY
STRIDE and security standards
Generate security threats and requirements using your organization’s policies and rating guidance.
AUTOMATED THREAT MODELING · DESIGN-STAGE THREAT MODELING
Turn your proposed architecture into a threat model before coding starts.
Generate components, data flows, trust boundaries, threats and security requirements from design inputs before coding begins. Connect planned components to their implementation as development starts.
Add a webhook receiver for events from an external provider.
Source interpretation
External provider → webhook receiver → event processing
Threat and requirement
Unauthenticated requests could trigger processing. Require authentication before handling the event.
Reviewer decision
Inspect the source, refine the model and approve the requirement.
DESIGN-STAGE THREAT MODELING
Start with a design. Get a model your team can review.
Heeler generates the architecture, threats and requirements from the material you already have. Your reviewers inspect the source evidence and decide which proposals become the approved design.
For existing systems, use Code-to-Cloud Threat Modeling to start from source code and deployed infrastructure.
See how the source becomes the model.
Inspect the passage or diagram region behind a proposed component, flow or requirement. Review assumptions and unanswered questions before accepting the proposal.
Illustrative source-to-model traceability. Inputs include pasted text, uploads, diagram images, connected documents and Figma frames.
Apply your standards during analysis.
Choose the threat-modeling methods and organization guidance that shape the review.
PRIVACY
LINDDUN and data flows
Review privacy threats across the data flows and trust boundaries in the model.
AI SYSTEMS
MAESTRO and agent architecture
Model threats involving AI models, agents, tools and MCP servers.
REVIEW AND APPROVE
Review the architecture and approve the requirement.
The generated model prepares the decision. Reviewers inspect the external boundary, resolve assumptions and approve the authentication requirement that development must satisfy.
Illustrative design review. Approvals apply to a specific model version.
Send approved requirements into development and verification.
The review produces more than a diagram. Mapped requirements are available through MCP and the CLI, organization-specific agent skills carry your guidance, and supported design guardrails connect requirements to security checks.
For planned components, inspect and confirm repository and code-root matches as implementation becomes available. That connection supports file-specific guidance and later design-to-implementation checks.
Technical questions
Can I start without code?
Yes. Create a draft system from design inputs, then connect approved planned components to their implementation as it becomes available.
Can I bring an existing threat model?
Import Microsoft TMT, Threat Dragon, OWASP TML, pytm JSON or component lists through a review. Interchange exports identify fields that required defaults.
Next: deliver the approved requirements to the coding agent.
The webhook authentication requirement now has to reach the agent before it edits the receiver. Heeler maps files to model elements and retrieves the requirements that apply.
AUTOMATED THREAT MODELING · FROM PROMPT TO RUNTIME
