What Comes After Threat Modeling?

The output of the threat modeling process includes documentation of the security aspects of the architecture of your application and a list of rated threats. The threat model helps you orchestrate development team members and focus on the most potent threats.

Important  

Threat modeling is an iterative process. The threat model is a document that evolves and that various team members can work from.

The threat model can be used by the following groups of people:

• Designers can use it to make secure design choices about technologies and functionality.

• Developers who write code can use it to mitigate risks.

• Testers can write test cases to test if the application is vulnerable to the threats identified by the analysis.

Generating a Work Item Report

From the initial threat model, you can create a more formalized work item report that can include additional attributes, such as a Bug ID, which can be used to tie the threat in with your favorite bug tracking system. In fact, you may choose to enter the identified threats in your bug tracking system and use its reporting facilities to generate the report. You can also include a status column to indicate whether or not the bug has been fixed. You should make sure the report includes the original threat number to tie it back to the threat model document.

Organize the threats in the report by network, host, and application categories. This makes the report easier to consume for different team members in different roles. Within each category, present the threats in prioritized order starting with the ones given a high risk rating followed by the threats that present less risk.