Threat Modeling Cheat Sheet & Lightweight Threat Modeling


OWASP Threat Modeling Cheat Sheet The objective of this cheat sheet is to provide guidance to developers, reviewers, designers and architects on conducting successful threat modeling. The main goal of threat modeling is to understand the controls needed for a software system. This is a complex endeavor that could involve investigations into:

- The trust boundaries to and within the solution that we build
- The actors that interact within and outside of the trust boundaries
- Information flows within and to and from the trust boundaries
- Information persistence within and out of trust boundaries
- Vulnerabilities at trust boundaries
- Threat agents that can exploit the vulnerabilities
- Impact of exploitation of vulnerability by a threat agents
- Controls and process needed to treat specific risks

Why

Threat modeling still needs great adoption into current SDLC methodologies. Many development groups strive to apply threat modeling efforts under tight development windows. The threat cheat sheet modeling cheat sheet aims to provide prescriptive guidance on scoping, application component enumeration, threat modeling activities, and key deliverables. This workshop will also provide prescriptive tools, techniques that can be used to conduct various types of threats models that are both agnostic to various threats and platforms, as well as specific to certain types of threats. The Cheatsheet will provide a guide on how to follow a heavyweight approach to threat modeling. In addition to this, some teams may find the heavy weight approach too cumbersome and onerous - for this reason, we’ll define a lightweight approach that should represent the Minimum Viable Threat Modeling activity to follow.

What

  • DFD Template
  • Kill chain template
  • Attack tree template
  • Component enumeration techniques
  • Attack library build out and mapping
  • Proposed threat library and integration
  • Weakness library management and integration
  • Lightweight Threat Modeling Steps ** What should a lightweight process produce? ** What are the simplest list of steps we can follow to arrive at that deliverable?

Who

  • Application Architects (for DFD creation, templating)
  • Web developers of varying language backgrounds (.NET, Java, PHP, *.js, etc.)
  • DBAs/ DB Developers
  • Security professionals w/ application architecture, software development experience

Related Working Session(s)



Back to list of all Working Sessions and Tracks

Edit this page here