You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what problem your feature request solves:
Multiple mitigations for a threat are possible, and also multiple threats per mitigations
Describe the solution you'd like:
revise data model of threat and mitigations to be more flexible
Additional context:
User reports:
"The data model for threat mitigations is in my opinion simply incorrrect. One threat may have many mitigations, which has different implementation status. At this moment the tool seems to allow tracking only one mitigation per threat.
Not being able to copy or move threats makes impossible to refactor the environment image later on. I would take even "make a copy of this threat to there" without any linking of contents to fix this. Without this I had to redraw the environment and do a lot of manual work to get the final report cleaned up."
The text was updated successfully, but these errors were encountered:
I agree that the schema / data model of threat dragon is not a good one
we are looking at revising the file format, schema and data model in #716 and also #850
Describe what problem your feature request solves:
Multiple mitigations for a threat are possible, and also multiple threats per mitigations
Describe the solution you'd like:
revise data model of threat and mitigations to be more flexible
Additional context:
User reports:
"The data model for threat mitigations is in my opinion simply incorrrect. One threat may have many mitigations, which has different implementation status. At this moment the tool seems to allow tracking only one mitigation per threat.
Not being able to copy or move threats makes impossible to refactor the environment image later on. I would take even "make a copy of this threat to there" without any linking of contents to fix this. Without this I had to redraw the environment and do a lot of manual work to get the final report cleaned up."
The text was updated successfully, but these errors were encountered: