Software security detection method and security development process management system

Abstract

The invention discloses a software security detection method and a security development process management system. The method relates to the field of supply chain information security or other related fields, and comprises the following steps: under the condition of receiving software initial data of target software, controlling a security design module to draw a software security architecture diagram according to the software initial data, and determining M security attribute values based on the software security architecture diagram; controlling a security modeling module to obtain N security requirements from a security database according to each security attribute value to obtain Y security requirements; and controlling the demand detection module to detect the Y security demands to obtain a detection result of the target software, and under the condition that the detection result represents that the detection is not passed, re-drawing the software security architecture diagram until the detection result associated with the updated software security architecture diagram represents that the detection is passed. Through the software security detection method and device, the problems of low detection efficiency and low detection accuracy during software security detection in related technologies are solved.

Description

Technical Field

[0001] The present application relates to the field of supply chain information security or other related fields, and specifically, to a software security detection method and a security development process management system. Background Art

[0002] With the rapid development of information technology, software systems are playing an increasingly important role in various fields. However, software security issues are becoming increasingly prominent and have become a key factor restricting software development. Software security requirements are the key to ensuring the security of software systems, but existing security requirements design and management technologies have many deficiencies and are in urgent need of improvement and optimization.

[0003] At present, security requirements design mainly relies on existing knowledge and manual threat modeling. Discussions and analyses are conducted through on-site Q&A, brainstorming, and guided groups between the software team and the security team. However, this method relies solely on manual implementation, which has high maintenance costs, complex execution, and high learning costs. At the same time, due to the continuous updating of security requirements, it is easy to cause deviations in understanding and execution. In addition, the security requirements verification results are usually analyzed through correlation analysis through security test reports. However, the correlation between the report and the security requirements is relatively vague and difficult to confirm. This makes it difficult to ensure the effectiveness and integrity of security requirements by lacking technical verification methods for the implementation of security requirements.

[0004] In order to solve the problem of unmanageable security requirements, the current relevant technology is to establish a secure development process. The security development process management technology usually adopts the security development lifecycle management framework, including requirements analysis, security design, security coding, security testing, deployment and other stages. However, the existing security development process management technology still faces some challenges, such as the lack of automation and intelligent support, and the inability of security testing to verify security requirements item by item. In addition, existing threat modeling tools often require manual operation and intervention, and lack automation and intelligent support. For example, the method of manually filling out forms or questionnaires requires developers to spend a lot of time and energy on manual analysis and modeling, and is prone to errors or omissions of certain security risks.

[0005] In addition, the existing security requirements design and management technologies have many deficiencies. Existing security testing technologies include interactive application security testing, static application security testing, software composition analysis, etc., which can all perform security vulnerability testing. However, these technologies cannot establish a mapping relationship between security test cases and security requirements, and cannot verify security requirements item by item. Security requirements verification requires manual verification and feedback to the system, which makes security requirements verification more difficult.

[0006] With regard to the problems of low detection efficiency and low detection accuracy when performing security testing on software in related technologies, no effective solution has been proposed so far. Summary of the invention

[0007] The main purpose of this application is to provide a software security detection method and a security development process management system to solve the problems of low detection efficiency and low detection accuracy when performing security detection on software in related technologies.

[0008] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a software security detection method is provided. The method includes: when receiving the software initial data of the target software, the control security design module draws the software security architecture diagram according to the software initial data, and determines M security attribute values ​​based on the software security architecture diagram, wherein the software security architecture diagram is used to characterize the mutual relationship between the components in the target software, and each security attribute value characterizes the attribute correspondence of each node in the software security architecture diagram, and M is a positive integer; the control security modeling module obtains N security requirements from the security database according to each security attribute value to obtain Y security requirements, wherein Y=M*N, Y, N are positive integers; the control requirement detection module detects the Y security requirements to obtain the detection result of the target software, wherein, when the detection result indicates that the detection fails, the software security architecture diagram is redrawn until the detection result associated with the updated software security architecture diagram indicates that the detection passes.

[0009] Furthermore, the requirement detection module includes a requirement management module and a requirement verification module. The requirement management module includes a requirement review module. The control requirement detection module detects Y security requirements, and the detection results of the target software include: the control requirement review module performs a rationality review on each security requirement according to multiple review tools, obtains Y review results, and sends the Y review results to the requirement verification module; the control requirement verification module obtains the detection rules, and verifies each security requirement according to the detection rules to obtain Y verification results; when the control requirement verification module receives Y review results, the detection result is determined according to the Y verification results and the Y review results.

[0010] Furthermore, the requirement detection module includes a quality scoring module, which controls the requirement detection module to detect Y security requirements, and obtains the detection results of the target software including: controlling the quality scoring module to identify the total number of review results representing the number of passed reviews to obtain a first total number, and identifying the total number of verification results representing the number of passed verifications to obtain a second total number; obtaining a first quantity threshold, a second quantity threshold, and a third quantity threshold, controlling the quality scoring module to compare the first quantity threshold with the number of Y security requirements to obtain a first comparison result, and comparing the second quantity threshold with the first total number to obtain a second comparison result; controlling the quality scoring module to compare the third quantity threshold with the second total number to obtain a third comparison result, and determining the detection result based on the first comparison result, the second comparison result, and the third comparison result.

[0011] Further, determining the test result by the first comparison result, the second comparison result and the third comparison result includes: generating a test result of passing the test when the first comparison result represents that the first quantity threshold is less than the number of Y security requirements, the second comparison result represents that the second quantity threshold is less than the first total, and the third comparison result represents that the third quantity threshold is less than the second total; generating a test result of failing the test when the first quantity threshold is greater than or equal to the number of Y security requirements, or the second quantity threshold is greater than or equal to the first total, or the third quantity threshold is greater than or equal to the second total.

[0012] Furthermore, the security modeling module includes a security attribute mapping module and a security database management module. The security database management module is associated with a security database. The security modeling module is controlled to obtain N security requirements from the security database according to each security attribute value. Obtaining Y security requirements includes: controlling the security attribute mapping module to communicate with the security database management module and obtaining the security database from the security database management module; screening N security requirements associated with each security attribute value from the security database to obtain Y security requirements.

[0013] Furthermore, the security modeling module also includes a model building module, and the method also includes: controlling the model building module to establish a security threat model according to Y security requirements, and displaying the security threat model, wherein the security threat model is used to display the applicable scope of the association of the Y security requirements.

[0014] Furthermore, the requirement management module also includes a requirement synchronization module and a requirement tracking module. After the requirement review module is controlled to conduct a rationality review on each security requirement according to multiple review tools and obtains Y review results, the method also includes: controlling the requirement synchronization module to identify the Y review results and synchronizing the review results representing the passed security requirements to the management system; and controlling the requirement tracking module to display the review progress of each security requirement.

[0015] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a security development process management system is provided. The system includes: a security design module, which is used to draw a software security architecture diagram according to the software initial data of the target software when the software initial data is received, and determine M security attribute values ​​based on the software security architecture diagram, and send the M security attribute values ​​to the security modeling module, wherein the software security architecture diagram is used to characterize the mutual relationship between components in the target software, and each security attribute value characterizes the attribute correspondence of each node in the software security architecture diagram, and M is a positive integer; a security modeling module, which is used to obtain N security requirements from the security database according to each security attribute value when the M security attribute values ​​are received, obtain Y security requirements, and send the Y security requirements to the requirement detection module, wherein Y=M*N, Y, N are positive integers; a requirement detection module, which is used to detect each group of security requirements when the Y security requirements are received, and obtain the detection result of the target software.

[0016] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a software security detection device is provided. The device includes: a first control unit, which is used to control the security design module to draw a software security architecture diagram according to the software initial data of the target software when receiving the software initial data, and determine M security attribute values ​​based on the software security architecture diagram, wherein the software security architecture diagram is used to characterize the mutual relationship between components in the target software, and each security attribute value characterizes the attribute correspondence relationship of each node in the software security architecture diagram, and M is a positive integer; a second control unit, which is used to control the security modeling module to obtain N security requirements from the security database according to each security attribute value, and obtain Y security requirements, wherein Y=M*N, Y, N are positive integers; a third control unit, which is used to control the requirement detection module to detect Y security requirements and obtain the detection result of the target software, wherein, when the detection result indicates that the detection fails, the software security architecture diagram is redrawn until the detection result associated with the updated software security architecture diagram indicates that the detection passes.

[0017] According to another aspect of an embodiment of the present invention, a computer storage medium is provided. The computer storage medium is used to store a program. When the program is running, the device where the computer storage medium is located is controlled to execute a software security detection method.

[0018] According to another aspect of an embodiment of the present invention, an electronic device is provided, comprising one or more processors and a memory; the memory stores computer-readable instructions, and the processor is used to execute the computer-readable instructions, wherein a software security detection method is executed when the computer-readable instructions are executed.

[0019] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, a software security detection method is executed.

[0020] Through this application, the following steps are adopted: when the initial software data of the target software is received, the control security design module draws a software security architecture diagram according to the initial software data, and determines M security attribute values ​​based on the software security architecture diagram, wherein the software security architecture diagram is used to characterize the relationship between components in the target software, and each security attribute value characterizes the attribute correspondence of each node in the software security architecture diagram, and M is a positive integer; the control security modeling module obtains N security requirements from the security database according to each security attribute value to obtain Y security requirements, wherein Y=M*N, Y and N are positive integers; the control requirement detection module detects the Y security requirements and obtains the target software. The test results of the target software are obtained, wherein, when the test results indicate that the test has not passed, the software security architecture diagram is redrawn until the test results associated with the updated software security architecture diagram indicate that the test has passed, thereby solving the problems of low detection efficiency and low detection accuracy in software security testing in related technologies. The security design module is controlled to draw the software security architecture diagram according to the initial software data, and the security attribute values ​​are determined based on the software security architecture diagram. The security modeling module is controlled to obtain the corresponding security requirements from the security database according to each security attribute value, and the test results are obtained after the security requirements are tested, thereby achieving the effect of improving the efficiency and accuracy of software security testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0022] Figure 1 is a schematic diagram of a secure development process management system provided according to an embodiment of the present application;

[0023] Figure 2 is a flowchart of a software security detection method provided according to an embodiment of the present application;

[0024] Figure 3 It is a workflow diagram of a demand management module provided according to an embodiment of the present application;

[0025] Figure 4 is a workflow diagram of a quality scoring module provided according to an embodiment of the present application;

[0026] Figure 5 is a workflow diagram of a security modeling module provided according to an embodiment of the present application;

[0027] Figure 6 is a flowchart of an optional secure development process management system provided according to an embodiment of the present application;

[0028] Figure 7 is a schematic diagram of a software security detection device provided according to an embodiment of the present application;

[0029] Figure 8 is a schematic diagram of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0031] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. For example, an interface is set between this system and the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0034] It should be noted that the collected information used in this application is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse to use it.

[0035] The present invention is described below in conjunction with preferred implementation steps. Figure 1 is a schematic diagram of a secure development process management system provided according to an embodiment of the present application, such as Figure 1 As shown, the system includes:

[0036] The security design module 101 is used to draw a software security architecture diagram based on the software initial data when the software initial data of the target software is received, and determine M security attribute values ​​based on the software security architecture diagram, and send the M security attribute values ​​to the security modeling module 102, wherein the software security architecture diagram is used to characterize the relationship between components in the target software, each security attribute value represents the attribute correspondence of each node in the software security architecture diagram, and M is a positive integer.

[0037] Specifically, the security design module 101 is mainly used to design the security attributes of the target software. The module includes a security architecture design and a security attribute association module. The security architecture design module is used to identify the main components of the software and the interaction relationships between them based on the software initial data after receiving the software initial data of the target software, and draw a software security architecture diagram based on the identified interaction relationships. The security attribute association module is used to select security attribute values ​​based on the drawn software security architecture diagram, and then send the selected security attribute values ​​to the security modeling module 102, where the security attribute values ​​can be encryption strength, security of the authentication mechanism, data isolation, etc.

[0038] The security modeling module 102 is used to obtain N security requirements from the security database according to each security attribute value when M security attribute values ​​are received, obtain Y security requirements, and send the Y security requirements to the requirement detection module 103, where Y=M*N, Y and N are positive integers.

[0039] Specifically, the security modeling module 102 includes a security attribute mapping module, a security knowledge base management module and a model building module, wherein the security attribute mapping module is used to establish an association between security attributes and security requirements, that is, when receiving a security attribute value, the security requirement is determined from the security database based on the security attribute value, and the security requirement is sent to the requirement detection module 103; the security knowledge base management module is used to manage knowledge base data related to security requirement design such as security requirements, security threats, security functions, security components, security test cases, application scenarios, laws and regulations, and to add, delete, modify and query data, that is, to store and manage the above data; the model building module is used to visualize the security requirements and export reports.

[0040] The requirement detection module 103 is used to detect each group of security requirements when Y security requirements are received, and obtain the detection result of the target software.

[0041] Specifically, the demand detection module 103 includes a demand management module and a demand verification module. These two modules can be used to detect security requirements. The demand management module can generate review results, and the demand verification module can generate corresponding verification results. Finally, the target detection results are determined based on the review results and verification results.

[0042] The security development process management system provided in the embodiment of the present application is used, through the security design module 101, to draw a software security architecture diagram according to the software initial data of the target software, and determine M security attribute values ​​based on the software security architecture diagram, and send the M security attribute values ​​to the security modeling module 102, wherein the software security architecture diagram is used to characterize the relationship between components in the target software, each security attribute value represents the attribute correspondence of each node in the software security architecture diagram, and M is a positive integer. The security modeling module 102 is used to obtain N security requirements from the security database according to each security attribute value when receiving M security attribute values, obtain Y security requirements, and send the Y security requirements to the security modeling module 102. The security requirements are sent to the requirement detection module 103, where Y=M*N, Y and N are positive integers; the requirement detection module 103 is used to detect each group of security requirements when Y security requirements are received, and obtain the detection results of the target software, which solves the problems of low detection efficiency and low detection accuracy when performing security detection on software in related technologies, and controls the security design module to draw a software security architecture diagram according to the initial software data, and determines the security attribute value based on the software security architecture diagram, and controls the security modeling module to obtain the corresponding security requirements from the security database according to each security attribute value, and obtains the detection results after testing the security requirements, thereby achieving the effect of improving the efficiency and accuracy of software security detection.

[0043] The embodiment of the present application also provides a software security detection method. The software security detection method of the embodiment of the present application can be applied to the security development process management system provided by the embodiment of the present application. The software security detection method provided by the embodiment of the present application is introduced below.

[0044] Figure 2 is a flowchart of a software security detection method provided in an embodiment of the present application. Figure 2 As shown, the method comprises the following steps:

[0045] Step S201, when receiving the software initial data of the target software, the control security design module draws a software security architecture diagram according to the software initial data, and determines M security attribute values ​​based on the software security architecture diagram, wherein the software security architecture diagram is used to characterize the relationship between components in the target software, each security attribute value represents the attribute correspondence of each node in the software security architecture diagram, and M is a positive integer.

[0046] Specifically, in order to perform security testing on the software, the security requirements of the target software can be verified. At this time, the security design module can be controlled to draw a software security architecture diagram by analyzing and understanding the initial data after receiving the software. The initial data of the software may include software interface data, access control data, data protection, vulnerability management data, security policy data, etc. The security attribute values ​​may include security-related parameters such as access rights to the system or resources, encryption settings, and authentication information. The software security architecture diagram is a graphical representation method that can clearly show the relationships and interactions between the various components in the target software. Through the software security architecture diagram, designers can better understand the structure and functions of the software, thereby providing an intuitive reference for determining security attributes.

[0047] Furthermore, when determining the security attribute value, the security design module can be controlled to identify the software security architecture diagram, analyze and evaluate the attributes of each node, and then determine the appropriate security attribute value, thereby effectively improving the security of the software and reducing potential security risks.

[0048] Step S202 , the security modeling module is controlled to obtain N security requirements from the security database according to each security attribute value, and obtain Y security requirements, where Y=M*N, and Y and N are positive integers.

[0049] Specifically, after determining the security attribute value according to the software security architecture diagram, the security modeling module can be used to establish the association relationship between the security attribute and the security requirement. That is, when the security attribute value is received, the corresponding security requirement is determined from the security database associated with the data storage module based on the security attribute value.

