A method and system for development security management of application software

By establishing a security management relationship diagram and cloud security tool library in the development of banking application software, and combining it with a development behavior evaluation model, we have achieved full-process security management, solved the problems of low efficiency and insufficient risk control in existing technologies, and improved development efficiency and security.

CN118551390BActive Publication Date: 2024-11-15BANK OF SHANGHAI

Patent Information

Application Number
CN202411023035.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-07-29
Publication Date
2024-11-15
Estimated Expiration
2044-07-29

AI Technical Summary

Technical Problem

Existing software development management systems are unable to effectively improve development efficiency, prevent security vulnerabilities and information leaks in banking application software development, and fail to effectively analyze and control potential risks.

Method used

By establishing a security management relationship diagram, loading relevant business test interfaces, configuring the cloud security tool library, and utilizing a trained development behavior evaluation model, we can conduct full-process security management, including verification and retesting of each node in functional requirements, development, testing, deployment, and release.

Benefits of technology

It has achieved full-process security management, improved development efficiency, effectively prevented security vulnerabilities and information leakage, reduced risks, and ensured the security and stability of banking application software.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118551390B_ABST
    Figure CN118551390B_ABST
Patent Text Reader

Abstract

The present invention is applicable to the field of computer technology, and provides a development security management method and system for application software, the method comprising: determining a security management relationship diagram for application software development based on the process of application software development; loading relevant business test interfaces in the security management relationship diagram; establishing a software development process model and a cloud security tool library, wherein the cloud security tool library is configured with security audit tools, security development tools, testing tools and evaluation tools; based on the software development process model, calling corresponding tools of the cloud security tool library to verify software function module data generated by different process nodes, and outputting whether they pass the verification; judging whether the generation time of software function module data at different process nodes exceeds the control time point through a trained development behavior evaluation model; the present invention can perform security management in the entire process of the software development process, rather than just performing simple development collaboration, thereby improving the overall development efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the field of computer technology, and in particular relates to a development security management method and system for application software. Background Art

[0002] With the rapid development of information technology, application software is increasingly used in all walks of life. However, in the process of software development, security issues are becoming increasingly prominent, such as code vulnerabilities and data leakage, which bring huge risks to enterprises and users. Therefore, the industry has begun to carry out application software development security management in order to reduce the probability of such risks.

[0003] Compared with ordinary application software, banking application software has more things to pay attention to during the development process, which is due to the complexity and security requirements of banking business. For example, for customer financial management, multiple terminals include online banking, ATM, call center, credit management system, etc., which need to interact directly or indirectly with the core system. Another example is that banking business is not limited to RMB business, but also includes foreign currency business, as well as intermediary businesses such as foreign exchange trading, fund business, and credit card business. These diverse business scenarios require application software to be highly flexible and scalable to cope with different business needs and ensure security, stability, efficiency and regulatory compliance.

[0004] The development process of the above software, whether in the early, middle or late stages, cannot be separated from the auxiliary support of the software development management system. However, most of the existing software development management systems only carry out simple development collaboration, and therefore cannot improve the overall development efficiency and effectively prevent the occurrence of security vulnerabilities and information leakage. At the same time, they also fail to analyze and control the potential risks in software development, which in turn brings unnecessary losses and increased costs. It is necessary to improve them. Summary of the invention

[0005] The object of the present invention is to provide a development security management method for application software to solve at least one problem mentioned in the background technology.

[0006] The present invention is implemented as follows: a method for developing security management for application software, the method comprising the following steps:

[0007] Based on the application software development process, determine the security management relationship diagram of application software development, which marks the process nodes of application software functional requirements, development, testing, deployment and release;

[0008] Load relevant business test interfaces in the security management relationship diagram, which include core business interfaces, bank payment interfaces, bank clearing interfaces, and third-party interaction interfaces;

[0009] Establish a software development process model and a cloud security tool library, which is equipped with security audit tools, security development tools, testing tools, and evaluation tools;

[0010] Based on the software development process model, call the corresponding tools in the cloud security tool library to verify the software function module data generated by different process nodes, and check whether the output passes the verification;

