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:
There is no OPSEC based threat modeling unless its in context SDLC
Describe the solution you'd like:
I would like an option to use Threat-Dragon to create OPSEC or Operation Security based threat model
Additional context:
Most threat models are defined in terms of software developers life cycle or IT. OPSEC applies to IT and all domains especially physical. I could find no OPSEC threat models and think this could easily be added to Threat-Dragon and increase the user baser. The ability to easily create OPSEC threat models and display them especially for the physical domain has a lot of value. See an good example here: https://old.reddit.com/r/opsec/comments/eh6uvc/want_to_learn_opsec_as_a_total_beginner_start_here/
The text was updated successfully, but these errors were encountered:
yes, certainly sounds interesting - can you take this on @PowerPress ?
I will assign it to you, but please decline it if you do not have the time to do it
Describe what problem your feature request solves:
There is no OPSEC based threat modeling unless its in context SDLC
Describe the solution you'd like:
I would like an option to use Threat-Dragon to create OPSEC or Operation Security based threat model
Additional context:
Most threat models are defined in terms of software developers life cycle or IT. OPSEC applies to IT and all domains especially physical. I could find no OPSEC threat models and think this could easily be added to Threat-Dragon and increase the user baser. The ability to easily create OPSEC threat models and display them especially for the physical domain has a lot of value. See an good example here: https://old.reddit.com/r/opsec/comments/eh6uvc/want_to_learn_opsec_as_a_total_beginner_start_here/
The text was updated successfully, but these errors were encountered: