Threat model

From HandWiki
Short description: Process of identifying structural vulnerabilities

Threat modeling is a process by which potential threats, such as structural vulnerabilities or the absence of appropriate safeguards, can be identified and enumerated, and countermeasures prioritized.[1] The purpose of threat modeling is to provide defenders with a systematic analysis of what controls or defenses need to be included, given the nature of the system, the probable attacker's profile, the most likely attack vectors, and the assets most desired by an attacker. Threat modeling answers questions like "Where am I most vulnerable to attack?", "What are the most relevant threats?", and "What do I need to do to safeguard against these threats?".

Conceptually, most people incorporate some form of threat modeling in their daily life and don't even realize it.[citation needed] Commuters use threat modeling to consider what might go wrong during the morning journey to work and to take preemptive action to avoid possible accidents. Children engage in threat modeling when determining the best path toward an intended goal while avoiding the playground bully. In a more formal sense, threat modeling has been used to prioritize military defensive preparations since antiquity.

Evolution of IT-based threat modeling

Shortly after shared computing made its debut in the early 1960s, individuals began seeking ways to exploit security vulnerabilities for personal gain.[2] As a result, engineers and computer scientists soon began developing threat modeling concepts for information technology systems.

Early IT-based threat modeling methodologies were based on the concept of architectural patterns[3] first presented by Christopher Alexander in 1977. In 1988 Robert Barnard developed and successfully applied the first profile for an IT-system attacker.

In 1994, Edward Amoroso put forth the concept of a "threat tree" in his book, "Fundamentals of Computer Security Technology.[4]" The concept of a threat tree was based on decision tree diagrams. Threat trees graphically represent how a potential threat to an IT system can be exploited.

Independently, similar work was conducted by the NSA and DARPA on a structured graphical representation of how specific attacks against IT-systems could be executed. The resulting representation was called "attack trees." In 1998 Bruce Schneier published his analysis of cyber risks utilizing attack trees in his paper entitled "Toward a Secure System Engineering Methodology".[5] The paper proved to be a seminal contribution in the evolution of threat modeling for IT-systems. In Schneier's analysis, the attacker's goal is represented as a "root node," with the potential means of reaching the goal represented as "leaf nodes." Utilizing the attack tree in this way allowed cybersecurity professionals to systematically consider multiple attack vectors against any defined target.

In 1999, Microsoft cybersecurity professionals Loren Kohnfelder and Praerit Garg developed a model for considering attacks relevant to the Microsoft Windows development environment. (STRIDE[1] is an acrostic for: Spoofing identity, Tampering with data, Repudiation, Information disclosure, Denial of service, Elevation of privilege) The resultant mnemonic helps security professionals systematically determine how a potential attacker could utilize any threat included in STRIDE.

In 2003, OCTAVE[6] (Operationally Critical Threat, Asset, and Vulnerability Evaluation) method, an operations-centric threat modeling methodology, was introduced with a focus on organizational risk management.

In 2004, Frank Swiderski and Window Snyder wrote "Threat Modeling," by Microsoft press. In it they developed the concept of using threat models to create secure applications.

In 2014, Ryan Stillions expressed the idea that cyber threats should be expressed with different semantic levels, and proposed the DML (Detection Maturity Level) model.[7] An attack is an instantiation of a threat scenario which is caused by a specific attacker with a specific goal in mind and a strategy for reaching that goal. The goal and strategy represent the highest semantic levels of the DML model. This is followed by the TTP (Tactics, Techniques and Procedures) which represent intermediate semantic levels. The lowest semantic levels of the DML model are the tools used by the attacker, host and observed network artifacts such as packets and payloads, and finally atomic indicators such as IP addresses at the lowest semantic level. Current SIEM (Security Information and Event Management) tools typically only provide indicators at the lowest semantic levels. There is therefore a need to develop SIEM tools that can provide threat indicators at higher semantic levels.[8]

Threat modeling methodologies for IT purposes