[0011] Use the trained development behavior evaluation model to determine whether the generation time of the software function module data at different process nodes exceeds the control time point;

[0012] Retest or expert evaluate the software function module data at the process nodes that failed verification or timed out, and output the retest or evaluation results.

[0013] Furthermore, the step of determining the security management relationship diagram of application software development based on the application software development process includes:

[0014] Obtain historical process data of application software development within a certain period of time and perform data preprocessing;

[0015] Extract the smallest functional modules of the application software, and allocate all the smallest functional modules based on the division of labor and timing of software development to form a security management relationship diagram;

[0016] Extract the time nodes of each link in the development process, which are functional requirements, development, testing, deployment and release;

[0017] Cluster all time nodes of each link, determine the typical time nodes of each link, and add them to the security management relationship diagram.

[0018] Furthermore, in the step of extracting the smallest sub-functional modules of the application software and allocating all the smallest sub-functional modules based on the division of labor and timing of software development to form a security management relationship diagram,

[0019] Division of software development: determined by a pre-archived directory of developers;

[0020] The timing of software development: first assign an initial value, and after allocating the developers corresponding to the smallest sub-functional module, update it. The update at least includes advance, maintain or adjust.

[0021] Furthermore, the steps of establishing the software development process model and the cloud security tool library specifically include:

[0022] On the security management side, set the management architecture of the software operating environment according to the development requirements of the application software;

[0023] Divide the management area of ​​each process node in the management architecture to execute the software function module data generated by each process node;

[0024] Set up security tools for each process node and connect them to the corresponding management area to form a software development process model;

[0025] Establish a cloud security tool library in the cloud server and connect the cloud server with the security management terminal.

[0026] Furthermore, the method further comprises: training and developing a behavior evaluation model;

[0027] The steps of training and developing the behavior evaluation model specifically include:

[0028] Based on a knowledge graph, establish an initial development behavior evaluation model;

[0029] Obtain historical software development data from developers and build a triple matrix of the magnitude, development difficulty, and development time of each software;

[0030] The triple matrices of all historical software are used as sample sets and input into the development behavior evaluation model for model training to obtain a trained development behavior evaluation model.

[0031] Furthermore, the step of judging whether the generation time of the software function module data of different process nodes exceeds the control time point by using the trained development behavior evaluation model specifically includes:

[0032] Performing peer matching on the development difficulty of the currently developed application software through the development behavior evaluation model;

[0033] Output the development time of software function modules of different process nodes of the application software according to the matching results, and obtain the generation time of the software function module data;

[0034] Determine whether the generation time exceeds the control time point.

[0035] Furthermore, in the step of determining whether the generation time exceeds the control time point, the method further includes:

[0036] Determine whether the control time point settings are reasonable, mark the process nodes corresponding to unreasonable control time points, and output the judgment results.

[0037] The present invention provides a development security management system for application software, which is used in the method described, and the system includes:

[0038] The management environment setting module can determine the security management relationship diagram of application software development based on the application software development process. The security management relationship diagram marks the process nodes of application software functional requirements, development, testing, deployment and release;

[0039] A test interface loading module is used to load relevant business test interfaces in the security management relationship diagram, wherein the relevant business test interfaces include core business interfaces, bank payment interfaces, bank clearing interfaces, and third-party interaction interfaces;

[0040] Model building module, used to build software development process model and cloud security tool library, which is equipped with security audit tools, security development tools, testing tools and evaluation tools;

[0041] The security tool testing module can call the corresponding tools in the cloud security tool library to verify the software function module data generated by different process nodes based on the software development process model, and output whether it passes the verification;

[0042] The development behavior analysis module is used to determine whether the generation time of the software function module data at different process nodes exceeds the control time point through the trained development behavior evaluation model;

[0043] The review and output module is used to retest or expert evaluate the software function module data at the process nodes that have not passed the verification or timed out, and output the retest or evaluation results.

[0044] Furthermore, the management environment setting module includes:

[0045] Develop a data acquisition unit, which is used to acquire historical process data of application software development within a certain period of time and perform data preprocessing;

[0046] Functional module extraction and connection unit, used to extract the smallest functional module of the application software, and allocate all the smallest functional modules based on the division of labor and timing of software development to form a security management relationship diagram;

