Multi-dimensional threat analysis method and system based on STRIDE threat modeling
By adding the association relationship between threat components and types in STRIDE threat modeling, a multi-dimensional threat analysis method is adopted to solve the problem that STRIDE threat modeling cannot determine the location of threat attacks in data security, achieving comprehensive and immediate threat discovery , improves software development efficiency.
Patent Information
- Application Number
- CN202411093232.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-09
- Publication Date
- 2024-11-22
AI Technical Summary
STRIDE threat modeling has limitations in data security applications, and it is impossible to determine the specific location of threat attacks, and it is impossible to build a complete security solution.
By increasing the association between threat components and threat types, a multi-dimensional threat analysis method is adopted, including business scenario decomposition, data flow graph mapping, threat component identification and threat dictionary establishment, to determine threat components and their mitigation measures, and to build threat and components Affiliate relationship dictionary, supports dimension expansion.
It realizes comprehensive and immediate discovery of threats, and improves the efficiency of software development. The expansion of new threats only requires adding key values and components, without rebuilding dictionaries, which significantly improves the immediacy of threat discovery.
Smart Images

Figure CN119004455A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of software development, and in particular relates to a multi-dimensional threat analysis method and system based on STRIDE threat modeling. Background Art
[0002] The statements in this section merely provide background information related to the present invention and do not necessarily constitute prior art.
[0003] In recent years, with the popularization of Internet applications and the development of software engineering, the functions and structures of software systems have become increasingly complex, and the threats faced by the systems are also increasing; threat modeling, as a technology for discovering potential risks in system structures in the early stages of software design, has become an important means to solve software security problems; many companies in the industry use STRIDE threat modeling technology to conduct threat analysis from the perspective of developers to prevent and eliminate threats in enterprise systems.
[0004] STRIDE threat modeling is a threat modeling method proposed by Microsoft. It divides threat types into Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service and Elevation of Privilege. It classifies known threats to the system and takes corresponding mitigation measures. However, the STRIDE security threat model has limitations when applied to data security solutions: the classification is one-dimensional, and after analysis, it can only know that the system may face attacks from a certain type of threat, but it cannot determine where in the system the attack from such a threat occurs, and it is impossible to build a complete security solution. Summary of the invention
[0005] To overcome the deficiencies of the above-mentioned prior art, the present invention provides a multi-dimensional threat analysis method and system based on STRIDE threat modeling, which analyzes and solves threats to data security from multiple dimensions.
[0006] To achieve the above objectives, one or more embodiments of the present invention provide the following technical solutions:
[0007] A first aspect of the present invention provides a multi-dimensional threat analysis method based on STRIDE threat modeling.
[0008] Based on the multi-dimensional threat analysis method of STRIDE threat modeling, the STRIDE threat modeling method is improved to increase the association between threat components and threat types, so as to identify the threat components that cause threats and take mitigation measures for the threat components, including:
[0009] Decompose the business scenarios involved in the software to be analyzed and identify the assets in each scenario;
[0010] Using assets as data, draw a data flow diagram for each scenario and identify threat components in the data flow diagram;
[0011] Perform threat analysis on the interaction data between threat components, determine the threat type of each threat component from the threat knowledge base, establish a threat dictionary, and store the association between threat components and threat types;
[0012] Determine the threat type of the software to be analyzed, and then search for the corresponding threat component from the threat dictionary;
[0013] For the threat components found, determine the corresponding threat mitigation measures.
[0014] Furthermore, the decomposition of the business scenarios is to divide the business scenarios involved in the software to be analyzed;
[0015] The assets are valuable resources that are vulnerable to attack and threats, including confidential data, private data and important data.
[0016] Furthermore, drawing a data flow diagram for each scenario is to perform data flow analysis on the scenario to obtain four core elements of the data flow diagram: external entity, process, data flow, and data storage, thereby obtaining the data flow diagram.
[0017] Furthermore, the threat knowledge base stores various threat types and corresponding threat mitigation measures.
[0018] Furthermore, the establishment of the threat dictionary is specifically as follows:
[0019] Identify possible security threats in the business by analyzing the customer's business needs, and determine the relationship between threat components and threat types;
[0020] Identify potential security requirements from the interactions between components, and determine the relationship between threat components and threat types;
[0021] By reviewing the code, potential threats in the code are discovered using inspection tools, thereby determining the relationship between threat components and threat types;
[0022] According to the model rules of the STRIDE model, the association between threat components and threat types is determined.
[0023] Furthermore, the threat type existing in the software to be analyzed is determined by using threat modeling software ThreadModeling Tool to identify the threat type existing in the software to be analyzed.
[0024] Furthermore, the determining of the corresponding threat mitigation measures is based on the threat mitigation measures corresponding to each threat type in the threat knowledge base, and the threat mitigation measures corresponding to the threat component are determined through the threat type corresponding to the threat component.
[0025] A second aspect of the present invention provides a multi-dimensional threat analysis system based on STRIDE threat modeling.
[0026] The multi-dimensional threat analysis system based on STRIDE threat modeling adds the association between threat components and threat types based on the STRIDE threat modeling method, thereby identifying the threat components that cause threats and taking mitigation measures for the threat components. It includes the following modules:
[0027] A scenario decomposition module is configured to: decompose the business scenarios involved in the software to be analyzed and identify the assets in each scenario;
[0028] The component identification module is configured to: draw a data flow graph for each scenario using assets as data, and identify threat components in the data flow graph;
[0029] The dictionary building module is configured to: perform threat analysis on the interaction data between threat components, determine the threat type of each threat component from the threat knowledge base, build a threat dictionary, and store the association relationship between threat components and threat types;
[0030] The threat analysis module is configured to: determine the threat type existing in the software to be analyzed, and then search for the corresponding threat component from the threat dictionary;
[0031] The measure determination module is configured to: determine corresponding threat mitigation measures for the found threat components.
[0032] A third aspect of the present invention provides a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements the steps of the multidimensional threat analysis method based on STRIDE threat modeling as described in the first aspect of the present invention.
[0033] The fourth aspect of the present invention provides an electronic device, including a memory, a processor, and a program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps in the multidimensional threat analysis method based on STRIDE threat modeling as described in the first aspect of the present invention are implemented.
[0034] One or more of the above technical solutions have the following beneficial effects:
[0035] 1) Discover the comprehensiveness of threats
[0036] The present invention associates threats with components through multiple dimensions, constructs a dictionary of corresponding relationships between threats and components, locates the relevant components where threats occur through the names of key-value threats, and supports the expansion of evaluation dimensions.
[0037] 2) Discover threats instantly and improve software development efficiency
[0038] The expansion of new threats only requires adding new key values and corresponding components without rebuilding the dictionary, which significantly improves the immediacy of threat discovery.
[0039] Advantages of additional aspects of the present invention will be given in part in the following description, and in part will become obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.
[0041] Figure 1 This is a flow chart of the method of the first embodiment.
[0042] Figure 2 This is an example diagram of the data flow diagram of the first embodiment.
[0043] Figure 3 This is a flowchart of building and analyzing a multi-dimensional threat model for the first embodiment. DETAILED DESCRIPTION
[0044] It should be noted that the following detailed descriptions are illustrative and are intended to provide further explanation of the present application. Unless otherwise specified, all technical and scientific terms used in the present invention have the same meanings as those commonly understood by those skilled in the art to which the present application belongs.
[0045] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprise" and / or "include" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.
[0046] First, let's briefly explain the STRIDE threat modeling method:
[0047] The core concept of STRIDE is to integrate security considerations into every stage of software development: requirements analysis, design, coding, testing and maintenance. Corresponding security activities are added to each stage from requirements, design to product release to reduce the number of vulnerabilities in the software and minimize security defects. Common terms involved in STRIDE are:
[0048] Asset: A valuable resource, such as data or system resources in a database or file system.
[0049] Threat: Any malicious or other event that has the potential to directly or indirectly endanger assets.
[0050] Vulnerability: A vulnerability is a defect in the specific implementation of hardware, software, protocol, or system security policy, which allows an attacker to access or damage the system without authorization.
[0051] Attack: An act of harming an asset by someone or something, which may be an act of someone threatening to cause harm or exploiting a vulnerability.
[0052] Countermeasure: Safeguards that address threats and reduce risks.
[0053] Embodiment 1
[0054] In one embodiment of the present disclosure, a multi-dimensional threat analysis method based on STRIDE threat modeling is provided, which improves the STRIDE threat modeling method by adding an association between threat components and threat types, thereby identifying threat components that cause threats and taking mitigation measures for threat components, such as Figure 1 As shown, the following steps are included:
[0055] Step S1: Decompose the business scenarios involved in the software to be analyzed and identify the assets in each scenario;
[0056] Furthermore, the decomposition of the business scenarios is to divide the business scenarios involved in the software to be analyzed;
[0057] The assets are valuable resources that are vulnerable to attack and threats, including confidential data, private data and important data.
[0058] Specifically, confirm that asset information is generally confidential data (such as customer lists, administrator passwords), private data (such as data that is only protected by property rights), and important data (encryption keys, etc.). This data is taken as the object of data security protection, and the assets are protected from aspects such as database integrity, page integrity, network and computer integrity, and application availability.
[0059] The decomposition of business scenarios is to divide the business scenarios involved in the analysis software, such as login scenarios, payment scenarios, and disaster recovery scenarios, so as to facilitate the drawing of data flow diagrams based on scenarios.
[0060] Step S2: Using assets as data, draw a data flow diagram for each scenario and identify threat components in the data flow diagram;
[0061] Furthermore, drawing a data flow diagram for each scenario is to perform data flow analysis on the scenario to obtain four core elements of the data flow diagram: external entity, process, data flow, and data storage, thereby obtaining the data flow diagram.
[0062] Specifically, the data flow model (ie, data flow graph) is the best model for threat modeling because security issues often occur in the data flow rather than in the control flow.
[0063] Perform data flow analysis on the scenario to obtain the four core elements of the data flow diagram: external entity, process, data flow, and data storage. Based on the four elements, draw the data flow diagram in the following way:
[0064] External entities: users, software systems or devices outside the control of the system, represented by a rectangular matrix.
[0065] Process: Running code, such as services and components, represented by rounded matrix or circular graphics.
[0066] Data flow: The interaction between an external entity and a process, between processes, or between a process and a data store, represented by arrows.
[0067] Data storage: Internal entities that store data, such as databases, message queues, files, etc., are represented by two parallel lines with a label in the middle.
[0068] After confirming the data flow diagram, it is necessary to introduce a trust boundary to improve the data flow diagram, so as to obtain the following Figure 2 The data flow diagram shown is analyzed, and the obtained external entities, processes, data flows, and data storage are used as threat components to obtain information of each threat component.
[0069] Step S3: Perform threat analysis on the interaction data between threat components, determine the threat type of each threat component from the threat knowledge base, establish a threat dictionary, and store the association between threat components and threat types;
[0070] Furthermore, the threat knowledge base stores various threat types and corresponding threat mitigation measures.
[0071] Specifically, the threat types in the threat knowledge base include the six threat types of the STRIDE model, as well as the threat types recorded in three open source data sources: Forward Security, Microsoft Threat Modeling Tool, and Challenge CoHapsar; and the threat mitigation measures corresponding to the threat types come partly from the records of open source data sources and partly from the experience of technical personnel.
[0072] Furthermore, the threat dictionary is established to perform threat analysis from multiple dimensions such as demand analysis and interaction between threat components, such as Figure 3 As shown, specifically:
[0073] (1) Identify possible security threats in the business based on the customer's business needs analysis, and determine the relationship between threat components and threat types;
[0074] (2) Identify potential security requirements from the interactions between components, thereby determining the relationship between threat components and threat types;
[0075] (3) By reviewing the code, potential threats in the code are discovered using inspection tools, thereby determining the relationship between threat components and threat types;
[0076] (4) According to the model rules of the STRIDE model, determine the association between threat components and threat types.
[0077] Among them, (1)-(2) are comprehensive analysis of the business based on the experience and capabilities of the technical personnel, (3) is to determine the threat type of the component through the code review tool, and the model rules in (4), as shown in Table 1, the external entity has only the threats of spoofing (S) and repudiation (R), the data flow has only the threats of tampering (T), information leakage (I), and denial of service (D), the process has all six threats (STRIDE), and the data storage has the threats of tampering (T), information leakage (I), and denial of service (D):
[0078] Table 1 Model rules
[0079]
[0080] In Table 1, red indicates that the denial threat needs to be analyzed only when the analyzed data storage is used for auditing. If it is not used for auditing, the denial threat does not need to be analyzed.
[0081] The threat components identified by the above four methods are associated with the threat types by constructing a dictionary, where the key is the threat name and the value is the component name. There may be multiple components corresponding to one threat type, so the threat dictionary is in the form of:
[0082] [{Threat type 1: [component 11, component 12, …, component 1n]}, {Threat type 2: [component 21, component 22, …, component 2n]}, …]
[0083] At the same time, the dictionary supports update operations. When there is a new threat type, the correspondence between components and threats will be rebuilt. At this time, you only need to add new key values and corresponding components without rebuilding the dictionary.
[0084] Step S4: Determine the threat type of the software to be analyzed, and then search for the corresponding threat component from the threat dictionary;
[0085] Furthermore, the threat type existing in the software to be analyzed is determined by using threat modeling software ThreadModeling Tool to identify the threat type existing in the software to be analyzed.
[0086] Specifically, according to the threat type determined by the threat modeling software Thread Modeling Tool, the corresponding component is searched in the dictionary through the threat type to find out the location range where the threat occurs.
[0087] Step S5: For the threat components found, determine corresponding threat mitigation measures.
[0088] Furthermore, the determining of the corresponding threat mitigation measures is to determine the threat mitigation measures corresponding to the threat types in the threat knowledge base and through the threat types corresponding to the threat components, to determine the threat mitigation measures corresponding to the threat components.
[0089] Specifically, the threat analysis report generated by the modeling software is summarized. Each threat corresponds to one or more components. For each type of threat, the relevant mitigation measures are determined. For example, for account theft, its attack method is to use traffic sniffer tools to sniff network traffic to obtain request data. The threat handling method (i.e., threat mitigation measure) is to use HTTPS instead of HTTP. For spoofing threats, the attack method is to use crawlers. The threat handling method is to force users to log in.
[0090] Identify relevant threat mitigation measures and build a threat model based on relevant threat mitigation measures, including:
[0091] Test the effectiveness of threat mitigation measures and conduct code review. By reviewing the code, we can find the threat information in the code and modify it in time. If the relevant threats are reduced during the test, build a model based on the current mitigation measures. If the relevant threats are still not reduced during the test, we need to re-execute the above five steps.
[0092] Threat modeling is an ongoing process. As software systems are updated and changed, and new threats emerge, when new threats are discovered, the threat scenarios, threat types, components and data flows involved, and security measures that have been taken or have failed are obtained, and the threat model is updated based on the above information.
[0093] Embodiment 2
[0094] In one embodiment of the present disclosure, a multi-dimensional threat analysis system based on STRIDE threat modeling is provided. Based on the STRIDE threat modeling method, an association relationship between threat components and threat types is added, so as to identify threat components that cause threats and take mitigation measures for the threat components, including the following modules:
[0095] A scenario decomposition module is configured to: decompose the business scenarios involved in the software to be analyzed and identify the assets in each scenario;
[0096] The component identification module is configured to: draw a data flow graph for each scenario using assets as data, and identify threat components in the data flow graph;
[0097] The dictionary building module is configured to: perform threat analysis on the interaction data between threat components, determine the threat type of each threat component from the threat knowledge base, build a threat dictionary, and store the association relationship between threat components and threat types;
[0098] The threat analysis module is configured to: determine the threat type existing in the software to be analyzed, and then search for the corresponding threat component from the threat dictionary;
[0099] The measure determination module is configured to: determine corresponding threat mitigation measures for the found threat components.
[0100] Embodiment 3
[0101] The purpose of this embodiment is to provide a computer-readable storage medium.
[0102] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the multi-dimensional threat analysis method based on STRIDE threat modeling as described in the first embodiment of the present disclosure.
[0103] Embodiment 4
[0104] The purpose of this embodiment is to provide an electronic device.
[0105] An electronic device includes a memory, a processor, and a program stored in the memory and executable on the processor. When the processor executes the program, the steps of the multidimensional threat analysis method based on STRIDE threat modeling as described in the first embodiment of the present disclosure are implemented.
[0106] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. A multi-dimensional threat analysis method based on STRIDE threat modeling, characterized by: Improve the STRIDE threat modeling method, add the relationship between threat components and threat types, so as to identify the threat components that cause threats and take mitigation measures for the threat components, including: Decompose the business scenarios involved in the software to be analyzed and identify the assets in each scenario; Using assets as data, draw a data flow diagram for each scenario and identify threat components in the data flow diagram; Perform threat analysis on the interaction data between threat components, determine the threat type of each threat component from the threat knowledge base, establish a threat dictionary, and store the association between threat components and threat types; Determine the threat type of the software to be analyzed, and then search for the corresponding threat component from the threat dictionary; For the threat components found, determine the corresponding threat mitigation measures.
2. The multi-dimensional threat analysis method based on STRIDE threat modeling according to claim 1, characterized in that: The decomposition of the business scenarios is to divide the business scenarios involved in the software to be analyzed; The assets are valuable resources that are vulnerable to attack and threats, including confidential data, private data and important data.
3. The multi-dimensional threat analysis method based on STRIDE threat modeling according to claim 1, characterized in that: The method of drawing a data flow diagram for each scenario is to perform data flow analysis on the scenario to obtain four core elements of the data flow diagram: external entity, process, data flow, and data storage, thereby obtaining the data flow diagram.
4. The multi-dimensional threat analysis method based on STRIDE threat modeling according to claim 1, characterized in that: The threat knowledge base stores various threat types and corresponding threat mitigation measures.
5. The multi-dimensional threat analysis method based on STRIDE threat modeling according to claim 1, characterized in that: The establishment of the threat dictionary is specifically as follows: Identify possible security threats in the business by analyzing the customer's business needs, and determine the relationship between threat components and threat types; Identify potential security requirements from the interactions between components, and determine the relationship between threat components and threat types; By reviewing the code, potential threats in the code are discovered using inspection tools, thereby determining the relationship between threat components and threat types; According to the model rules of the STRIDE model, the association between threat components and threat types is determined.
6. The multi-dimensional threat analysis method based on STRIDE threat modeling according to claim 1, characterized in that: The determining of the threat type existing in the software to be analyzed uses threat modeling software Thread Modeling Tool to identify the threat type existing in the software to be analyzed.
7. The multi-dimensional threat analysis method based on STRIDE threat modeling according to claim 1, characterized in that: The determining of the corresponding threat mitigation measures is based on the threat mitigation measures corresponding to each threat type in the threat knowledge base, and the threat mitigation measures corresponding to the threat components are determined through the threat types corresponding to the threat components.
8. A multi-dimensional threat analysis system based on STRIDE threat modeling, characterized by: Based on the STRIDE threat modeling method, the association between threat components and threat types is increased to identify threat components that cause threats and take mitigation measures for threat components, including the following modules: A scenario decomposition module is configured to: decompose the business scenarios involved in the software to be analyzed and identify the assets in each scenario; The component identification module is configured to: draw a data flow graph for each scenario using assets as data, and identify threat components in the data flow graph; The dictionary building module is configured to: perform threat analysis on the interaction data between threat components, determine the threat type of each threat component from the threat knowledge base, build a threat dictionary, and store the association relationship between threat components and threat types; The threat analysis module is configured to: determine the threat type existing in the software to be analyzed, and then search for the corresponding threat component from the threat dictionary; The measure determination module is configured to: determine corresponding threat mitigation measures for the found threat components.
9. An electronic device, comprising: a memory for non-transitory storage of computer readable instructions; a processor for executing the computer-readable instructions; Wherein, when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 7 is executed.
10. A storage medium, characterized in that: The computer-readable instructions are non-transitorily stored, wherein when the computer-readable instructions are executed by a computer, the method of any one of claims 1 to 7 is performed.
Citation Information
Cited By
Security design scheme generation method, device and storage medium
WO2026218737A1
