Threat mitigation is an important part of the security development lifecycle (SDL) and at NCC Group we have been performing a number of threat modeling workshops focused specifically on the automotive sector. Step 3 (threat elicitation) is therefore the focus of this document. Matt Lewis Tool Release, Transport July 20, 2016. customer experience improvement program during installation or at any time from the Settings-> Options menu within the Threat Modeling Tool and deselecting 'Take part in anonymous customer experience improvement program.
This document was actually used as baseline during a descriptive study (for the evaluation of LINDDUN). Contribute to microsoft/threat-modeling-templates development by creating an account on GitHub. The process of securing applications begins with understanding the security threats they face and hence the generation of a Threat Modeling Document is one of the corner stones of a Secure Development Lifecycle (SDL). This document also illustrates the easy transition from the client-server diagram to the DFD required by LINDDUN.Īnother example involves a smart grid system that is being evaluated for privacy threats using LINDDUN. Threat Modeling is the structured process by which we come to identify, categorize and document application level risks. Note that in this example has been worked out using the original LINDDUN and thus not take into account the updated LINDDUN trees or the updated fifth step (mitigation strategies) of the methodology.Ī more extensive execution of LINDDUN is the step-by-step application of (the original) LINDDUN to a patient community system (steps 1-4). Once he clicks on the analysis view from the icon menu selection (file with magnifying glass), he is taken to a list of generated threats the Threat Modeling Tool found based on the default template, which uses the SDL approach called STRIDE (Spoofing, Tampering, Info Disclosure, Repudiation, Denial of Service and Elevation of Privilege).
Sdl threat modeling tool template full#
The full running example is available in the LINDDUN paper. These examples thus do not yet take into account the updated solution-oriented steps, nor do they consider the updated LINDDUN threat trees, as they closely follow the methodology and threat trees described in the original LINDDUN paper.
Note that currently these examples are still based on the original LINDDUN methodology and LINDDUN threat trees. Below you can find a number of worked out examples of the LINDDUN methodology.