Difference between revisions of "Threat Model"
(→References) |
(→References) |
||
| Line 39: | Line 39: | ||
<references /> | <references /> | ||
| − | *Michael Howard, Praerit Garg Loren M. Kohnfelder, RAPID APPLICATION SECURITY THREAT ANALYSIS US Patent 7,243,374 B2 (2007-07-12) Abstract | + | *Michael Howard, Praerit Garg Loren M. Kohnfelder, RAPID APPLICATION SECURITY THREAT ANALYSIS [https://patentimages.storage.googleapis.com/31/17/7a/1a4fe95d4064c8/US7243374.pdf US Patent 7,243,374 B2] (2007-07-12) Abstract |
| − | <blockquote>The following Subject matter provides for modeling an | + | <blockquote>The following Subject matter provides for modeling an application's potential security threats at a logical component level early in the design phase of the application. Specifically, in a computer system, multiple model components are defined to represent respective logical elements of |
| − | application's potential security threats at a logical component level early in the design phase of the application. Specifically, in a computer system, multiple model components are defined to represent respective logical elements of | ||
the application. Each model component includes a corresponding set of security threats that could potentially be of | the application. Each model component includes a corresponding set of security threats that could potentially be of | ||
import not only to the component but also to the application | import not only to the component but also to the application | ||
| Line 48: | Line 47: | ||
the application. One or more potential security threats are | the application. One or more potential security threats are | ||
then analyzed in terms of the model components in the | then analyzed in terms of the model components in the | ||
| − | logical model. | + | logical model. </blockquote> |
[[Category:Glossary]] | [[Category:Glossary]] | ||
[[Category:Security]] | [[Category:Security]] | ||
[[Category:Vulnerability]] | [[Category:Vulnerability]] | ||
Revision as of 11:24, 30 March 2019
Full Title or Meme
A model of an information processing system that shows data flows around the system and which spots in the network that a susceptible to attack.
Context
Carnegie Mellon University Software Engineering Institute published a report on "Threat Modeling: 12 Available Methods" [1]
Loren Kohnfleder paper 'Threat Modeling Retrospective'[2]
Crispin Cowan on The Calculus of Threat Modeling [3]
Problems
Solutions
A comprehensive Data Flow Diagram
STRIDE is an acronym for: Spoofing identity, Tampering data, Repudiation (denial of responsibility), Information disclosure (data breach), Denial of Service (a.k.a. DoS), and Elevation of privilege.[4]
Each threat is a violation of a desirable property for a system:
| Threat | Desired property |
|---|---|
| Spoofing | Authenticity |
| Tampering | Integrity |
| Repudiation | Non-repudiability |
| Information disclosure | Confidentiality |
| Denial of Service | Availability |
| Elevation of Privilege | Authorization |
References
- ↑ Nataliya Shevchenko, Threat Modeling: 12 Available Methods (2018-12-03) https://insights.sei.cmu.edu/sei_blog/2018/12/threat-modeling-12-available-methods.html
- ↑ Loren Kohnfleder, Threat Modeling Retrospective () Medium https://medium.com/@lorenkohnfelder/threat-modeling-retrospective-72910908533c
- ↑ https://www.leviathansecurity.com/blog/the-calculus-of-threat-modeling
- ↑ The threats to our Products. (199) Microsoft https://adam.shostack.org/microsoft/The-Threats-To-Our-Products.docx
- Michael Howard, Praerit Garg Loren M. Kohnfelder, RAPID APPLICATION SECURITY THREAT ANALYSIS US Patent 7,243,374 B2 (2007-07-12) Abstract
The following Subject matter provides for modeling an application's potential security threats at a logical component level early in the design phase of the application. Specifically, in a computer system, multiple model components are defined to represent respective logical elements ofthe application. Each model component includes a corresponding set of security threats that could potentially be of import not only to the component but also to the application as a whole in its physical implementation. The model components are interconnected to form a logical model of the application. One or more potential security threats are then analyzed in terms of the model components in the
logical model.