[0050] Step S203, control the requirement detection module to detect Y security requirements and obtain the detection result of the target software. When the detection result indicates that the detection has not passed, redraw the software security architecture diagram until the detection result associated with the updated software security architecture diagram indicates that the detection has passed.

[0051] Specifically, after obtaining multiple security requirements, each security requirement is tested to ensure that the software system meets the expected safety performance. If a security requirement is found to have failed the test, the control requirement detection module can redraw the software security architecture diagram. At this time, the software security architecture diagram is adjusted and optimized accordingly, and the updated software security architecture diagram is re-tested for security. When the test result associated with the architecture diagram indicates that the test has passed, it indicates that the target software has passed the verification, providing sufficient protection for the security of the software.

[0052] The software security detection method provided in the embodiment of the present application is that, when receiving the software initial data of the target software, the control security design module draws a software security architecture diagram according to the software initial data, and determines M security attribute values ​​based on the software security architecture diagram, wherein the software security architecture diagram is used to characterize the mutual relationship between components in the target software, each security attribute value characterizes the attribute correspondence of each node in the software security architecture diagram, and M is a positive integer; the control security modeling module obtains N security requirements from the security database according to each security attribute value to obtain Y security requirements, wherein Y=M*N, Y and N are positive integers; the control requirement detection module detects the Y security requirements, The test results of the target software are obtained, wherein, when the test results indicate that the test has failed, the software security architecture diagram is redrawn until the test results associated with the updated software security architecture diagram indicate that the test has passed, thereby solving the problems of low detection efficiency and low detection accuracy in software security testing in related technologies. The security design module is controlled to draw the software security architecture diagram according to the initial software data, and the security attribute values ​​are determined based on the software security architecture diagram. The security modeling module is controlled to obtain the corresponding security requirements from the security database according to each security attribute value, and the test results are obtained after the security requirements are tested, thereby achieving the effect of improving the efficiency and accuracy of software security testing.

[0053] The detection of security requirements can be divided into a requirement review stage and a requirement verification stage. Optionally, in the software security detection method provided in the embodiment of the present application, the requirement detection module includes a requirement management module and a requirement verification module, the requirement management module includes a requirement review module, and the control requirement detection module detects Y security requirements to obtain the detection results of the target software, including: controlling the requirement review module to perform a rationality review on each security requirement according to multiple review tools, obtain Y review results, and send the Y review results to the requirement verification module; controlling the requirement verification module to obtain detection rules, and verifying each security requirement according to the detection rules to obtain Y verification results; when the control requirement verification module receives Y review results, the detection result is determined according to the Y verification results and the Y review results.

[0054] Specifically, the requirement management module can be used to review the requirements during the requirement review phase, and the requirement verification module can be used to verify the requirements during the requirement verification phase. When reviewing security requirements, the requirement review module in the requirement management module can be used to perform operations. Figure 3 is a workflow diagram of a demand management module provided according to an embodiment of the present application, such as Figure 3 As shown, the requirement review module is used to conduct a rationality review of security requirements and record the review process and results. That is, after receiving the security requirements sent by the security modeling module, multiple review tools are used to conduct a rationality review on each security requirement, obtain the corresponding review results, and send the review results to the requirement verification module.

[0055] Furthermore, after the requirement verification module receives the review results and security requirements, it obtains the detection rules, verifies each security requirement according to the detection rules, obtains the corresponding verification results, and determines the detection results according to the verification results and the review results. This embodiment improves the detection efficiency and accuracy by using the requirement detection module to detect security requirements.

[0056] In order to check the detection progress in time, optionally, in the software security detection method provided in the embodiment of the present application, the requirement management module also includes a requirement synchronization module and a requirement tracking module. After the requirement review module is controlled to conduct a rationality review on each security requirement according to multiple review tools and obtain Y review results, the method also includes: controlling the requirement synchronization module to identify the Y review results, and synchronizing the review results representing the passed security requirements to the management system; controlling the requirement tracking module to display the review progress of each security requirement.

[0057] Specifically, Figure 3As shown, the demand management module also includes a demand synchronization module and a demand tracking module. After the demand review module generates the review results, the review results are identified, and the review results representing the security requirements that have passed the review are synchronized to the management system through the demand synchronization module. At the same time, the management system processes the synchronized results to obtain the completion status of the security requirements, and sends the completion status of the security requirements to the demand tracking module. The demand tracking module can also receive the security requirement verification results sent by the demand verification module, and then display the completion status of the security requirements and the security requirement verification results, which is convenient for staff to view.

[0058] In order to accurately determine the detection result, optionally, in the software security detection method provided in the embodiment of the present application, the requirement detection module includes a quality scoring module, and the control requirement detection module detects Y security requirements, and the detection result of the target software obtained includes: controlling the quality scoring module to identify the review result representing the total number of reviews that passed, and obtain a first total number, and identifying the verification result representing the total number of verifications that passed, and obtain a second total number; obtaining a first quantity threshold, a second quantity threshold, and a third quantity threshold, controlling the quality scoring module to compare the first quantity threshold with the number of Y security requirements to obtain a first comparison result, and comparing the second quantity threshold with the first total number to obtain a second comparison result; controlling the quality scoring module to compare the third quantity threshold with the second total number to obtain a third comparison result, and determining the detection result by the first comparison result, the second comparison result, and the third comparison result.

