“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.” - CAR Hoare
Threat modeling has long been a “design level” activity that fits in right at the beginning of a well-defined application security strategy. However, the current speed and scale of product and security engineering has forced software teams to overlook this very critical element of software security...and rightfully so!
In this webcast, we dive into the world of application threat modeling, sharing insights on and demystifying the chatter that product teams have been exposed to and expanding on some of the cause and effects of threat modeling not seeing its rightful place in agile product engineering. The presentation also examines two schools of thought—component-driven threat modeling and offense-driven (abuser case) threat modeling—as well as their unique use cases and applicability.
- The context of threat modeling in today’s context of product engineering
- The problem with threat modeling (as we know it)
- A comparison of component-driven and defense-driven threat modeling
- Threat modeling as a route to better test case design and automation