English? Ahead!
Deutsch? Lies hier.
First collaborative Threat Modeling of TMC DACH!
- Slides (
): Threat Modeling Feierabend - Online Dating im Tinder-Stil
- Results (
): Threat Modeling Feierabend - Online Dating im Tinder-Stil - Ergebnisse
On Tuesday, 22.04.2025, 17 threat modeling enthusiasts met for the 1st Threat Modeling Feierabend (after work) of the German-speaking TMC chapter for the DACH region. There were participants from a wide range of backgrounds: Beginners, people with little experience and professionals. What they all had in common was that Threat Modeling was close to their hearts.
The aim of the “Threat Modeling Feierabend” format is to subject a simple system to threat modeling in a relaxed atmosphere. In doing so, a Threat modeling method meets a
topic.
Since both are easily accessible, even people without threat modeling experience can jump right in.
It quickly became clear that hearts played a role: The threat analysis system was an online dating platform like Tinder or Grindr!
Methods of the evening -
ready to go in less than 30 minutes
What we didn’t want to do was spend an entire evening debating how we actually want to threat-model. Instead, we let ourselves be challenged by Chris Romeo’s @edgeroute rule:
“It is not allowed to talk about Threat Modeling for more than 30 minutes until people have to threat model”
The methods of the evening, selected and presented by Hendrik Ewerlin @hewerlin :
(All the German slides: Threat Modeling Feierabend - Online Dating im Tinder-Stil)
- 4 Question Framework by Adam Shostack @adamshostack
- ThreatPad Online Editor for
threats and
mitigations - see also Meet ThreatPad and ThreatPad
- Prepared system model - see below
- STRIDE
- Safety
- NIST Cyber Security Framework
This is inspired by this post by @AppSecSeanner
The example threat shows someone worried about forgetting swim suit. Suggested mitigations are buy new
packing list
go to beach where you can swim naked (and, related, safe money so we can afford to buy new)
Illustrating the NIST strategies:
make harder / prevent (as part of protect)
reduce harm (as part of protect)
detect
respond
recover ( with super beautiful German word wiedergutmachen: make-good-again)
System model as a start-up aid
The system model was already provided as a starting aid. The advantage: full focus on threats and
measures. And: Few technical details were required for the threat analysis, although these were also well reflected in the threats later on. Real-life threats were clearly part of the analysis.
The first model shows the process of how two users come into contact on the platform. The individual stages ( #AuthN, #Profile = #Profil, #Location = #Standort, #Discovery = #Erkunden, #Swiping = #Swipen, #Matches, #Chat, #Dating ) structure the threat identification as keywords.
The second model sorts the same topics into an architectural view and shows a classic user - client - service - server - database architecture with client distribution via an app store. A few naive threat actors are also introduced and named to offer words for the conversation.
Collaborative Threat Modeling
Then 3 teams of 5-6 people got together in break-out rooms. They identified threats and
mitigations. Lilith, Laura and Hendrik moderated the rooms.
Participants saw a screen like this: On the left, the ThreatPad, where threats and
mitigations were interactively written down from the lively conversation. On the right, a collage of system model and methods. Because ThreatPad is so slim, it takes up little space and leaves enough room for context while sharing the screen. Since only the current threat is shown, the discussion is focused… (well, more or less
)
All three discussions were lively, bubbly and produced exciting threats and mitigations! We would like to thank all our participants for the great encounter and the stimulating experience and results!
After an initial round, the most important findings and threats were presented in a joint session. Then it was time for the final spurt of countermeasures. It was pointed out once again that these can be quite diverse and are not always just avoidance or mitigation. Timely recognition or correction, making amends, also play a role. We were able to see how system providers can also make their users’ lives safer outside of the software by offering additional functions or information.
Results
Here is the results als ThreatPad PDF-Export, raw, without post processing
We have had AI translate our results and were not really satisfied to present you that stuff. Stay tuned, as we will share some more of our insights on the content level…
(If you can’t wait, you may want process the results yourself.)
The results are particularly impressive considering the limited time: 2x30 minutes. Also bear in mind that people from different backgrounds worked together for the first time.
Impressive! You guys are awesome!!!
Risk assessment, threat ranking or determining the essence was not part of the evening.
What are your findings?
Final exchange
In the concluding discussion, Christoph expressed what everyone was thinking: That it is clearly recognizable how valuable it is to look at things together and that this brings up a variety of perspectives! Surprisingly, despite intensive preparation, the organizers were also able to learn a lot of new things.
One very important question came up at the end. This is often asked when teams start out with threat modeling: “What tools do I need?” Ron’s answer: a sheet of paper and a simple list like Excel. Sure, tools for automation and organization help, but a picture of “What are we working on?”, a list of “What can go wrong?” and “What do we want to do about it?” often works wonders. We can start simple and then get better…
Next event: May 20th
Threat Modeling the Clouds with OWASP Cumulus and Christoph Niehofff
The evening flew by and we are looking forward to the next one! After our successful founding meeting and the first Threat Modeling Feierabend, you can now look forward to the next event from our chapter! TMC DACH: OWASP Cumulus and security games - Threat Modeling Feierabend with Christoph Niehoff, the creator of OWASP Cumulus, on Mai 20th 2025 from 5 pm via Zoom. The event language is German.