[0047] The time node extraction unit is used to extract the time nodes of each link in the development process, namely functional requirements, development, testing, deployment and release;

[0048] The typical parameter clustering unit is used to cluster all the time nodes of each link, determine the typical time nodes of each link, and add them to the security management relationship diagram.

[0049] The present invention provides a development security management method for application software. Compared with the prior art, the present invention can perform security management throughout the entire software development process, such as testing, verification, retesting and expert evaluation, rather than just simple development collaboration, thereby improving the overall development efficiency, effectively preventing the occurrence of security vulnerabilities and information leakage, and at the same time determining whether there are potential risks based on development behavior analysis, thereby reducing risks. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 A flow chart of a development safety management method for application software provided by the present invention;

[0051] Figure 2 is the first sub-flow chart of the present invention;

[0052] Figure 3 is the second sub-flow chart of the present invention;

[0053] Figure 4 is the third sub-flow chart of the present invention;

[0054] Figure 5 is the fourth sub-flow chart of the present invention;

[0055] Figure 6 is the fifth sub-flow chart of the present invention;

[0056] Figure 7 A structural block diagram of a development safety management system for application software provided by the present invention;

[0057] Figure 8 A structural diagram of the management environment setting module in the present invention;

[0058] Fig. 9 An application environment diagram of a development safety management method for application software provided by the present invention;

[0059] Fig.10 The present invention provides a block diagram of the internal structure of a computer device. DETAILED DESCRIPTION

[0060] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0061] Figure 1 A flowchart of a method for development security management of application software provided by an embodiment of the present invention may specifically include steps S101 to S106:

[0062] S101. Based on the process of application software development, determine a security management relationship diagram for application software development, where the process nodes of functional requirements, development, testing, deployment, and release of the application software are marked in the security management relationship diagram;

[0063] In this step, the functional requirements, development, testing, deployment and release of application software are general security management processes; among them, the functional requirements, for example, when the software development requirements are determined, it is found that the verification code interface of the account registration function is vulnerable to attack. In this regard, measures can be taken to increase the length and complexity of the verification code, limit the frequency of sending verification codes, enable the cooling time mechanism of the verification code, add an anti-explosion mechanism, limit the request frequency and number of requests for each IP address, etc., to enhance the security of the software.

[0064] Security management relationship diagram: It is a visual representation of the relationship between functional requirements, development, testing, deployment and release, as well as the test location of the functional modules that developers are responsible for in each process node.

[0065] For example, during the software development phase, it is necessary to understand and manage cross-site scripting (XSS), SQL injection, cross-site request forgery (CSRF), encryption of sensitive data, etc.

[0066] In step S101, based on the process of application software development, a security management relationship diagram for application software development is determined. Figure 2 , which may include:

[0067] S201, obtaining historical process data of application software development within a certain period of time, and performing data preprocessing;

[0068] The certain period of time may be half a year, one year, or two years, etc. Generally, software development tools are updated very quickly, so the time can be determined as needed;

[0069] Data preprocessing, including but not limited to data cleaning, data alignment, normalization, etc.

[0070] S202, extracting the minimum functional modules of the application software, and allocating all the minimum functional modules based on the division of labor and timing of software development to form a security management relationship diagram;

[0071] Among them, the functional modules are: account registration, account verification (password verification, face recognition, SMS verification, etc.), personal center, software homepage, wealth, etc.; these functional modules are divided into more detailed modules, such as: transfer, income and expenditure, credit cards, deposits, loans, financial management, etc.

[0072] S203, extracting the time nodes of each link in the development process, where each link is functional requirements, development, testing, deployment and release;

[0073] For example: the time periods corresponding to functional requirements, development, testing, deployment, and release are: one week, eight weeks, one week, one week, and one day respectively; after the development project of the application software is determined, the time period of the functional requirements link is used as the starting point, and other links are derived from this; conversely, based on this principle, the time nodes of each link in the development process can be extracted.

[0074] S204: Cluster all time nodes of each link, determine the typical time node of each link, and add it to the security management relationship diagram.