[0059] Specifically, the detection of software security requirements can be visualized by scoring security requirements, so the requirement detection module can also include a quality scoring module, which can first control the quality scoring module to identify the total number of results in the review results that represent the review and the total number of results in the verification results that represent the verification, thereby obtaining the first total number and the second total number. Further, after obtaining the quantity threshold of security requirements (i.e., the first quantity threshold), the quantity threshold of security requirement review results (i.e., the second quantity threshold), and the quantity threshold of security requirement verification results (i.e., the third quantity threshold), the first quantity threshold is compared with the number of security requirements, the second quantity threshold is compared with the first total number, and the third quantity threshold is compared with the second total number, thereby obtaining the first comparison result, the second comparison result, and the third comparison result, and finally determining the detection result based on the first comparison result, the second comparison result, and the third comparison result. This embodiment uses multiple quantity thresholds to determine the detection result, which can intuitively reflect the detection result, thereby facilitating the staff to judge the cause of the abnormality.

[0060] Figure 4 is a workflow diagram of a quality scoring module provided in an embodiment of the present application, such as Figure 4As shown, optionally, in the software security detection method provided in the embodiment of the present application, determining the detection result by the first comparison result, the second comparison result and the third comparison result includes: generating a detection result of passing the detection when the first comparison result represents that the first quantity threshold is less than the number of Y security requirements, the second comparison result represents that the second quantity threshold is less than the first total, and the third comparison result represents that the third quantity threshold is less than the second total; generating a detection result of failing the detection when the first quantity threshold is greater than or equal to the number of Y security requirements, or the second quantity threshold is greater than or equal to the first total, or the third quantity threshold is greater than or equal to the second total.

[0061] Specifically, the quality scoring module compares the number of security requirements, the first total number, and the second total number based on the number threshold of security requirements (i.e., the first number threshold), the number threshold of security requirement review results (i.e., the second number threshold), and the number threshold of security requirement verification results (i.e., the third number threshold), to obtain corresponding comparison results, and finally generates different results by connecting with an "AND gate", that is, when the first comparison result indicates that the first number threshold is less than the number of security requirements, the second comparison result indicates that the second number threshold is less than the first total number, and the third comparison result indicates that the third number threshold is less than the second total number, a test result of passing the test is generated; when the first number threshold is greater than or equal to the number of security requirements, or the second number threshold is greater than or equal to the first total number, or the third number threshold is greater than or equal to the second total number, a test result of failing the test is generated. This embodiment generates different test results by using an "AND gate" to reflect the development of the software from many aspects.

[0062] Figure 5 is a workflow diagram of a security modeling module provided according to an embodiment of the present application, such as Figure 5 As shown, optionally, in the software security detection method provided in the embodiment of the present application, the security modeling module includes a security attribute mapping module and a security database management module, the security database management module is associated with a security database, and the security modeling module is controlled to obtain N security requirements from the security database according to each security attribute value, and obtaining Y security requirements includes: controlling the security attribute mapping module to communicate with the security database management module, and obtaining the security database from the security database management module; screening the N security requirements associated with each security attribute value from the security database to obtain Y security requirements.

[0063] Specifically, the security modeling module and the data storage module are bidirectional output settings, including a security attribute mapping module, a security knowledge base management module, and a model building module. The data storage module can provide the security knowledge base management module with knowledge base data related to security requirements design, such as security requirements, security threats, security functions, security components, security test cases, application scenarios, laws and regulations, etc. The security knowledge base management module is associated with the security database, and can add, delete, modify, and query the corresponding knowledge base data after the data storage module provides the corresponding knowledge base data, and store the processed knowledge base data in the security database.

[0064] The security attribute mapping module is used to establish the association between security attributes and security requirements. That is, when receiving the security attribute value, it controls the communication connection between the security attribute mapping module and the security database management module, obtains the security database from the security database management module, and finally determines the security requirements from the security database based on the security attribute value, and sends the security requirements to the requirement detection module.

[0065] Optionally, in the software security detection method provided in the embodiment of the present application, the security modeling module also includes a model building module, and the method also includes: controlling the model building module to establish a security threat model according to Y security requirements, and displaying the security threat model, wherein the security threat model is used to display the scope of application associated with the Y security requirements.

[0066] Specifically, Figure 5 As shown, the model building module can extract knowledge base data such as security requirements, security threats, security functions, security components, security test cases, application scenarios, laws and regulations from the security knowledge base management module, and use security requirements to build a security threat model and visualize the model.

[0067] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0068] The present application also provides a secure development process management system. Figure 6 is a flowchart of an optional secure development process management system provided according to an embodiment of the present application, such as Figure 6 As shown, the system includes: a security design module, a security modeling module, a requirement management module, a requirement verification module, a data storage module and a quality scoring module.

[0069] Among them, the security design module can access the security knowledge base data and obtain the security attribute values ​​in the security knowledge base data. The output end is provided with a security modeling module to output the confirmed security attribute values; the input end of the security modeling module is provided with a data storage module, which can access the data storage module and obtain the security knowledge base data. The output end is provided with a data storage module and a requirement management module, which outputs project data to the data storage module and outputs confirmed security requirements to the requirement management module; the data storage module is divided into "security knowledge base data" and "project data"; the output end of the requirement management module is provided with a requirement verification module to output the completed security requirements; the output end of the requirement verification module is provided with a quality scoring module to output the security requirement verification result; the input end of the quality scoring module is provided with a data storage module to access the project data. When the quality scoring module outputs the test result that fails the test, the security requirement is returned to the requirement management module for redevelopment and verification.

