Skip to content

Commit

Permalink
#1227 - threat modeling as a process is out of scope
Browse files Browse the repository at this point in the history
  • Loading branch information
elarlang authored and tghosth committed Dec 14, 2023
1 parent 7b45415 commit cfd829b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion 5.0/en/0x10-V1-Architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ In this chapter, the ASVS covers the primary aspects of any sound security archi
| # | Description | L1 | L2 | L3 | CWE |
| :---: | :--- | :---: | :---: | :---: | :---: |
| **1.1.1** | [DELETED, NOT IN SCOPE] | | | | |
| **1.1.2** | Verify the use of threat modeling for every design change or sprint planning to identify threats, plan for countermeasures, facilitate appropriate risk responses, and guide security testing. | | || 1053 |
| **1.1.2** | [DELETED, NOT IN SCOPE] | | | | |
| **1.1.3** | [DELETED, NOT IN SCOPE] | | | | |
| **1.1.4** | Verify documentation and justification of all the application's trust boundaries, components, and significant data flows. | ||| 1059 |
| **1.1.5** | Verify definition and security analysis of the application's high-level architecture and all connected remote services. ([C1](https://owasp.org/www-project-proactive-controls/#div-numbering)) | ||| 1059 |
Expand Down

0 comments on commit cfd829b

Please sign in to comment.