Threat Modeling Testing is a new concept with a main goal, convert STRIDE threats into executable checks you can run in your CI/CD, so known threats don’t become real incidents.
Threat modeling often ends as diagrams, documents or "plans": risks are identified, but nothing verifies that mitigations actually work. With today’s delivery speed (and AI-assisted generation), “we discussed it” is not enough, controls must be continuously checked.
This talk introduces TMT (Threat Modeling Testing): a brand new practical way to turn threats into testable hypotheses with expected evidence. Using a real style case (sensitive data exposure caused by a misconfigured Elastic search index), I will show why a known and identified threat still shipped, and how a small set of derived tests would have caught it earlier.
Using STRIDE framework as a generator for test ideas, this session wants to show how each category becomes an executable check (e.g., spoofing, information disclosure, elevation of privilege), written in a clear Given/When/Then style. Finally, a collaborative cheatsheet about TMT will be shared with the audience (https://github.com/testingsoul/TMT-CheatSheets).
Attendees will leave with a reusable template to move from “threats identified” to “threats continuously verified” even if your product doesn’t have a dedicated security team or a previous Threat Model.