[0070] The security design module includes a security architecture design and a security attribute association module. The security architecture design module is used to draw a software security architecture diagram, including an information entry module, a toolbox module, and a drawing module. The information entry module is used to record software information, including software name, version, security level, R&D department, R&D manager, security manager, etc. The toolbox module has built-in common architecture drawing graphics for architecture diagram drawing, and the drawing module is used to draw software security architecture diagrams. The security attribute association module is used to select security attribute values ​​according to the security architecture diagram and establish an association relationship identifier with the software, including a security attribute acquisition module, a security attribute selection module, and a security attribute transmission module. The security attribute acquisition module obtains a security attribute list from the security attribute knowledge base data in the data storage module. The security attribute selection provides security attribute list display and selection functions. The security attribute transmission transmits the confirmed security attributes to the security modeling module for further analysis.

[0071] The security modeling module and the data storage module are bidirectional output settings, including the security attribute mapping module, the security knowledge base management module and the model building module. The security attribute mapping module obtains the security requirement information in the security knowledge base data from the data storage module, which is used to establish the association between security attributes and security requirements, and generate security requirements based on security attributes. The security knowledge base management module is used to manage the knowledge base data related to security requirement design, such as security requirements, security threats, security functions, security components, security test cases, application scenarios, laws and regulations, and to add, delete, modify and query data. The model building module is used to establish the threat model of security requirements and perform visual display and report export, including the model building module, the model generation module and the report management module. The model building module is used to build the relationship between security requirements, security threats, security functions, security components, security test cases, application scenarios, and laws and regulations. The model generation module obtains the security knowledge base data from the data storage module based on the confirmed security requirements, builds a security threat model, describes the application scenarios of the security requirements, compliance basis, possible security threats, standard security design, available security components, and test steps used for design, and stores the constructed security threat model in the project data of the data storage module. The report management module can generate and export the result report based on the security modeling analysis results.

[0072] The data storage module is set up as a two-way output with the security modeling module and the quality scoring module. The data storage module is divided into "security knowledge base data" and "project data". "Security knowledge base data" includes security attribute library data, security requirement library data, security design library data, test case library data, compliance library data, threat library data, scenario library data, association relationship data, requirement verification rule library data, and project quality scoring model library data. "Project data" includes software name, version, security level, R&D department, R&D person in charge, security person in charge, software security requirements, security design, application scenarios, compliance basis, security threats, software security requirements verification results, project security quality scoring data, etc.

[0073] The requirement management module includes the requirement review module, the requirement synchronization module and the requirement tracking module. The requirement review module is used to review the rationality of security requirements and record the review process and results. The requirement synchronization module is used to synchronize security requirements to the management system. The requirement tracking module is used to display the progress of requirement completion and verification, including the requirement acquisition module and the requirement progress display module. The requirement acquisition module obtains the requirement progress data from the management system and obtains the requirement verification result data from the requirement verification module. The requirement progress display module visualizes the requirement implementation and verification progress in the form of a flowchart.

[0074] The requirement verification module includes a test engine module and a rule management module. The test engine module is used to detect and verify the software security requirements, including a source code analysis module, a build configuration file analysis module, a library file analysis module, a header file analysis module, a code fingerprint analysis module, a simulated build analysis module, a compiler-based analysis module, a bytecode comparison analysis module, and a data flow analysis module. The source code analysis module is used to analyze the underlying control flow and data flow of the code, perform code abstract interpretation and symbolic execution, and detect and discover code defects. The build configuration file analysis module is used to analyze the component information declared in the build configuration file identification file. The library file analysis module is used to identify the code package information directly inserted into the source code. The header file analysis module is used to identify the component information declared in the header file. The code fingerprint analysis module is used to identify the referenced open source code fragments. The simulated build analysis module is used to identify the component information pulled during the build process. The compiler-based analysis module is used to monitor the compilation process to identify the component information that the software indirectly depends on. The bytecode comparison analysis module is used to understand the program behavior and thus discover hidden security vulnerabilities. The data flow analysis module is used to confirm whether the program execution meets the vulnerability triggering conditions. The rule management module is used to manage the detection rules used by the test engine module, including detection engine integration and detection rule management. The detection engine integration is used to configure the detection engine parameters for integration into the development security pipeline, and the detection engine rule management is used to configure the detection rules of each detection engine.

[0075] The quality scoring module includes a first quantity threshold, a second quantity threshold, and a third quantity threshold. The first quantity threshold, the second quantity threshold, and the third quantity threshold are connected through an "AND gate". The output detection results are detection failure and detection pass. The output data of the security modeling module includes the number of security requirements, the number of qualified security requirements reviewed by the requirement review module, and the number of requirements verified by the requirement verification module. The threshold is the minimum value. When the number of security requirements, the pass rate of the security requirement review, and the pass rate of the security requirement verification exceed the set threshold, the output is "1", otherwise the output is "0". The output result of the first quantity threshold is A, the output result of the second quantity threshold is B, and the output result of the third quantity threshold is C. The total output result of the quality scoring module is Y, Y=A*B*C, the Y output result of "0" indicates that the detection fails, and the Y output structure of "1" indicates that the detection passes. All detection results are fed back to the requirement management module.

[0076] This embodiment controls the security design module to draw a software security architecture diagram according to the software initial data, determines the security attribute values ​​based on the software security architecture diagram, and controls the security modeling module to obtain the corresponding security requirements from the security database according to each security attribute value, and obtains the test results after testing the security requirements, thereby achieving the effect of improving the efficiency and accuracy of software security testing.