[0075] The clustering of time nodes may adopt a conventional clustering algorithm, such as the K-means algorithm.

[0076] S102. Load relevant business test interfaces in the security management relationship diagram, where the relevant business test interfaces include core business interfaces, bank payment interfaces, bank clearing interfaces, and third-party interaction interfaces;

[0077] Taking a certain banking application software as an example, the third-party interactive interface is the settlement call interface of Taobao, Pinduoduo, JD.com, etc.

[0078] S103. Establish a software development process model and a cloud security tool library, wherein the cloud security tool library is configured with security audit tools, security development tools, testing tools, and evaluation tools;

[0079] In this step, based on the functional requirements, development, testing, deployment and release process nodes, etc., security development tools (such as static code analysis, dynamic analysis, etc.) can be used to automatically detect and fix security issues; security testing and penetration testing can be performed on the application software's operating system, data security testing and personal information protection testing can be performed on the data, and security checks can be performed on the configuration library and operating environment. During the deployment and release phase, compliance verification in terms of security assessment, password assessment, risk assessment, etc. may be required, and penetration testing may be performed regularly or irregularly. Of course, it is not limited to these methods.

[0080] It is understandable that the security tools in the cloud security tool library can also be set according to banking application software; for example: security testing tools within the industry are selected in terms of personal privacy, data confidentiality and regulatory compliance, and are pre-set to facilitate subsequent testing and management.

[0081] The operation of the software development process model can be carried out based on the following stages, thereby achieving full process management of functional requirements, development, testing, deployment and release process nodes, etc.; it is not limited to simple collaboration.

[0082] During the development phase, manage the security coding standards of mainstream programming languages ​​and score developers (or development teams) based on these standards; security coding standards include code writing standards, database standard interfaces, input and output verification, etc., which can effectively reduce code vulnerabilities such as buffer overflows, cross-site scripting, and SQL injections; then the development team needs to analyze all functions and APIs used in the application software development project, disable functions and APIs that are determined to be unsafe, and build a secure function library; finally, the development team should conduct code analysis, check the quality of the code through manual code review or static code analysis tools, and reduce problems such as syntax errors and security vulnerabilities in the code. In addition, version management of the source code is required to ensure the correctness of the application software version.

[0083] In the testing phase, after development is completed, test design is required based on threat modeling. First, the application software is subjected to black box testing. Based on the intended use and functions of the application software, badly formatted or random data is deliberately input into the application software to induce program failures and detect the security of the application software. Then a penetration test is conducted, in which professionals simulate hackers to attack the application software. Through penetration testing, potential vulnerabilities caused by coding errors, system configuration errors or other operational deployment weaknesses are discovered.

[0084] In addition, security testing of application software can also be carried out through security crowd-testing platforms, such as Alibaba Cloud's Prophet Platform and some open source white hat crowd-testing platforms.

[0085] During the release phase, the application software must first be integrated tested in a similar production environment to ensure that it can run safely; then security experts will conduct a final security review, and if it passes the security review, it can be released.

[0086] S104. Based on the software development process model, call the corresponding tool of the cloud security tool library to verify the software function module data generated by different process nodes, and output whether it passes the verification;

[0087] The specific verification process can be implemented according to the above-mentioned development phase, testing phase, release phase and other operation processes.

[0088] S105. Determine whether the generation time of the software function module data of different process nodes exceeds the control time point through the trained development behavior evaluation model;

[0089] For example: the time corresponding to functional requirements, development, testing, deployment and release is: one week, eight weeks, one week, one week, one day; the control time point can be obtained by adding the corresponding time to the starting point of the project.

[0090] S106 , retesting or expert evaluation is performed on the software function module data at the process nodes that have failed verification or timed out, and the retesting or evaluation results are output.

[0091] In an example of this embodiment, the method is used in a security management system for application software development, which can be deployed on a cloud server or a management terminal managed by an administrator, for example: Fig. 9 The management end A and management end B (specifically computers); the equipment used for application software development is the development end, that is, development end A, development end B, development end C, etc. (also computers).

[0092] It should be noted that the banking system requires strict security requirements, data encryption and protection, and multi-level security protection; it has high stability and reliability, core system stability: the core banking system is the foundation of banking business and requires high stability and reliability; application software must undergo rigorous testing during the development process to ensure that it can work properly under various circumstances; disaster recovery and business continuity: the banking system must have the ability to recover quickly in the event of a failure or disaster to ensure business continuity. This requires that the application software must consider backup and recovery mechanisms, as well as disaster recovery and business continuity plans when designing. As well as regulatory compliance, technology selection and implementation, and good user experience and interface interaction design, etc. Therefore, when conducting retests or expert evaluations and outputting retest or evaluation results, you can focus on them for highlighting and significant reminders.

[0093] In an example of this embodiment, in the step of extracting the smallest sub-functional modules of the application software, allocating all the smallest sub-functional modules based on the division of labor and timing of software development, and forming a security management relationship diagram,

[0094] Division of software development: determined by a pre-archived directory of developers;

[0095] The timing of software development: first assign an initial value, and after allocating the developers corresponding to the smallest sub-functional module, update it. The update at least includes advance, maintain or adjust.

[0096] In one example of this embodiment, Figure 3 As shown, the steps of establishing the software development process model and the cloud security tool library specifically include:

[0097] S301. On the security management side, according to the development requirements of the application software, set the management architecture of the software operating environment;

[0098] For example: when applied to Android systems, iOS systems, Windows systems, etc., different systems set up different software operating environments, and system simulation can also be achieved by establishing a virtual machine.

[0099] S302, dividing the management area of ​​each process node in the management architecture to execute the software function module data generated by each process node;

[0100] S303, setting up security tools for each process node and connecting them to the corresponding management area to form a software development process model;

[0101] Corresponding security tools include security audit tools, security development tools, testing tools, evaluation tools, etc.

[0102] S304: Establish a cloud security tool library in the cloud server and connect the cloud server to the security management terminal.

[0103] In one embodiment, Figure 4 As shown, the method also includes:

[0104] S401, training development behavior evaluation model;

[0105] In this embodiment, the specific model training belongs to the prior art. Of course, you can also refer to Figure 5 The steps of training and developing the behavior evaluation model specifically include:

[0106] S501. Based on a knowledge graph, establish an initial development behavior evaluation model;

[0107] S502, obtaining historical software development data of developers, and establishing a triple matrix for the magnitude, development difficulty and development time of each software;

[0108] After obtaining the historical software development data of the developer, the data may also be preprocessed, as described above for details.

[0109] S503: Take the triple matrices of all historical software as sample sets, input them into the development behavior evaluation model for model training, and obtain a trained development behavior evaluation model.

[0110] In one embodiment, Figure 6 As shown, the step of judging whether the generation time of the software function module data of different process nodes exceeds the control time point by using the trained development behavior evaluation model specifically includes:

[0111] S601, performing peer matching of the development difficulty of the currently developed application software through the development behavior evaluation model;

[0112] S602, output the development time of the software function modules of different process nodes of the application software according to the matching result, and obtain the generation time of the software function module data;

[0113] S603, determining whether the generation time exceeds the control time point;

[0114] If it does not exceed the control time point, no operation will be performed; if it exceeds, retesting or other processing will be carried out.

[0115] In an example of this embodiment, in the step of determining whether the generation time exceeds the control time point, the method further includes:

[0116] Determine whether the control time point settings are reasonable, mark the process nodes corresponding to unreasonable control time points, and output the judgment results;

[0117] In this way, accidents caused by inaccurate matching of the development difficulty of the currently developed application software can be avoided.

[0118] like Figure 7 As shown, in another embodiment, a development security management system for application software, used in the method described, the system comprising:

[0119] The management environment setting module 100 can determine the security management relationship diagram of application software development based on the process of application software development, and the process nodes of functional requirements, development, testing, deployment and release of application software are marked in the security management relationship diagram;

[0120] The test interface loading module 200 is used to load the relevant business test interface in the security management relationship diagram, and the relevant business test interface includes a core business interface, a bank payment interface, a bank clearing interface and a third-party interaction interface;

[0121] The model building module 300 is used to build a software development process model and a cloud security tool library, in which security audit tools, security development tools, testing tools and evaluation tools are configured;

[0122] The security tool testing module 400 can call the corresponding tools of the cloud security tool library to verify the software function module data generated by different process nodes based on the software development process model, and output whether it passes the verification;

[0123] The development behavior analysis module 500 is used to determine whether the generation time of the software function module data of different process nodes exceeds the control time point through the trained development behavior evaluation model;

[0124] The review and output module 600 is used to retest or expert evaluate the software function module data at the process nodes that have not passed the verification or timed out, and output the retest or evaluation results.

[0125] In an example of this embodiment, Figure 8 As shown, the management environment setting module 100 includes:

[0126] The development data acquisition unit 110 is used to acquire the historical process data of application software development within a certain period of time and perform data preprocessing;

[0127] The function module extraction and connection unit 120 is used to extract the minimum function module of the application software, and allocate all the minimum function modules based on the division of labor and timing of software development to form a security management relationship diagram;

[0128] A time node extraction unit 130 is used to extract the time nodes of each link in the development process, and each link is functional requirements, development, testing, deployment and release;

[0129] The typical parameter clustering unit 140 is used to cluster all the time nodes of each link, determine the typical time nodes of each link, and add them to the security management relationship diagram.

[0130] In one embodiment, the acquired data is preprocessed; generally, the data preprocessing that can be performed includes classification, screening and processing; data preprocessing is a prior art and will not be described in detail here.

[0131] An embodiment of the present invention provides a development security management method for application software. The method can perform security management throughout the entire software development process, rather than just simple development collaboration, thereby improving the overall development efficiency, effectively preventing the occurrence of security vulnerabilities and information leakage, and at the same time determining whether there are potential risks based on development behavior analysis, thereby reducing risks.

[0132] like Fig.10 As shown, in another embodiment, a computer device is provided, wherein the computer device stores a computer program, and when the computer program is executed by a processor, the processor executes steps S101 to S106 of the development security management method for application software.

[0133] Fig.10The internal structure diagram of a computer device in one embodiment is shown. The computer device includes a processor, a memory, a network interface, an input device and a display screen connected through a system bus. Among them, the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program. When the computer program is executed by the processor, the processor can implement a development security management method for application software. The internal memory may also store a computer program. When the computer program is executed by the processor, the processor can execute a development security management method for application software. The display screen of the computer device may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device may be a touch layer covered on the display screen, or a button, trackball or touchpad provided on the housing of the computer device, or an external keyboard, touchpad or mouse, etc.

[0134] It should be understood that, although each step in the flow chart of each embodiment of the present invention is shown in sequence according to the indication of the arrow, these steps are not necessarily performed in sequence according to the order indicated by the arrow. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be performed in other orders. Moreover, at least a portion of the steps in each embodiment may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these sub-steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0135] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0136] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0137] The above-mentioned embodiments only express several implementation methods of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the scope of the patent of the present invention. It should be pointed out that, for ordinary technicians in this field, several variations and improvements can be made without departing from the concept of the present invention, which all belong to the protection scope of the present invention. Therefore, the protection scope of the patent of the present invention shall be subject to the attached claims.

