Week 6: Scientific paper proposal #2402
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Yet another cybersecurity risk assessment framework
Names and KTH ID
Deadline
Category
Description
Threat Modeling is an integral part of the planning and design stages in the DevSecOps cycle and keeps being highly relevant in later stages of a product development cycle. We want to explain the basics of Threat Modeling, the main motivations behind it, and the methodology on how to perform Threat Modeling which is explained in the chosen paper: https://link.springer.com/article/10.1007/s10207-023-00713-y
Relevance
Threat Modeling is a highly relevant methodology which allows modeling and security testing of software "on paper". It can help with identifying security vulnerabilities in early stages of the development, making them easier and cheaper to fix. Additionally it provides a high value when working with constraint budgets, allowing security practitioners and decision makers to prioritize effectively.