[0077] The embodiment of the present application also provides a software security detection device. It should be noted that the software security detection device of the embodiment of the present application can be used to execute the software security detection method provided by the embodiment of the present application. The software security detection device provided by the embodiment of the present application is introduced below.

[0078] Figure 7 is a schematic diagram of a software security detection device provided according to an embodiment of the present application, such as Figure 7 As shown, the device includes: a first control unit 70, a second control unit 71, and a third control unit 72.

[0079] A first control unit 70 is used to control the security design module to draw a software security architecture diagram according to the software initial data when receiving the software initial data of the target software, and determine M security attribute values ​​based on the software security architecture diagram, wherein the software security architecture diagram is used to represent the relationship between components in the target software, each security attribute value represents the attribute correspondence relationship of each node in the software security architecture diagram, and M is a positive integer;

[0080] A second control unit 71 is used to control the security modeling module to obtain N security requirements from the security database according to each security attribute value to obtain Y security requirements, where Y=M*N, Y and N are positive integers;

[0081] The third control unit 72 is used to control the requirement detection module to detect Y security requirements and obtain the detection result of the target software. When the detection result indicates that the detection fails, the software security architecture diagram is redrawn until the detection result associated with the updated software security architecture diagram indicates that the detection passes.

[0082] The software security detection device provided in the embodiment of the present application controls the security design module to draw a software security architecture diagram according to the software initial data of the target software through the first control unit 70, and determines M security attribute values ​​based on the software security architecture diagram, wherein the software security architecture diagram is used to characterize the relationship between components in the target software, and each security attribute value characterizes the attribute correspondence of each node in the software security architecture diagram, and M is a positive integer; the second control unit 71 controls the security modeling module to obtain N security requirements from the security database according to each security attribute value to obtain Y security requirements, wherein Y=M*N, Y and N are positive integers; the third control unit 72 controls the requirement detection module Y security requirements are tested to obtain the test results of the target software. When the test results indicate that the test has failed, the software security architecture diagram is redrawn until the test results associated with the updated software security architecture diagram indicate that the test has passed. This solves the problems of low detection efficiency and low detection accuracy in software security testing in related technologies. The security design module is controlled to draw the software security architecture diagram according to the initial software data, and the security attribute values ​​are determined based on the software security architecture diagram. The security modeling module is controlled to obtain the corresponding security requirements from the security database according to each security attribute value. The test results are obtained after the security requirements are tested, thereby achieving the effect of improving the efficiency and accuracy of software security testing.

[0083] Optionally, in the software security detection device provided in the embodiment of the present application, the third control unit 72 includes: a first control module, used to control the requirement review module to perform a rationality review on each security requirement according to multiple review tools, obtain Y review results, and send the Y review results to the requirement verification module; a second control module, used to control the requirement verification module to obtain detection rules, and verify each security requirement according to the detection rules to obtain Y verification results; a determination module, used to determine the detection result according to Y verification results and Y review results when the requirement verification module is controlled to receive Y review results.

[0084] Optionally, in the software security detection device provided in the embodiment of the present application, the third control unit 72 includes: a third control module, which is used to control the quality scoring module to identify the review result representing the total number of reviews that passed, and obtain a first total number, and identify the verification result representing the total number of verifications that passed, and obtain a second total number; an acquisition module, which is used to obtain a first quantity threshold, a second quantity threshold, and a third quantity threshold, and control the quality scoring module to compare the first quantity threshold with the number of Y security requirements to obtain a first comparison result, and compare the second quantity threshold with the first total number to obtain a second comparison result; a fourth control module, which is used to control the quality scoring module to compare the third quantity threshold with the second total number to obtain a third comparison result, and determine the detection result by the first comparison result, the second comparison result, and the third comparison result.

[0085] Optionally, in the software security detection device provided in the embodiment of the present application, the third control unit 72 includes: a first generation module, used to generate a detection result of passing the detection when the first comparison result indicates that the first quantity threshold is less than the number of Y security requirements, the second comparison result indicates that the second quantity threshold is less than the first total, and the third comparison result indicates that the third quantity threshold is less than the second total; and a second generation module, used to generate a detection result of failing the detection when the first quantity threshold is greater than or equal to the number of Y security requirements, or the second quantity threshold is greater than or equal to the first total, or the third quantity threshold is greater than or equal to the second total.

[0086] Optionally, in the software security detection device provided in the embodiment of the present application, the second control unit 72 includes: a fifth control module, used to control the communication connection between the security attribute mapping module and the security database management module, and obtain the security database from the security database management module; a screening module, used to screen N security requirements associated with each security attribute value from the security database to obtain Y security requirements.

[0087] Optionally, in the software security detection device provided in the embodiment of the present application, the device also includes: a sixth control module, used to control the model building module to establish a security threat model according to Y security requirements, and display the security threat model, wherein the security threat model is used to display the scope of application associated with the Y security requirements.

[0088] Optionally, in the software security detection device provided in the embodiment of the present application, the device also includes: a fourth control unit, used to control the requirement review module to perform a rationality review on each security requirement according to multiple review tools, and after obtaining Y review results, the control requirement synchronization module identifies the Y review results and synchronizes the review results representing the passed security requirements to the management system; a fifth control unit, used to control the requirement tracking module to display the review progress of each security requirement.

[0089] The above-mentioned software security detection device includes a processor and a memory. The above-mentioned first control unit 70, second control unit 71, third control unit 72, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0090] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the kernel parameters can be adjusted to solve the problems of low detection efficiency and low detection accuracy in the related technology when performing security detection on software.

