To generate stub threats for later analysis: $ threatmodel -generate-threats examples/minesweeper.yaml

mitigations (optional, list of mitigation IDs that have been applied to this threat).

child_threats (optional, list of threat IDs that an attacker can attempt next).

threat_category (optional, defaults to unknown if missing).

status (optional, defaults to unmanaged if missing).

You can add the threats key to your system YAML to load existing threats for your system, for example: threats:Р”Вescription: An attacker is able to introduce malicious changes into the settings file

This will generate the following Data Flow Diagram: You can use this as follows: $ threatmodel -dfd minesweeper.yaml The following YAML is an example specification (example taken from this paper (PDF)): - name : Minesweeper description : Minesweeper threat model nodes : - name : Settings File type : Datastore id : DFD1 - name : Game File type : Datastore id : DFD2 - name : DirectX API type : ExternalEntity id : DFD3 - name : user type : ExternalEntity id : DFD4 - name : Game Application type : Process id : DFD5 boundaries : - name : System members : - DFD1 - DFD2 - DFD3 - DFD5 dataflows : - name : Settings first_node : DFD1 second_node : DFD5 bidirectional : True - name : Game Data first_node : DFD2 second_node : DFD5 bidirectional : True - name : Graphics Rendering first_node : DFD3 second_node : DFD5 - name : User Input first_node : DFD4 second_node : DFD5 (fails linter) references to mitigations that do not existР”Вata Flow Diagram YAML-based system specification.(fails linter) references to child threats that do not exist.(fails linter) threats that have not been triaged (i.e.Threatmodel -check will look for the following: check lint/check your threat model definition h, -help show this help message and exit In your CI/CD pipeline (see CircleCI job examples and the Linter section below) to flag issues.

There is also a threatmodel -check option which is effectively a linter and can be run This is done to make it easier to track why countermeasures have been implemented/applied and to aid decision-making when deciding between implementing various proposed countermeasures. This library considers countermeasures to be first-class objects, in addition to threats and DFD elements. This YAML document can be stored in version control and updated to keep track the DFD structure, the list of threats that have been considered, their mitigation status, and what compensating security controls have been applied. If you include the threats and their child-parent relationships in the YAML specification, you can also generate attack trees. Data Flow Diagrams (DFDs) can be generated using a YAML specification of the system architecture. This is a library of threat modeling tools in Python inspired by related projects like pytm. Note: this is an experimental tool in the alpha stage that is under active development, the API and YAML spec format may change.

Sdl threat modeling tool download