Conceptually, a threat modeling practice flows from a methodology. Numerous threat modeling methodologies are available for implementation. Typically, threat modeling has been implemented using one of five approaches independently: asset-centric, attacker-centric, software-centric, value and stakeholder-centric, and hybrid. Based on the volume of published online content, the methodologies discussed below are the most well known.

STRIDE methodology

The STRIDE approach to threat modeling was introduced in 1999 at Microsoft, providing a mnemonic for developers to find 'threats to our products'.[9][|permanent dead link|dead link}}] STRIDE, Patterns and Practices, and Asset/entry point were amongst the threat modeling approaches developed and published by Microsoft. References to "the" Microsoft methodology commonly mean STRIDE and Data Flow Diagrams.

PASTA

The Process for Attack Simulation and Threat Analysis (PASTA) is a seven-step, risk-centric methodology.[10] It provides a seven-step process for aligning business objectives and technical requirements, taking into account compliance issues and business analysis. The intent of the method is to provide a dynamic threat identification, enumeration, and scoring process. Once the threat model is completed, security subject matter experts develop a detailed analysis of the identified threats. Finally, appropriate security controls can be enumerated. This methodology is intended to provide an attacker-centric view of the application and infrastructure from which defenders can develop an asset-centric mitigation strategy.

Trike

The focus of the Trike methodology[11] is using threat models as a risk-management tool. Within this framework, threat models are used to satisfy the security auditing process. Threat models are based on a "requirements model." The requirements model establishes the stakeholder-defined "acceptable" level of risk assigned to each asset class. Analysis of the requirements model yields a threat model from which threats are enumerated and assigned risk values. The completed threat model is used to construct a risk model based on asset, roles, actions, and calculated risk exposure.

VAST

The Visual, Agile and Simple Threat (VAST) methodology,[12] is based on ThreatModeler, a commercial automated threat-modeling platform. VAST requires creating two types of models: application threat models and operational threat models. Application threat models use process-flow diagrams, representing the architectural point of view. Operational threat models are created from an attacker point of view based on DFDs. This approach allows for the integration of VAST into the organization's development and DevOps lifecycles.[13]

The Hybrid Threat Modeling Method

Researchers created this method to combine the positive elements of different methodologies.[14][15][16] This methodology combines different methodologies, including SQUARE[17] and the Security Cards[18] and Personae Non Gratae.[19]

Generally accepted IT threat modeling processes

All IT-related threat modeling processes start with creating a visual representation of the application and / or infrastructure being analyzed. The application / infrastructure is decomposed into various elements to aid in the analysis. Once completed, the visual representation is used to identify and enumerate potential threats. Further analysis of the model regarding risks associated with identified threats, prioritization of threats, and enumeration of the appropriate mitigating controls depends on the methodological basis for the threat model process being utilized. The identification and enumeration of threats (or of mitigation objectives), can either be carried out in an attack-centric way or in an asset-centric way. The former focuses on the types of possible attacks that shall be mitigated, whereas the latter focuses on the assets that shall be protected.

Visual representations based on data flow diagrams

Data Flow Diagram – Online Banking Application

The Microsoft methodology, PASTA, and Trike each develop a visual representation of the application-infrastructure utilizing data flow diagrams (DFD). DFDs were developed in the 1970s as tool for system engineers to communicate, on a high level, how an application caused data to flow, be stored, and manipulated by the infrastructure upon which the application runs. Traditionally, DFDs utilize only four unique symbols: data flows, data stores, processes, and interactors. In the early 2000s, an additional symbol, trust boundaries, were added to allow DFDs to be utilized for threat modeling.

Once the application-infrastructure system is decomposed into its five elements, security experts consider each identified threat entry point against all known threat categories. Once the potential threats are identified, mitigating security controls can be enumerated or additional analysis can be performed.

