Threat modeling method and device
By building a security baseline for security knowledge base and parameterized fields, the problems of high difficulty and low efficiency of enterprise threat modeling are solved, and automated threat modeling is realized, efficiency is improved and costs are reduced, and process linkage and data backtracking are supported.
Patent Information
- Application Number
- CN202210240537.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-10
- Publication Date
- 2025-08-08
- Estimated Expiration
- 2042-03-10
AI Technical Summary
In the prior art, enterprises are difficult, inefficient and costly when conducting threat modeling. They mainly rely on the developer's security experience and technical level, and cannot effectively reduce the difficulty and time-consuming of complex threat modeling.
By building a security knowledge base, using the security baseline of the parameterized fields to correlate with the threat modeling data, quickly determine the security requirements parameters of the software products to be evaluated, realize automated threat modeling, and reduce the analysis difficulty and cost of developers.
It improves the efficiency of threat modeling, reduces modeling costs, realizes fast matching of security baselines and accurate acquisition of threat modeling results, and supports process linkage and long-term analysis and backtracking of data.
Smart Images
Figure CN114626069B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of artificial intelligence identification and classification technology, and in particular to a threat modeling method and device. Background Art
[0002] This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. No statement herein is admitted to be prior art by virtue of its inclusion in this section.
[0003] Threat modeling is a process that systematically identifies and assesses product security risks and threats through a structured approach, and then develops mitigation measures for these risks and threats. Currently, most companies conduct threat modeling through offline modeling documents, relying on developers' security experience. However, because threat modeling involves a wide range of threats and requires security knowledge spanning multiple domains, modeling is time-consuming. Developers' security experience and technical expertise are limited to simple modeling activities. Complex threat modeling becomes more challenging, inefficient, and costly for developers. Summary of the Invention
[0004] An embodiment of the present invention provides a threat modeling method for reducing the difficulty of threat modeling, improving modeling efficiency, and reducing modeling costs. The method includes:
[0005] Receive a threat modeling request from a user for a software product to be evaluated; the threat modeling request includes current security requirement parameters of the software product to be evaluated;
[0006] Determining a current security baseline corresponding to the current security requirement parameters based on the current security requirement parameters and a pre-built security knowledge base; the security knowledge base includes: a plurality of security baselines, each security baseline includes: an association relationship between the security requirement parameters and a plurality of threat modeling data, each item in the relationship existing in the form of a parameterized field;
[0007] Perform threat modeling based on multiple threat modeling data corresponding to the current security baseline to obtain threat modeling results.
[0008] An embodiment of the present invention further provides a threat modeling device for reducing the difficulty of threat modeling, improving modeling efficiency, and reducing modeling costs. The device includes:
[0009] A receiving module, configured to receive a threat modeling request from a user for a software product to be evaluated; the threat modeling request includes current security requirement parameters of the software product to be evaluated;
[0010] A security baseline determination module is configured to determine a current security baseline corresponding to the current security requirement parameters based on the current security requirement parameters and a pre-built security knowledge base; the security knowledge base includes: a plurality of security baselines, each security baseline includes: an association relationship between the security requirement parameters and multiple threat modeling data, each item in the relationship being in the form of a parameterized field;
[0011] The threat modeling module is used to perform threat modeling based on multiple threat modeling data corresponding to the current security baseline to obtain threat modeling results.
[0012] An embodiment of the present invention further provides a computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned threat modeling method when executing the computer program.
[0013] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which implements the above-mentioned threat modeling method when executed by a processor.
[0014] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the above-mentioned threat modeling method is implemented.
[0015] In an embodiment of the present invention, a user's threat modeling request for a software product to be evaluated is received; the threat modeling request includes current security requirement parameters of the software product to be evaluated; a current security baseline corresponding to the current security requirement parameters is determined based on the current security requirement parameters and a pre-built security knowledge base; the security knowledge base includes: multiple security baselines, each security baseline includes: an association relationship between the security requirement parameters and multiple threat modeling data, each item in the relationship exists in the form of a parameterized field; threat modeling is performed based on the multiple threat modeling data corresponding to the current security baseline to obtain a threat modeling result. Compared with the technical solutions in the prior art that rely on the security experience and technical level of developers to perform threat modeling, the pre-built security knowledge base can quickly determine the security baseline corresponding to the current security requirement parameters of the software product to be evaluated. The security baseline associates the security requirement parameters with the multiple threat modeling data in the form of parameterized fields. Therefore, threat modeling can be quickly performed based on the multiple threat modeling data corresponding to the security baseline, eliminating the need for developers to analyze threats to the software product to be evaluated based on previous experience, reducing the difficulty and cost of threat modeling for developers and improving the efficiency of threat modeling. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:
[0017] Figure 1 A flowchart of a threat modeling method provided in an embodiment of the present invention;
[0018] Figure 2 A diagram of the system architecture for threat modeling provided in an embodiment of the present invention;
[0019] Figure 3 A flowchart of another threat modeling method provided in an embodiment of the present invention;
[0020] Figure 4 A flowchart of another threat modeling method provided in an embodiment of the present invention;
[0021] Figure 5 A structural diagram of a threat modeling device provided in an embodiment of the present invention;
[0022] Figure 6 This is a structural diagram of another threat modeling device provided in an embodiment of the present invention;
[0023] Figure 7 This is a structural diagram of another threat modeling device provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0024] To make the purpose, technical solutions and advantages of the embodiments of the present invention more clear, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. Here, the exemplary embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.
[0025] In order to more clearly illustrate the solution of the present invention, the existing threat modeling method is first briefly described below.
[0026] First of all, the reason for threat modeling of software products is to stand in the attacker's perspective, identify threats, and discover as many security risks as possible in the product architecture and functional design; and to ensure the security of the product by formulating measures to reduce threats and avoid risks.
[0027] Therefore, threat modeling should be integrated into an enterprise's Software Development Security Lifecycle (SDL). Threat modeling should be conducted during the design phase of new products or features to identify risks and develop mitigation measures. Mitigation measures are part of security requirements and must be tracked within product requirements to ensure product security. Threat modeling can also be conducted during system operation. The risks discovered can support enterprise penetration testing and uncover as many vulnerabilities as possible.
[0028] However, most companies and organizations currently conduct threat modeling offline, relying primarily on developers' security experience. This leads to the following issues:
[0029] (1) Threat modeling is difficult:
[0030] Developers generally lack sufficient understanding of threat modeling. The security knowledge used involves multiple different fields, and developer experience is difficult to share.
[0031] (2) High complexity of threat modeling:
[0032] The threat content is extensive, the process is long, and it takes a long time to complete threat modeling, resulting in extremely high costs and extremely low efficiency for developers to perform threat modeling.
[0033] (3) Workflow disconnection:
[0034] The output results of conventional threat modeling activities are not integrated into the existing R&D process, resulting in a disconnect in the process.
[0035] (4) Lack of an integrated work platform:
[0036] Simple modeling activities are based on questionnaires or table record analysis, and threat modeling data lacks actual updating, accumulation and further analysis.
[0037] To address the above issues, an embodiment of the present invention provides a threat modeling solution. Based on the construction of an integrated platform, it can effectively accumulate historical threat modeling experience and data, facilitating long-term analysis and retrospective analysis. Based on the construction of a security knowledge base and security baseline, it can quickly and efficiently associate threat modeling data such as business scenarios, threat types, and threat mitigation or elimination measures corresponding to software products, thereby reducing the difficulty of threat modeling, improving modeling efficiency, and lowering modeling costs. At the same time, through the development of API interfaces, it supports the integration of threat modeling data into various development processes, achieving process linkage.
[0038] like Figure 1 FIG. 1 is a flowchart of a threat modeling method provided by an embodiment of the present invention. The method may include the following steps:
[0039] Step 101: Receive a threat modeling request from a user for a software product to be evaluated; the threat modeling request includes current security requirement parameters of the software product to be evaluated;
[0040] Step 102: Determine a current security baseline corresponding to the current security requirement parameters based on the current security requirement parameters and a pre-built security knowledge base; the security knowledge base includes multiple security baselines, each of which includes an association between the security requirement parameters and multiple threat modeling data items, with each item in the association being in the form of a parameterized field.
[0041] Step 103: Perform threat modeling based on multiple threat modeling data corresponding to the current security baseline to obtain a threat modeling result.
[0042] In an embodiment of the present invention, a user's threat modeling request for a software product to be evaluated is received; the threat modeling request includes current security requirement parameters of the software product to be evaluated; a current security baseline corresponding to the current security requirement parameters is determined based on the current security requirement parameters and a pre-built security knowledge base; the security knowledge base includes: multiple security baselines, each security baseline includes: an association relationship between the security requirement parameters and multiple threat modeling data, each item in the relationship exists in the form of a parameterized field; threat modeling is performed based on the multiple threat modeling data corresponding to the current security baseline to obtain a threat modeling result. Compared with the technical solutions in the prior art that rely on the security experience and technical level of developers to perform threat modeling, the pre-built security knowledge base can quickly determine the security baseline corresponding to the current security requirement parameters of the software product to be evaluated. The security baseline associates the security requirement parameters with the multiple threat modeling data in the form of parameterized fields. Therefore, threat modeling can be quickly performed based on the multiple threat modeling data corresponding to the security baseline, eliminating the need for developers to analyze threats to the software product to be evaluated based on previous experience, reducing the difficulty and cost of threat modeling for developers and improving the efficiency of threat modeling.
[0043] Figure 2 The following is a diagram of the threat modeling system architecture provided by the embodiment of the present invention. Figure 2 The threat modeling method provided by an embodiment of the present invention is described.
[0044] In the above step 101, the user can Figure 2 The front-end work panel of the system shown initiates a threat modeling request for the software product to be evaluated. The threat modeling request may include current security requirement parameters of the software product to be evaluated.
[0045] The above-mentioned current security requirement parameters may be requirement parameters set by the user for the software product to be evaluated.
[0046] In the above step 102, a current security baseline corresponding to the current security requirement parameters can be matched from a pre-built security knowledge base according to the current security requirement parameters.
[0047] The security knowledge base may include multiple security baselines. Each security baseline may include a relationship between security requirement parameters and multiple threat modeling data items. Specifically, the multiple threat modeling data items may include business scenarios, threats, threat types, and threat mitigation or elimination measures. Each security baseline may include a relationship between security requirement parameters and business scenarios, threats, threat types, and threat mitigation or elimination measures, with each item in the relationship being represented by a parameterized field.
[0048] During specific implementation, the security knowledge base can also include a pre-built threat reduction library. This library integrates existing public security services and public security components, and stores various threats and corresponding threat reduction or elimination measures in the library. In specific applications, it can be classified according to different business scenarios and provided to developers. Specifically, threat types can be divided into six categories: Spooling, Tampering, Repudiation, Information Disclosure, Dos (Denial of Service), and Elevation of Privilege.
[0049] In other words, each of the aforementioned security baselines can be constructed from parameterized fields representing security requirement parameters, business scenarios, threats, threat types, and threat mitigation or elimination measures. Each parameterized field in a security baseline is associated with corresponding content. In practice, the corresponding security baseline can be identified from multiple pre-built security baselines using only the security requirement parameters. The corresponding business scenario, threat, threat type, and threat mitigation or elimination measures corresponding to the parameterized fields of the current security baseline can then be retrieved.
[0050] Furthermore, in this embodiment of the present invention, each item in the security baseline is associated with a parameterized field. When a user enters any parameter related to threat modeling, the corresponding content can be quickly retrieved. For example, if a user enters a threat type, the corresponding security baseline can be quickly matched. Based on the content associated with the security baseline, the corresponding threat, threat mitigation or elimination measures, and so on can be determined.
[0051] In an embodiment of the present invention, a set security baseline can also be named to facilitate quick identification of the application scenario of the security baseline. For example, the security baseline name can be "Alert keyboard cache when entering sensitive data." The content associated with the security baseline may include: content description (i.e., security requirement parameters), data privacy (i.e., threat type), risk description (i.e., corresponding threat), security design (i.e., threat mitigation or elimination measures), test cases (i.e., security test cases), etc.
[0052] In the above step 103, threat modeling may be performed based on multiple threat modeling data corresponding to the current security baseline to obtain a threat modeling result.
[0053] During specific implementation, a data model can be constructed by obtaining threat modeling data such as security requirement parameters, business scenarios, threats, threat types, and threat reduction or elimination measures corresponding to the current security baseline.
[0054] In the embodiment of the present invention, Figure 2 As shown, after obtaining the threat modeling results, the software product can be developed, tested, and released based on the threat modeling results.
[0055] In the embodiment of the present invention, each security baseline may further include: a security test case corresponding to each threat reduction or elimination measure;
[0056] like Figure 3 As shown, the threat modeling method may further include: Step 301: verifying the threat modeling result according to the security test case corresponding to the current security baseline.
[0057] In specific implementations, the security knowledge base also includes a pre-built security test library, which can be a collection of security test cases accumulated and developed during security testing during the R&D process. Each security baseline can also include parameterized fields for security test cases corresponding to threat mitigation or elimination measures. Threat modeling results can be verified using the security test cases corresponding to each parameterized field of the security baseline.
[0058] In this way, the embodiment of the present invention, by constructing a security knowledge base and utilizing the security baseline corresponding to the security requirement parameters, can accurately and efficiently obtain the business scenarios, threats, threat types, threat reduction or elimination measures corresponding to the threats, security test cases corresponding to the threat reduction or elimination measures, etc. of the software product to be evaluated, and then can perform efficient threat modeling based on the obtained data, without the need for developers to perform threat modeling based on limited security knowledge, thereby greatly reducing the difficulty of threat modeling and improving the efficiency of threat modeling.
[0059] In the embodiment of the present invention, the security baseline in the security knowledge base may also be updated based on newly added or changed security requirement parameters, business scenarios, threats, threat types, and threat mitigation or elimination measures.
[0060] During specific implementation, the security baseline in the security knowledge base can be updated in real time when any of the security requirement parameters, business scenarios, threats, threat types, and threat reduction or elimination measures are changed or added.
[0061] In an embodiment of the present invention, the security knowledge base may further include: an architecture analysis tool, a security requirements analysis tool, and a security design tool;
[0062] In an embodiment of the present invention, the threat modeling method may further include: updating a security knowledge base using an architecture analysis tool, a security requirement analysis tool, and a security design tool.
[0063] During specific implementation, the architecture of the software product to be evaluated can be analyzed through architecture analysis tools; the threats and threat types of the software product to be evaluated can be analyzed through security requirements analysis tools; and threat reduction or elimination measures can be designed through security design tools to update the security knowledge base.
[0064] In this way, by updating the security baseline, threat reduction library, security testing library, etc. in the security knowledge base, it is possible to effectively accumulate historical threat modeling experience and data, which is conducive to long-term analysis and retrospection.
[0065] In the embodiment of the present invention, Figure 4 As shown, the method may further include: Step 401: providing threat modeling results to the outside in the form of an API interface.
[0066] In the specific implementation, all the contents of the security knowledge base and the threat modeling results are provided through the API interface (such as Figure 2 It is provided to the outside in the form of a service scheduling layer, so as to be integrated into various existing R&D process systems and mechanisms to achieve seamless connection.
[0067] In an embodiment of the present invention, the method may further include:
[0068] Extracting elements of an entity relationship diagram, a data flow diagram, and a structure diagram from the threat modeling results;
[0069] The elements of entity relationship diagram, data flow diagram and structure diagram are used to form diagrams and / or documents for presentation.
[0070] During specific implementation, based on the threat modeling results, the elements of the entity relationship diagram, data flow diagram, and structure diagram in the threat modeling results are extracted and output to the front-end work panel of the corresponding threat modeling system to realize the display of results including the threat modeling results.
[0071] Specifically, an entity relationship diagram can be a relationship diagram between users, software systems or devices outside the control scope of the system; a data flow diagram can be the interaction between entities and processes, processes and processes, or processes and data storage, used to represent the flow of data; a structure diagram can be a system architecture diagram of a software product.
[0072] In an embodiment of the present invention, it may also include: recording one or any combination of the user's threat modeling login or logout time, access data, access duration, and security baseline modification operation data.
[0073] During specific implementation, security backtracking and statistical analysis are achieved by recording the user's complete use process of the threat modeling system, including login time, logout time, access data, access residence time, threat modeling content, modification of security baseline and other operational data.
[0074] The present invention also provides a threat modeling device, as described in the following embodiments. Since the principle of the device to solve the problem is similar to the threat modeling method, the implementation of the device can refer to the implementation of the threat modeling method, and the repeated parts will not be repeated.
[0075] like Figure 5 FIG. 1 is a structural diagram of a threat modeling device provided by an embodiment of the present invention, and the device may include:
[0076] Receiving module 501, configured to receive a threat modeling request from a user for a software product to be evaluated; the threat modeling request includes current security requirement parameters of the software product to be evaluated;
[0077] A security baseline determination module 502 is configured to determine a current security baseline corresponding to the current security requirement parameters based on the current security requirement parameters and a pre-built security knowledge base; the security knowledge base includes multiple security baselines, each of which includes an association between the security requirement parameters and multiple threat modeling data items, with each item in the association being in the form of a parameterized field.
[0078] The threat modeling module 503 is used to perform threat modeling based on the security requirement parameters, business scenarios, threats, threat types and threat reduction or elimination measures of the current security baseline to obtain threat modeling results.
[0079] In an embodiment of the present invention, the plurality of threat modeling data may include: business scenarios, threats, threat types, and threat mitigation or elimination measures.
[0080] In the embodiment of the present invention, each security baseline may further include: a security test case corresponding to each threat reduction or elimination measure;
[0081] like Figure 6 As shown, the threat modeling apparatus further includes: a verification module 601, configured to verify the threat modeling result according to a security test case corresponding to the current security baseline.
[0082] In an embodiment of the present invention, it also includes: an update module for updating the security baseline in the security knowledge base according to newly added or changed security requirement parameters, business scenarios, threats, threat types and threat reduction or elimination measures.
[0083] like Figure 7 As shown, in the embodiment of the present invention, it also includes: an API calling module 701, which is used to provide threat modeling results to the outside in the form of an API interface.
[0084] In an embodiment of the present invention, the security knowledge base further includes: an architecture analysis tool, a security requirements analysis tool, and a security design tool;
[0085] The threat modeling device also includes: a security tool module, which is used to update the security knowledge base using an architecture analysis tool, a security requirement analysis tool, and a security design tool.
[0086] In an embodiment of the present invention, the present invention further includes a display module for:
[0087] Extracting elements of an entity relationship diagram, a data flow diagram, and a structure diagram from the threat modeling results;
[0088] The elements of entity relationship diagram, data flow diagram and structure diagram are used to form diagrams and / or documents for presentation.
[0089] In an embodiment of the present invention, it also includes: a recording module for recording one or any combination of the user's threat modeling login or logout time, access data, access duration and security baseline modification operation data.
[0090] An embodiment of the present invention further provides a computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned threat modeling method when executing the computer program.
[0091] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which implements the above-mentioned threat modeling method when executed by a processor.
[0092] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the above-mentioned threat modeling method is implemented.
[0093] In an embodiment of the present invention, a user's threat modeling request for a software product to be evaluated is received; the threat modeling request includes current security requirement parameters of the software product to be evaluated; a current security baseline corresponding to the current security requirement parameters is determined based on the current security requirement parameters and a pre-built security knowledge base; the security knowledge base includes: multiple security baselines, each security baseline includes: an association relationship between the security requirement parameters and multiple threat modeling data, each content in the relationship exists in the form of a parameterized field; threat modeling is performed to obtain a threat modeling result. Compared with the technical solution in the prior art that relies on the security experience and technical level of the developer to perform threat modeling, the pre-built security knowledge base can quickly determine the security baseline corresponding to the current security requirement parameters of the software product to be evaluated, and the security baseline associates the security requirement parameters with the multiple threat modeling data in the form of parameterized fields. Therefore, threat modeling can be quickly performed based on the multiple threat modeling data corresponding to the security baseline, without requiring the developer to analyze the threats of the software product to be evaluated based on previous experience, thereby reducing the difficulty and cost of threat modeling for the developer and improving the efficiency of threat modeling.
[0094] In an embodiment of the present invention, by updating the security baseline, threat reduction library, security testing library, etc. in the security knowledge base, and by recording the user's complete use process of the threat modeling system, it is possible to effectively accumulate historical threat modeling experience and data, which is conducive to long-term analysis and backtracking.
[0095] In the embodiment of the present invention, all the contents of the security knowledge base and the threat modeling results are provided to the outside in the form of an API interface, so as to be integrated into various existing R&D process systems and mechanisms to achieve seamless connection.
[0096] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0097] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0098] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.
[0099] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0100] The specific embodiments described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.
Claims
1. A threat modeling method, characterized in that: include: Receive threat modeling requests from users for software products to be evaluated; The threat modeling request includes current security requirement parameters of the software product to be evaluated; Determine the current security baseline corresponding to the current security requirement parameters based on the current security requirement parameters and the pre-built security knowledge base; The security knowledge base includes: multiple security baselines, each security baseline includes: an association relationship between security requirement parameters and multiple threat modeling data, and a security test case corresponding to each threat mitigation or elimination measure, each item in the relationship exists in the form of a parameterized field; the multiple threat modeling data includes: business scenarios, threats, threat types, and threat mitigation or elimination measures; Perform threat modeling based on multiple threat modeling data corresponding to the current security baseline to obtain threat modeling results; Verify the threat modeling results based on the security test cases corresponding to the current security baseline; The threat modeling results are made available to the outside world through API interfaces, so that the threat modeling data can be integrated into various development processes to achieve process linkage.
2. The threat modeling method according to claim 1, wherein: Also includes: Update the security baseline in the security knowledge base based on any new or changed threat modeling data.
3. The threat modeling method according to claim 1, wherein: The security knowledge base also includes: architecture analysis tools, security requirements analysis tools and security design tools; The threat modeling method further includes: updating a security knowledge base using an architecture analysis tool, a security requirement analysis tool, and a security design tool.
4. The threat modeling method according to claim 1, wherein: Also includes: Extracting elements of an entity relationship diagram, a data flow diagram, and a structure diagram from the threat modeling results; The elements of entity relationship diagram, data flow diagram and structure diagram are used to form diagrams and / or documents for presentation.
5. The threat modeling method according to claim 1, wherein: Also includes: Record one or any combination of the user's threat modeling login or logout time, access data, access duration, and security baseline modification operation data.
6. A threat modeling device, characterized in that include: A receiving module, configured to receive a user's request for threat modeling of a software product to be evaluated; The threat modeling request includes current security requirement parameters of the software product to be evaluated; A security baseline determination module is used to determine the current security baseline corresponding to the current security requirement parameters based on the current security requirement parameters and a pre-built security knowledge base; The security knowledge base includes: multiple security baselines, each security baseline includes: an association relationship between security requirement parameters and multiple threat modeling data, and a security test case corresponding to each threat mitigation or elimination measure, each item in the relationship exists in the form of a parameterized field; the multiple threat modeling data includes: business scenarios, threats, threat types, and threat mitigation or elimination measures; A threat modeling module is used to perform threat modeling based on multiple threat modeling data corresponding to the current security baseline and obtain threat modeling results; A verification module, configured to verify the threat modeling results based on security test cases corresponding to the current security baseline; The API call module is used to provide threat modeling results to the outside world through the API interface, so as to integrate the threat modeling data into various development processes as a whole and realize process linkage.
7. The threat modeling apparatus according to claim 6, wherein: Also includes: The update module is used to update the security baseline in the security knowledge base according to any new or changed threat modeling data.
8. The threat modeling apparatus according to claim 6, wherein: The security knowledge base also includes: architecture analysis tools, security requirements analysis tools and security design tools; The threat modeling device also includes: a security tool module, which is used to update the security knowledge base using an architecture analysis tool, a security requirement analysis tool, and a security design tool.
9. The threat modeling apparatus according to claim 6, wherein: Also includes: Display module for: Extracting elements of an entity relationship diagram, a data flow diagram, and a structure diagram from the threat modeling results; The elements of entity relationship diagram, data flow diagram and structure diagram are used to form diagrams and / or documents for presentation.
10. The threat modeling apparatus according to claim 6, wherein: Also includes: The recording module is used to record one or any combination of the user's threat modeling login or logout time, access data, access duration, and security baseline modification operation data.
11. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 5 is implemented.
12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.
13. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.
Citation Information
Patent Citations
Threat modeling-oriented information processing method and system, and electronic equipment
CN111914408A
Enterprise threat modeling
US20070294766A1