Skip to content

Commit 93550b7

Browse files
author
jon gadsden
committed
add content for LINDDUN GO
1 parent 452133c commit 93550b7

File tree

4 files changed

+90
-4
lines changed

4 files changed

+90
-4
lines changed

.github/workflows/release.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ jobs:
3131
find release -name "*.md" -exec sed -i "/www-project-developer-guide\/issues\/new?labels/d" {} +
3232
find release -name "*.md" -exec sed -i "/www-project-developer-guide\/blob\/main/d" {} +
3333
find release -name "*.md" -exec \
34-
sed -i "s/.*the latest contributions to the Developer Guide.*/\#\#\# Release version ${{ GITHUB_REF_NAME }}/" {} +
34+
sed -i "s/.*the latest contributions to the Developer Guide.*/\#\#\# Release version $GITHUB_REF_NAME/" {} +
3535
find release -name "*.md" -exec sed -i "s/ (Draft)//gI" {} +
3636
find release -name "*.md" -exec sed -i "/order: / s/$/0/" {} +
3737
@@ -83,7 +83,7 @@ jobs:
8383
- name: Create pull request
8484
uses: peter-evans/[email protected]
8585
with:
86-
title: "Release for version $GITHUB_REF_NAME"
86+
title: "Release for version ${{ GITHUB_REF_NAME }}"
8787
body: |
8888
**Summary** :
8989
Pull request automatically generated for the latest release version

.wordlist.txt

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -469,4 +469,8 @@ testssl
469469
DrHEADer
470470
csp
471471
DocX
472-
MOBI
472+
MOBI
473+
linddun
474+
LINNDUN
475+
DPO
476+
CISO
Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
---
2+
3+
title: Threat Modeling and LINDDUN GO
4+
layout: col-document
5+
tags: OWASP Developer Guide
6+
contributors: Jon Gadsden
7+
document: OWASP Developer Guide
8+
order: 615
9+
permalink: /draft/design/threat_modeling/linddun-go/
10+
11+
---
12+
13+
{% include breadcrumb.html %}
14+
15+
### 4.1.4 Threat Modeling and LINDDUN GO
16+
17+
LINNDUN GO is a card game used to help derive privacy requirements during the software development life cycle.
18+
The LINNDUN GO card set can be [downloaded][linddun-go-cards] as a PDF and then printed out.
19+
20+
#### What is LINDDUN GO?
21+
22+
[LINDDUN GO][linddun-go] helps identify potential privacy threats based on the key LINDDUN threats to privacy:
23+
24+
* Linking
25+
* Identifying
26+
* Non-repudiation
27+
* Detecting
28+
* Data Disclosure
29+
* Unawareness
30+
* Non-compliance
31+
32+
LINNDUN GO is similar to OWASP [Cornucopia][cornucopia] in that it takes the form of a set of cards that
33+
can be used to gamify the process of identifying application privacy / security requirements.
34+
The deck of 33 cards are arranged in suits that match each category of threats to privacy,
35+
and there is a [set of rules][linddun-go-rules] to structure the game sessions.
36+
Each LINDDUN GO card illustrates a single common privacy threat and suggested remediations.
37+
38+
#### Why use it?
39+
40+
[LINDDUN][linddun] is an approach to threat modeling from a privacy perspective.
41+
It is a methodology that is useful to structure and guide the identification of threats to privacy,
42+
and also helps with suggestions for the mitigation of any threats.
43+
44+
[LINDDUN GO][linddun-go] gamifies this approach to privacy with a set of cards and rules
45+
to guide the identification process for threats to the privacy provided by the application.
46+
This is a change to other established processes and provides a different and useful perspective to the system.
47+
48+
#### How to use LINDDUN GO
49+
50+
The idea for a LINDDUN GO is that it is played in person by a diverse team with as varied a set of viewpoints as possible.
51+
The advice from the LINDDUN GO 'getting started' instructions is that this team contains some or all of:
52+
53+
* domain experts
54+
* system architects
55+
* developers
56+
* the Data Protection Officer (DPO)
57+
* legal experts
58+
* the Chief Information Security Officer (CISO)
59+
* privacy champions
60+
61+
The application should have already been described by an architecture diagram or data flow diagram
62+
so that the players have something to refer to during the game.
63+
[Download][linddun-go-cards] and printout the deck of cards.
64+
65+
Follow the [set of rules][linddun-go-rules] to structure the game session, record the outcome and act on it.
66+
The outcome of the game is to identify possible privacy threats and propose remediations;
67+
as well as having a good time of course.
68+
69+
----
70+
71+
The OWASP Developer Guide is a community effort; if there is something that needs changing
72+
then [submit an issue][issue060105] or [edit on GitHub][edit060105].
73+
74+
[cornucopia]: https://owasp.org/www-project-cornucopia/
75+
[edit060105]: https://github.com/OWASP/www-project-developer-guide/blob/main/draft/06-design/01-threat-modeling/05-linddun-go.md
76+
[issue060105]: https://github.com/OWASP/www-project-developer-guide/issues/new?labels=content&template=request.md&title=Update:%2006-design/01-threat-modeling/05-linddun-go
77+
[linddun]: https://linddun.org/
78+
[linddun-go]: https://linddun.org/go/
79+
[linddun-go-cards]: https://downloads.linddun.org/linddun-go/default/latest/go.pdf
80+
[linddun-go-rules]: https://linddun.org/go-getting-started/
81+
82+
\newpage

draft/09-training-education/01-vulnerable-apps/01-juice-shop.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
title: Juice Shop
44
layout: col-document
55
tags: OWASP Developer Guide
6-
contributors:
6+
contributors: Jon Gadsden
77
document: OWASP Developer Guide
88
order: 911
99
permalink: /draft/training_education/vulnerable_applications/juice_shop/

0 commit comments

Comments
 (0)