Threat modeling tools

  • Microsoft's free Threat Modeling Tool (formerly SDL Threat Modeling Tool),[20] also uses the Microsoft threat modeling methodology, is based on DFD and identifies threats based on the STRIDE threat classification system. It is mainly intended for general use.
  • IriusRisk provides both a community and a commercial version of the tool. This tool focuses on creating and maintaining a living threat model throughout the SDLC. It drives the process using fully customizable questionnaires and risk model libraries, and connects to several other different tools (OWASP ZAP, BDD-Security, Threadfix) to enable automation.[21]
  • securiCAD is a threat modeling and risk management tool from the Scandinavian company foreseeti.[22] It is intended for enterprise cybersecurity management, from CISO to security engineer, including technician. securiCAD performs automated attack simulations on current and future IT architectures, identifies and quantifies risks globally, including structural vulnerabilities, and provides decision support based on results. securiCAD is available in commercial and community editions.[23]
  • SD Elements by Security Compass is a software security requirements management platform that includes automated threat modeling capabilities. A set of threats is generated by filling out a short questionnaire on the application's technical details and compliance factors. Countermeasures are included in the form of actionable tasks for developers that can be tracked and managed across the SDLC.[24]
  • OWASP Threat Dragon is a modeling tool used to create threat model diagrams as part of a secure development lifecycle. Threat Dragon follows the values and principles of the threat modeling manifesto. It can be used to record possible threats and decide on their mitigations, as well as giving a visual indication of the threat model components and threat surfaces. Threat Dragon runs either as a web application or as a desktop application. Threat Dragon supports STRIDE / LINDDUN / CIA / DIE / PLOT4ai, provides modeling diagrams and implements a rule engine to auto-generate threats and their mitigations. [25]
  • OWASP pytm is a Pythonic framework for threat modeling and the first Threat-Model-as-Code tool: define your system in Python using the elements and properties described in the pytm framework, and based on your definition, pytm can generate a Data Flow Diagram (DFD), a Sequence Diagram and most important of all, threats to your system. .[26]

Further fields of application

Threat modeling is being applied not only to IT but also to other areas such as vehicle,[27][28] building and home automation.[29] In this context, threats to security and privacy like information about the inhabitant's movement profiles, working times, and health situations are modeled as well as physical or network-based attacks. The latter could make use of more and more available smart building features, i.e., sensors (e.g., to spy on the inhabitant) and actuators (e.g., to unlock doors).[29]

Threat Modeling Manifesto

The threat modeling manifesto is a document published in 2022 by threat modeling authorities in order to clearly state the core values and principles that every threat modeler should know and follow. [30]