[0091] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0092] An embodiment of the present invention provides a computer storage medium, which is used to store a program. When the program is running, the device where the computer storage medium is located is controlled to execute a software security detection method.

[0093] Figure 8 is a schematic diagram of an electronic device provided according to an embodiment of the present application, such as Figure 8 As shown, an embodiment of the present invention provides an electronic device, the electronic device 80 includes a processor, a memory, and a program stored in the memory and executable on the processor, the processor is used to execute computer-readable instructions, wherein a software security detection method is executed when the computer-readable instructions are executed. The device in this article can be a server, a PC, a PAD, a mobile phone, etc.

[0094] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of a software security detection method in each embodiment of the present application.

[0095] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0096] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, 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 generate 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 flowchart and / or block diagram. 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.

[0097] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate 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 A function specified in one or more boxes.

[0098] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0099] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0100] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0101] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0102] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0103] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A software security detection method, applied to a security development process management system, characterized in that: include: In the case of receiving the software initial data of the target software, the control security design module draws a software security architecture diagram according to the software initial data, and determines M security attribute values ​​based on the software security architecture diagram, wherein the software security architecture diagram is used to characterize the mutual relationship between components in the target software, each security attribute value characterizes the attribute correspondence relationship of each node in the software security architecture diagram, and M is a positive integer; The control security modeling module obtains N security requirements from the security database according to each security attribute value to obtain Y security requirements, where Y = M*N, Y and N are positive integers; The control requirement detection module detects the Y security requirements to obtain the detection result of the target software, wherein, when the detection result indicates that the detection fails, the software security architecture diagram is redrawn until the detection result associated with the updated software security architecture diagram indicates that the detection passes.

2. The method according to claim 1, characterized in that The requirement detection module includes a requirement management module and a requirement verification module. The requirement management module includes a requirement review module. The requirement detection module is controlled to detect the Y security requirements. The detection results of the target software include: Control the requirement review module to conduct a rationality review on each security requirement according to multiple review tools, obtain Y review results, and send the Y review results to the requirement verification module; Control the requirement verification module to obtain detection rules, and verify each security requirement according to the detection rules to obtain Y verification results; In a case where the requirement verification module is controlled to receive the Y review results, the detection result is determined according to the Y verification results and the Y review results.

3. The method according to claim 1, characterized in that The requirement detection module includes a quality scoring module, which controls the requirement detection module to detect the Y security requirements, and the detection results of the target software include: Control the quality scoring module to identify the total number of review results representing the number of reviews that passed, to obtain a first total number, and to identify the total number of verification results representing the number of verifications that passed, to obtain a second total number; Obtain a first quantity threshold, a second quantity threshold, and a third quantity threshold, control the quality scoring module to compare the first quantity threshold with the number of the Y security requirements to obtain a first comparison result, and compare the second quantity threshold with the first total number to obtain a second comparison result; The quality scoring module is controlled to compare the third quantity threshold with the second total number to obtain a third comparison result, and the detection result is determined according to the first comparison result, the second comparison result and the third comparison result.

4. The method according to claim 3, characterized in that Determining the detection result based on the first comparison result, the second comparison result, and the third comparison result includes: If the first comparison result indicates that the first quantity threshold is less than the number of the Y safety requirements, the second comparison result indicates that the second quantity threshold is less than the first total number, and the third comparison result indicates that the third quantity threshold is less than the second total number, a test result of passing the test is generated; When the first quantity threshold is greater than or equal to the number of the Y safety requirements, or the second quantity threshold is greater than or equal to the first total number, or the third quantity threshold is greater than or equal to the second total number, a test result indicating that the test failed is generated.

5. The method according to claim 1, characterized in that The security modeling module includes a security attribute mapping module and a security database management module. The security database management module is associated with the security database and controls the security modeling module to obtain N security requirements from the security database according to each security attribute value. The obtained Y security requirements include: Controlling the security attribute mapping module to communicate with the security database management module, and obtaining the security database from the security database management module; The N security requirements associated with each security attribute value are screened from the security database to obtain the Y security requirements.

6. The method according to claim 1, characterized in that The security modeling module also includes a model building module, and the method also includes: The model building module is controlled to establish a security threat model according to the Y security requirements, and the security threat model is displayed, wherein the security threat model is used to display the applicable scope associated with the Y security requirements.

7. The method according to claim 2, characterized in that The requirement management module also includes a requirement synchronization module and a requirement tracking module. After controlling the requirement review module to conduct a rationality review on each security requirement according to multiple review tools and obtaining Y review results, the method further includes: Control the requirement synchronization module to identify the Y review results, and synchronize the review results representing the security requirements that have passed the review to the management system; Control the requirement tracking module to display the review progress of each security requirement.

8. A secure development process management system, characterized in that: include: A security design module, configured to draw a software security architecture diagram according to the software initial data upon receiving the software initial data of the target software, determine M security attribute values ​​based on the software security architecture diagram, and send the M security attribute values ​​to a security modeling module, wherein the software security architecture diagram is used to characterize the mutual relationship between components in the target software, each security attribute value characterizes the attribute correspondence relationship of each node in the software security architecture diagram, and M is a positive integer; The security modeling module is used to obtain N security requirements from the security database according to each security attribute value when receiving the M security attribute values, obtain Y security requirements, and send the Y security requirements to the requirement detection module, where Y=M*N, Y and N are positive integers; The requirement detection module is used to detect each group of security requirements when receiving the Y security requirements to obtain the detection result of the target software.

9. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the software security detection method according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the software security detection method described in any one of claims 1 to 7.

Images