AI & Automation Listed
modern-threat-modeling
Threat model a system, service, or architecture with STRIDE, then produce a data-flow diagram, a threat ledger, a scored and ranked risk register, and prioritized remediations. Every threat maps to a valid MITRE ATT&CK technique; MITRE ATLAS techniques are added only for LLM components in the data-flow diagram. Use it for a security design review of a whole system: attack surface, trust boundaries, which risks matter most, and how to fix them first, even when the user never says STRIDE or threat model. It works from a described idea, an architecture diagram, a code repo, or any mix, and covers LLM and agent apps (prompt injection, unsafe tool calls, RAG poisoning) as well as conventional software. It also fits asks to build a DFD, enumerate threats, or map them to ATT&CK and rank by risk. Not for hardening one config file, scanning for secrets or vulnerable dependencies, debugging a live outage or DoS, incident response after a breach, improving an LLM's answer quality, or a project schedule risk register.
