Skip to content

Commit e361d50

Browse files
anandchughanand chugh
and
anand chugh
authored
Adding threat modeling example to security documentation (microsoft#891)
* Adding threat modeling example * [MegaLinter] Apply linters fixes * Fixing review comments * Fixing linting issues * Fixing dead link * Fixing dead link * Adding unchanged files form main branch * Fixing review comments * [MegaLinter] Apply linters fixes Co-authored-by: anandchugh <[email protected]> Co-authored-by: anand chugh <[email protected]>
1 parent b42b903 commit e361d50

7 files changed

+111
-0
lines changed

docs/security/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ When requesting a security review for your application, please make sure you hav
1414
- [Web Application Security Quick Reference](https://owasp.org/www-pdf-archive//OWASP_Web_Application_Security_Quick_Reference_Guide_0.3.pdf)
1515
- [Security Mindset/Creating a Security Program Quick Start](https://github.com/OWASP/Quick-Start-Guide/blob/master/OWASP%20Quick%20Start%20Guide.pdf?raw=true)
1616
- [Automated Secret Detection](./secret-detection.md)
17+
- [Threat Modelling](./threat-modelling.md)
1718

1819
## Azure DevOps Security
1920

docs/security/images/arch_diagram.png

348 KB
Loading

docs/security/images/data_flow.png

217 KB
Loading

docs/security/images/threat_list.png

147 KB
Loading

docs/security/images/threat_model.png

404 KB
Loading

docs/security/threat-modelling-example.md

Lines changed: 83 additions & 0 deletions
Large diffs are not rendered by default.

docs/security/threat-modelling.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Threat Modeling
2+
3+
Threat modeling is an effective way to help secure your systems, applications, networks, and services. It's a systematic approach that identifies potential threats and recommendations to help reduce risk and meet security objectives earlier in the development lifecycle.
4+
5+
## Threat Modeling Phases
6+
7+
1. *Diagram*
8+
Capture all requirements for your system and create a data-flow diagram
9+
2. *Identify*
10+
Apply a threat-modeling framework to the data-flow diagram and find potential security issues. Here we can use [STRIDE framework](https://learn.microsoft.com/en-us/training/modules/tm-use-a-framework-to-identify-threats-and-find-ways-to-reduce-or-eliminate-risk/1b-threat-modeling-framework) to identify the threats.
11+
3. *Mitigate*
12+
Decide how to approach each issue with the appropriate combination of security controls.
13+
4. *Validate*
14+
Verify requirements are met, issues are found, and security controls are implemented.
15+
16+
Example of these phases is covered in the [threat modelling example.](./threat-modelling-example.md)
17+
More details about these phases can be found at [Threat Modeling Security Fundamentals.](https://learn.microsoft.com/en-us/training/paths/tm-threat-modeling-fundamentals/)
18+
19+
## Threat Modeling Example
20+
21+
[Here is an example](./threat-modelling-example.md) of a threat modeling document which talks about the architecture and different phases involved in the threat modeling. This document can be used as reference template for creating threat modeling documents.
22+
23+
## References
24+
25+
* [Threat Modeling](https://www.microsoft.com/en-us/securityengineering/sdl/threatmodeling)
26+
* [Microsoft Threat Modeling Tool](https://learn.microsoft.com/en-us/azure/security/develop/threat-modeling-tool)
27+
* [STRIDE (Threat modeling framework)](https://learn.microsoft.com/en-us/training/modules/tm-use-a-framework-to-identify-threats-and-find-ways-to-reduce-or-eliminate-risk/1b-threat-modeling-framework)

0 commit comments

Comments
 (0)