When a method call in your application fails, what does your application do? How much do you reveal? Do you return friendly error information to end users? Do you pass valuable exception information back to the caller? Does your application fail gracefully? How are you keeping secrets (confidentiality)? How are you tamper-proofing your data or libraries (integrity)? How are you providing seeds for random values that must be cryptographically strong? Cryptography refers to how your application enforces confidentiality and integrity Who does your application run as? Which databases does it connect to? How is your application administered? How are these settings secured? Configuration management refers to how your application handles these operational issues

Who are you talking to? Communication Security ensures all communication done is as secure as possible What can you do? Authorization is how your application provides access controls for resources and operations Who are you? Authentication is the process where an entity proves the identity of another entity, typically through credentials, such as a user name and password Who did what and when? Auditing and logging refer to how your application records security-related events The Threat Modeling Tool mitigations are categorized according to the Web Application Security Frame, which consists of the following: Category Visit the Threat Modeling Tool to get started today! Mitigation categories Also, we designed the tool with non-security experts in mind, making threat modeling easier for all developers by providing clear guidance on creating and analyzing threat models.

As a result, it greatly reduces the total cost of development. It allows software architects to identify and mitigate potential security issues early, when they are relatively easy and cost-effective to resolve. The Threat Modeling Tool is a core element of the Microsoft Security Development Lifecycle (SDL).

Ms sdl threat modeling tool