Yes. There are now several tools specifically designed to turn an architecture diagram into a threat model rather than merely having a general-purpose LLM “look at the picture.”
Best options
- iriusrisk.com — probably the strongest fit if you want a formal, reviewable threat model. Jeff can take images or other design artifacts and generate a threat model, while IriusRisk's rules engine provides deterministic threats and countermeasures with traceability. It supports STRIDE-style analysis and broader security/compliance workflows.
- threatmodeler.ai — particularly interesting for larger engineering organizations. Its System Mapping Agent can ingest architecture diagrams, IaC, cloud environments, code, APIs, and documents, then construct an architecture-aware model.
- threatvector.ai — more diagram-centric. Its AI assistant analyzes components and data flows and produces threats, attack paths, and mitigations, with STRIDE/OWASP-oriented analysis.
- arcwall.io — explicitly offers architecture-diagram upload → STRIDE threat model, attack vectors, trust boundaries, mitigations, and compliance mappings.
- learn.microsoft.com — not AI-first, but still a very solid option if you want a structured STRIDE model and deterministic analysis. You create a DFD and identify trust boundaries; the tool then guides threat identification and mitigations.
One important caveat
I wouldn't treat an AI-generated threat model as the final security assessment. An architecture image often doesn't tell the model things that are crucial to threat analysis—authentication assumptions, IAM roles, network controls, data sensitivity, tenancy boundaries, third-party trust, deployment configuration, etc.
A good workflow is:
Architecture diagram → AI decomposition → validate components/data flows/trust boundaries → STRIDE/attack-path analysis → human security review → prioritized mitigations
That's also why I like IriusRisk/ThreatModeler more than simply uploading a diagram to a general-purpose AI: they attempt to turn the visual architecture into a structured security model, rather than just producing a prose list of scary-sounding vulnerabilities. IriusRisk, for example, explicitly separates AI-assisted model creation from its deterministic rules engine.
If you have the architecture diagram available, you can upload it here. I can analyze it and produce a practical threat model covering:
- Assets and sensitive data
- Trust boundaries
- Entry points and attack surfaces
- Data flows
- Threat actors
- STRIDE threats
- Authentication/authorization weaknesses
- Injection and data-validation risks
- SSRF and network pivot opportunities
- Secrets/credential exposure
- Supply-chain and third-party risks
- Cloud/IAM misconfiguration risks
- Abuse cases and attack paths
- Severity/prioritization
- Concrete mitigations
I can also format the result as a security-review-ready threat model with a threat ID, affected component, attack scenario, likelihood, impact, severity, and recommended control.
That's also why I like IriusRisk/ThreatModeler more than simply uploading a diagram to a general-purpose AI: they attempt to turn the visual architecture into a structured security model, rather than just producing a prose list of scary-sounding vulnerabilities. IriusRisk, for example, explicitly separates AI-assisted model creation from its deterministic rules engine.
If you have the architecture diagram available, you can upload it here. I can analyze it and produce a practical threat model covering: