Dear Threat Modelers,
With Team 24, we had the pleasure of participating in the Threat Modeling Hackathon 2025, where we received a Special Mention for our work—something I’m proud to share with you today! 
We chose Use Case A, focusing on the in-vehicle embedded systems of the autonomous vehicle “TMC-Drive.” While Use Case B was more familiar territory, we wanted to challenge ourselves with the complexity and novelty of embedded hardware, diagnostics, and connectivity in a real-world scenario (full system description available here). It pushed us out of our comfort zone and into a space that reflects the messy, incomplete, and sometimes ambiguous realities of threat modeling.
Our approach was to began with user stories and selected a high-impact scenario involving remote diagnostics by a technician. From there, we followed a methodical process:
- Defined system architecture and a focused Data Flow Diagram (DFD)
- Identified threat actors relevant to the chosen user story
- Mapped potential attack vectors using STRIDE
- Highlighted abuse cases where normal functionality could be misused
- Built threat scenarios, grounded in real attacker behavior, business risks, and MITRE ATT&CK mappings
- Evaluated assumptions and selected mitigations that align with operational constraints and impact.
This model is not exhaustive by design—we prioritized depth over breadth to provide decision-makers like CISOs with actionable insights, focusing on what could realistically go wrong and how to fix or contain it.
You can read our full threat model report in PDF format at the following link: [HERE]