Shortened Threat modeling section #358
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jgadsden
reviewed
Feb 14, 2025
| * Use standard terminology throughout the document | ||
| * Categorize the threat with respect to probability of occurrence | ||
| and impact. | ||
| * Have an [incident response][IR] idea in mind for each threat. |
There was a problem hiding this comment.
typically we would not have an incident response to each threat, it should be a remediation instead?
There was a problem hiding this comment.
Ah, oversight on my part. I'll change that
jgadsden
reviewed
Feb 14, 2025
| * Architecture diagrams | ||
| * Dataflow transitions | ||
| * Data classifications | ||
| **1 What to work on**? |
There was a problem hiding this comment.
The wording 'What are we working on?' is taken from the 4 questions, so we should keep that
|
@jgadsden Can this be closed now? |
|
Thanks for the revisions @pUrGe12 , and it should stay open for now because the page is not quite right. |
|
yep, that seems right.
…On Wed, 19 Feb, 2025, 8:42 pm Jon Gadsden, ***@***.***> wrote:
Thanks for the revisions @pUrGe12 <https://github.com/pUrGe12> , and it
should stay open for now because the page is not quite right.
Hard to put my finger on it, but Threat Modeling is a complex subject that
is highly nuanced, so the wording has to be very justifiable
—
Reply to this email directly, view it on GitHub
<#358 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BER5OHZK6G2YWE2FDVRFV3T2QSNMVAVCNFSM6AAAAABXEHOB4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRYHE2DEMRYHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: jgadsden]*jgadsden* left a comment
(OWASP/www-project-developer-guide#358)
<#358 (comment)>
Thanks for the revisions @pUrGe12 <https://github.com/pUrGe12> , and it
should stay open for now because the page is not quite right.
Hard to put my finger on it, but Threat Modeling is a complex subject that
is highly nuanced, so the wording has to be very justifiable
—
Reply to this email directly, view it on GitHub
<#358 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BER5OHZK6G2YWE2FDVRFV3T2QSNMVAVCNFSM6AAAAABXEHOB4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRYHE2DEMRYHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary :
Shortened threat modeling section, included more in-doc links as discussed in #344
Description for the changelog :
Shortened threat modeling section.
closes #344