Skip to content

Commit 59e4750

Browse files
authored
Update links in Threat Modeling cheat sheet (#1913)
* fix broken links in Threat Modeling cheat-sheet * wording for Threat Modeling cheat sheet aligned with CIA and AAA triads
1 parent f58a280 commit 59e4750

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

cheatsheets/Threat_Modeling_Cheat_Sheet.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22

33
## Introduction
44

5-
Threat modeling is an important concept for modern application developers to understand. The goal of this cheatsheet is to provide a concise, but actionable, reference for both those new to threat modeling and those seeking a refresher. The official project page is [https://owasp.org/www-project-threat-model/](https://owasp.org/www-project-threat-model/).
5+
Threat modeling is an important concept for modern application developers to understand. The goal of this cheatsheet is to provide a concise, but actionable, reference for both those new to threat modeling and those seeking a refresher.
6+
The OWASP [Threat Modeling project](https://owasp.org/www-project-threat-modeling/) provides further information on various aspects of threat modeling.
67

78
## Overview
89

@@ -33,7 +34,7 @@ Proper threat modeling requires participants to think creatively and critically
3334

3435
### Improved Visibility of Target of Evaluation (TOE)
3536

36-
Threat modeling requires a deep understanding of the system being evaluated. To properly threat model, one must understand data flows, trust boundaries, and other characteristics of the system. Thus, [Stiliyana Simeonova](https://securityintelligence.com/threat-modeling-in-the-enterprise-part-1-understanding-the-basics/) asserts that improved visibility into a system and its interactions is one advantage of threat modeling.
37+
Threat modeling requires a deep understanding of the system being evaluated. To properly threat model, one must understand data flows, trust boundaries, and other characteristics of the system. Thus improved visibility into a system and its interactions is one advantage of threat modeling.
3738

3839
## Addressing Each Question
3940

@@ -69,7 +70,7 @@ Cloud-native systems introduce unique considerations for threat modeling due to
6970
- **Dynamic environments:** container orchestration, serverless functions, and ephemeral infrastructure.
7071
- **Compliance and data residency:** ensuring that workloads meet jurisdictional and privacy requirements.
7172

72-
Cloud threat modeling frameworks such as [Microsoft’s Cloud Security Threat Modeling](https://learn.microsoft.com/en-us/azure/security/develop/threat-modeling-tool-cloud), [OWASP Cloud Security Project](https://owasp.org/www-project-cloud-security/), and AWS’s [Well-Architected Framework – Security Pillar](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/welcome.html) can serve as references.
73+
Cloud threat modeling frameworks such as AWS’s [Well-Architected Framework – Security Pillar](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/welcome.html) can serve as references.
7374

7475
### Threat Identification
7576

@@ -79,10 +80,10 @@ STRIDE is a mature and popular threat modeling technique and mnemonic originally
7980

8081
| Threat Category | Violates | Examples |
8182
| --------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
82-
| **S**poofing | Authenticity | An attacker steals the authentication token of a legitimate user and uses it to impersonate the user. |
83+
| **S**poofing | Authentication | An attacker steals the authentication token of a legitimate user and uses it to impersonate the user. |
8384
| **T**ampering | Integrity | An attacker abuses the application to perform unintended updates to a database. |
84-
| **R**epudiation | Non-repudiability | An attacker manipulates logs to cover their actions. |
85-
| **I**nformation Disclosure | Confidentiality | An attacker extracts data from a database containing user account info. |
85+
| **R**epudiation | Accounting | An attacker manipulates logs to cover their actions. |
86+
| **I**nformation Disclosure | Confidentiality | An attacker extracts data from a database containing user account info. |
8687
| **D**enial of Service | Availability | An attacker locks a legitimate user out of their account by performing many failed authentication attempts. |
8788
| **E**levation of Privileges | Authorization | An attacker tampers with a JWT to change their role. |
8889

0 commit comments

Comments
 (0)