-
-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reinstate automated generation of threats by element #792
Comments
@jgadsden I'm curious, was this feature removed/deprecated in 2.x for any particular reason? |
Well, only because we just did not have the engineering resource to implement it |
@jgadsden Im in the process of writing my bachelors thesis on templating threat models for IoT architectures and having had a quick look at Microsofts threat modeling tool, not having automated threat generation definitely stuck out. So did this the existing issue of non-existent templates given that's my thesis' goal #220 Hope I can help tackling both issues to some degree |
Absolutely good to have any help you can on both these issues @ryeqb |
This is a Google Summer of Code project, and the application dates for GSoC contributors are between March 18th and April 2nd |
Hi, @jgadsden! I am interested to contribute this issue under Gsoc. I am looking for some help from you to understand that issue deeply. So, that I can create an outline for the remedy. 🙂 Can you help me by providing more exposure to it, please? |
Describe what problem your feature request solves:
Version 1.x has a feature where the threats are suggested by element, for example if STRIDE:
Describe the solution you'd like:
Reinstate automated generation of threats by element
Additional context:
The text was updated successfully, but these errors were encountered: