> Markdown version of [/videos/936-real-world-threat-modeling?t=81](https://www.wearedevelopers.com/videos/936-real-world-threat-modeling?t=81). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Real-world Threat Modeling

Stop treating security as an afterthought. Shift left with the STRIDE framework to catch and eliminate critical vulnerabilities before a single line of code is written.

- **Speakers:** [Ali Yazdani](https://www.wearedevelopers.com/@ali-yazdani)
- **Event:** World Congress 2024
- **Published:** August 20, 2024
- **Duration:** 21:54
- **URL:** https://www.wearedevelopers.com/videos/936-real-world-threat-modeling

## Summary

Software vulnerabilities discovered in production, such as exposed Kubernetes APIs, carry severe financial and operational consequences. Traditional product deployment previously treated security testing as a final, often delayed step. To effectively reduce production vulnerabilities, organizations must shift left by moving security evaluations directly into the software design and development phases. Threat modeling serves as the foundational practice for achieving this secure design before permanent code is ever written.

Implementing robust threat modeling requires structured methodologies like the STRIDE framework (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege). Engineering teams map systems using Data Flow Diagrams (DFDs), breaking architecture down into processes, data flows, data stores, and external entities. Security teams must first define explicit trust boundaries across these architectural components. Once threats are identified, teams can address risks through four distinct strategies: mitigating the issue by strengthening security mechanisms, eliminating the vulnerable feature entirely, transferring the risk to third-party identity providers, or requiring business leaders to formally accept the structural risk.

Ultimately, threat modeling is not a one-time project but a continuous process that matures alongside active feature development. Integrating threat detection precisely between the system design and coding phases prevents systemic weaknesses from becoming easily exploitable vulnerabilities. Developer and security teams can streamline this workflow using open-source platforms like OWASP Threat Dragon, allowing engineers to visualize data flows, map STRIDE vectors to specific application interfaces, and comprehensively track mitigation plans throughout the product lifecycle.

**Keywords:** shift left security, threat modeling methodology, stride framework components, data flow diagrams, vulnerability mitigation strategies, owasp threat dragon, devsecops secure pipelines, system trust boundaries, kubernetes api security, remote code execution, elevation of privilege, information disclosure risks, risk acceptance framework, secure software design, threat actor identification, software weakness exploitation

## Chapters

1. **Real-world consequences of missing threat modeling** (00:00) — Real-world examples like a costly Kubernetes API vulnerability demonstrate the need for early security measures.
1. **Expanding the shift left security journey** (01:21) — Transitioning from late-stage testing to secure pipelines shifts security earlier into the design phase.
1. **Defining threat modeling in secure design** (03:16) — Threat modeling provides a structured way to identify and mitigate risks between the design and coding phases.
1. **Core terminologies and relationships in threat modeling** (05:10) — Mapping the cascading relationship between system weaknesses, exploitable vulnerabilities, and attacks clarifies overall risk.
1. **Using the STRIDE threat modeling methodology** (08:11) — The STRIDE framework categorizes threats into spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege.
1. **Adopting an iterative threat modeling workflow** (10:11) — Effective threat modeling requires a continuous loop of diagramming data flows, ranking risks, and deploying mitigations.
1. **Mapping STRIDE to data flow diagrams** (11:21) — Applying STRIDE categories directly to system processes, data stores, and external entities exposes critical security boundaries.
1. **Four strategies for addressing identified security threats** (13:14) — Handling discovered vulnerabilities involves choosing whether to mitigate, eliminate, transfer, or formally accept the business risk.
1. **Scoping systems with multi-level data flow diagrams** (15:39) — Deconstructing an application from a high-level overview down to specific components establishes clear trust boundaries.
1. **Implementing threat models with OWASP Threat Dragon** (18:07) — Visualizing diagrams with open-source tools tracks component threats and verifies the presence of appropriate mitigation controls.
1. **Recommended resources for continuous threat modeling education** (20:53) — Studying practical examples and reference implementations helps integrate threat modeling practices into everyday engineering workflows.

## Related Moments

- [Introducing collaborative threat modeling workshops in engineering teams](https://www.wearedevelopers.com/videos/485-we-adopted-devops-and-are-cloud-native-now-what) (from "We adopted DevOps and are Cloud-native, Now What?")
- [Pairing with teams for continuous threat modeling](https://www.wearedevelopers.com/videos/478-organizational-change-through-the-power-of-why-devsecops-enablement) (from "Organizational Change Through The Power Of Why - DevSecOps Enablement")
- [Addressing insecure design through early threat modeling](https://www.wearedevelopers.com/videos/100072-bulletproof-web-applications-the-2025-owasp-top-ten) (from "Bulletproof Web Applications: The 2025 OWASP Top Ten")
- [Integrating security across the application development lifecycle](https://www.wearedevelopers.com/videos/468-securing-your-application-software-supply-chain) (from "Securing your application software supply-chain")
- [Writing secure code and utilizing threat modeling methodologies](https://www.wearedevelopers.com/videos/726-security-pitfalls-for-software-engineers) (from "Security Pitfalls for Software Engineers")
- [Structuring implementation timelines and threat modeling cadence](https://www.wearedevelopers.com/videos/478-organizational-change-through-the-power-of-why-devsecops-enablement) (from "Organizational Change Through The Power Of Why - DevSecOps Enablement")

## Related Articles

- [Walking Into The Era of Supply Chain Risks](https://www.wearedevelopers.com/magazine/106-walking-into-the-era-of-supply-chain-risks)
- [Understanding and Mitigating Common Web Vulnerabilities](https://www.wearedevelopers.com/magazine/565-understanding-and-mitigating-common-web-vulnerabilities)
- [Events like RSAC Get You CISOs. Developers Decide What Actually Gets Deployed.](https://www.wearedevelopers.com/magazine/693-events-like-rsac-get-you-cisos-developers-decide-what-actually-gets-deployed)
- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)

## Related Jobs

- [Senior Threat Intelligence Analyst](https://www.wearedevelopers.com/jobs/ext/1684162-senior-threat-intelligence-analyst) at **ZEISS Group**
- [Engineer, Offensive Security Organization](https://www.wearedevelopers.com/jobs/ext/1992296-engineer-offensive-security-organization) at **Twilio**
- [Senior Threat Intelligence Analyst](https://www.wearedevelopers.com/jobs/ext/2000909-senior-threat-intelligence-analyst) at **ZEISS Group**
- [Staff Engineer - Offensive Security](https://www.wearedevelopers.com/jobs/ext/1226927-staff-engineer-offensive-security) at **Twilio**
- [Staff Engineer, Security Engineering Partners](https://www.wearedevelopers.com/jobs/ext/1187268-staff-engineer-security-engineering-partners) at **Twilio**
- [Security Architect - AI](https://www.wearedevelopers.com/jobs/ext/1581899-security-architect-ai) at **ZEISS Group**