[0138] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for development security management of application software, characterized in that: The method comprises: Based on the application software development process, determine the security management relationship diagram of application software development, which marks the process nodes of application software functional requirements, development, testing, deployment and release; Load relevant business test interfaces in the security management relationship diagram, which include core business interfaces, bank payment interfaces, bank clearing interfaces, and third-party interaction interfaces; Establish a software development process model and a cloud security tool library, which is equipped with security audit tools, security development tools, testing tools, and evaluation tools; Based on the software development process model, call the corresponding tools in the cloud security tool library to verify the software function module data generated by different process nodes, and check whether the output passes the verification; Training the development behavior evaluation model; the steps of training the development behavior evaluation model specifically include: establishing an initial development behavior evaluation model based on a knowledge graph; obtaining historical software development data of developers, and establishing a triple matrix for the magnitude, development difficulty and development time of each software; using the triple matrix of all historical software as a sample set, inputting it into the development behavior evaluation model for model training, and obtaining a trained development behavior evaluation model; Use the trained development behavior evaluation model to determine whether the generation time of the software function module data at different process nodes exceeds the control time point; Retest or expert evaluate the software function module data at the process nodes that failed verification or timed out, and output the retest or evaluation results; The step of judging whether the generation time of the software function module data of different process nodes exceeds the control time point by using the trained development behavior evaluation model specifically includes: Performing peer matching on the development difficulty of the currently developed application software through the development behavior evaluation model; Output the development time of software function modules of different process nodes of the application software according to the matching results, and obtain the generation time of the software function module data; Determine whether the generation time exceeds the control time point; The step of determining the security management relationship diagram of application software development based on the application software development process includes: Obtain historical process data of application software development within a certain period of time and perform data preprocessing; Extract the smallest functional modules of the application software, and allocate all the smallest functional modules based on the division of labor and timing of software development to form a security management relationship diagram; Extract the time nodes of each link in the development process, which are functional requirements, development, testing, deployment and release; Cluster all time nodes of each link, determine the typical time nodes of each link, and add them to the safety management relationship diagram; In the step of extracting the smallest sub-functional module of the application software, allocating all the smallest sub-functional modules based on the division of labor and timing of software development, and forming a security management relationship diagram, Division of software development: determined by a pre-archived directory of developers; The timing of software development: first assign an initial value, and after assigning the developer corresponding to the smallest sub-functional module, update it. The update includes at least advance, maintain or adjust; The steps of establishing the software development process model and the cloud security tool library specifically include: On the security management side, set the management architecture of the software operating environment according to the development requirements of the application software; Divide the management area of ​​each process node in the management architecture to execute the software function module data generated by each process node; Set up security tools for each process node and connect them to the corresponding management area to form a software development process model; Establish a cloud security tool library in the cloud server and connect the cloud server with the security management terminal.

2. The method according to claim 1, characterized in that: In the step of determining whether the generation time exceeds the control time point, the method further includes: determining whether the control time point is set reasonably, marking the process nodes corresponding to the unreasonable control time points, and outputting the determination result.

3. A development security management system for application software, used in the method according to any one of claims 1-2, characterized in that: The system comprises: The management environment setting module can determine the security management relationship diagram of application software development based on the application software development process. The security management relationship diagram marks the process nodes of application software functional requirements, development, testing, deployment and release; A test interface loading module is used to load relevant business test interfaces in the security management relationship diagram, wherein the relevant business test interfaces include core business interfaces, bank payment interfaces, bank clearing interfaces, and third-party interaction interfaces; Model building module, used to build software development process model and cloud security tool library, which is equipped with security audit tools, security development tools, testing tools and evaluation tools; The security tool testing module can call the corresponding tools in the cloud security tool library to verify the software function module data generated by different process nodes based on the software development process model, and output whether it passes the verification; The development behavior analysis module is used to determine whether the generation time of the software function module data at different process nodes exceeds the control time point through the trained development behavior evaluation model; The review and output module is used to retest or expert evaluate the software function module data at the process nodes that have not passed the verification or timed out, and output the retest or evaluation results.

4. The system according to claim 3, characterized in that The management environment setting module includes: Develop a data acquisition unit, which is used to acquire historical process data of application software development within a certain period of time and perform data preprocessing; Functional module extraction and connection unit, used to extract the smallest functional module of the application software, and allocate all the smallest functional modules based on the division of labor and timing of software development to form a security management relationship diagram; The time node extraction unit is used to extract the time nodes of each link in the development process, namely functional requirements, development, testing, deployment and release; The typical parameter clustering unit is used to cluster all the time nodes of each link, determine the typical time nodes of each link, and add them to the security management relationship diagram.

Citation Information

Patent Citations

  • Quality detection method and device for financial transaction software

    CN111352841A

  • Method and system for optimizing project management in software development

    CN112068806A

  • Software system research and development quality evaluation method and system, storage medium and electronic equipment

    CN112328490A

  • Software development man-hour determination method and device

    CN113689191A

  • Software defect prediction and quality analysis method and device, equipment and medium

    CN114328277A

Cited By

  • Software development security test management method and system

    CN120687357A

  • Software development security test management method and system

    CN120687357B