References

  1. ↑ 1.0 1.1 "The STRIDE Threat Model". Microsoft. 2016. https://msdn.microsoft.com/en-us/library/ee823878(v=cs.20).aspx. 
  2. ↑ McMillan, Robert (2012). "The World's First Computer Password? It Was Useless Too". Wired Business. https://www.wired.com/2012/01/computer-password/. 
  3. ↑ Shostack, Adam (2014). "Threat Modeling: Designing for Security". John Wiley & Sons Inc: Indianapolis. http://threatmodelingbook.com. 
  4. ↑ Amoroso, Edward G (1994). Fundamentals of Computer Security Technology. AT&T Bell Labs. Prentice-Hall: Upper Saddle River.. ISBN 9780131089297. http://dl.acm.org/citation.cfm?id=179237. 
  5. ↑ Schneier, Bruce (1998). "Toward A Secure System Engineering Methodology". National Security Agency: Washington. https://www.schneier.com/academic/paperfiles/paper-secure-methodology.pdf. 
  6. ↑ Alberts, Christopher (2003). "Introduction to the OCTAVE® Approach". Software Engineering Institute, Carnegie Mellon: Pittsburgh.. http://www.itgovernanceusa.com/files/Octave.pdf. 
  7. ↑ Stillions, Ryan (2014). "The DML Model". Ryan Stillions. http://ryanstillions.blogspot.no/2014/04/the-dml-model_21.html. 
  8. ↑ Bromander, Siri (2016). "Semantic Cyberthreat Modelling". Semantic Technology for Intelligence, Defence and Security (STIDS 2016). http://folk.uio.no/josang/papers/BJE2016-STIDS.pdf. 
  9. ↑ Kohnfelder, Loren; Garg, Praerit. "Threats to Our Products". Microsoft. http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-components-postattachments/00-09-88-74-86/The-threats-to-our-products.docx. Retrieved 20 September 2016. 
  10. ↑ Ucedavélez, Tony and Marco M. Morana (2015). "Risk Centric Threat Modeling: Process for Attack Simulation and Threat Analysis". John Wiley & Sons: Hobekin. http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470500964.html#. 
  11. ↑ Eddington, Michael, Brenda Larcom, and Eleanor Saitta (2005). "Trike v1 Methodology Document". http://octotrike.org/papers. 
  12. ↑ Fruhlinger, Josh (2020-04-15). "Threat modeling explained: A process for anticipating cyber attacks" (in en). https://www.csoonline.com/article/3537370/threat-modeling-explained-a-process-for-anticipating-cyber-attacks.html. 
  13. ↑ "Threat Modeling: 12 Available Methods" (in en). https://insights.sei.cmu.edu/blog/threat-modeling-12-available-methods/. 
  14. ↑ "The Hybrid Threat Modeling Method". https://insights.sei.cmu.edu/blog/the-hybrid-threat-modeling-method/. 
  15. ↑ "A Hybrid Threat Modeling Method". https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=516617. 
  16. ↑ Tarandach, Izar; Coles, Matthew J. (24 November 2020). Threat Modeling: A Practical Guide for Development Teams. ISBN 978-1492056553. 
  17. ↑ "Security Quality Requirements Engineering Technical Report". https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=7657. 
  18. ↑ https://securitycards.cs.washington.edu/
  19. ↑ "CSDL | IEEE Computer Society". https://www.computer.org/csdl/magazine/so/2014/04/mso2014040028/13rRUwInvrl. 
  20. ↑ "What's New with Microsoft Threat Modeling Tool 2016". Microsoft Secure Blog. Microsoft. 2015.
  21. ↑ "Irius Risk Risk Management Tool". Continuum Security. 2016.
  22. ↑ "foreseeti - securiCAD". https://www.foreseeti.com/securicad-enterprise/. 
  23. ↑ "Cyber Threat Modelling and Risk Management - securiCAD by foreseeti". foreseeti.
  24. ↑ "SD Elements by Security Compass". www.securitycompass.com. Retrieved 2017-03-24.
  25. ↑ "OWASP Threat Dragon".
  26. ↑ "OWASP pytm".
  27. ↑ http://publications.lib.chalmers.se/records/fulltext/252083/local_252083.pdf[bare URL PDF]
  28. ↑ Hamad, Mohammad; Prevelakis, Vassilis; Nolte, Marcus (November 2016). "Towards Comprehensive Threat Modeling for Vehicles". "Institute of Control Engineering". Publications Institute of Computer and Network Engineering. doi:10.24355/dbbs.084-201806251532-0. https://publikationsserver.tu-braunschweig.de/servlets/MCRFileNodeServlet/dbbs_derivate_00044573/Hamad_Towards_Comprehensive_Threat_Modeling_for_Vehicles.pdf. Retrieved 11 March 2019. 
  29. ↑ 29.0 29.1 Meyer, D.; Haase, J.; Eckert, M.; Klauer, B. (2016-07-01). "A threat-model for building and home automation". 2016 IEEE 14th International Conference on Industrial Informatics (INDIN). pp. 860–866. doi:10.1109/INDIN.2016.7819280. ISBN 978-1-5090-2870-2. 
  30. ↑ https://www.threatmodelingmanifesto.org//



Retrieved from "https://handwiki.org/wiki/index.php?title=Threat_model&oldid=3430458"