I am designing a Threat Modeling tool. It is good at (many to many) relationships!
At it’s heart, it has a set of rules with source type, question/prompt and target type. I can configure this really flexible.
A simple set and example is
HOME => What are we working on? => PROJECT
PROJECT => What can go wrong with <X>? => THREAT
THREAT => What helps with <X>? => MITIGATION
This helps create a tree of PROJECT, THREAT and MITIGATION nodes.
If I want likelihood/impact, I might add
THREAT => How likely is <X>? => LIKELIHOOD
THREAT => How bad is <X>? => IMPACT
If I am concerned about MITIGATION bypasses, I might add
MITIGATION => How could someone bypass <X>? => THREAT
(Notice how I introduced a circular thing?)
I’m fiddling around with different variants.
Call for ideas
What would you think would be a promising set of source type => question => target type rules, so that Threat Modeling will be best supported?