Software supply chain security management method and system based on DevSecOps
Through the DevSecOps-based method, we collect and analyze open source data, establish a security warehouse, and use security analysis engines and plug-ins, we solve the problems of low automation and single vulnerability detection of existing tools, and realize the full life cycle security control of the software supply chain and Autonomous and controllable vulnerability detection.
Patent Information
- Application Number
- CN202410138398.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-31
- Publication Date
- 2024-11-12
AI Technical Summary
The existing software supply chain security governance tools lack security tools with high performance, high automation, high maturity and good visibility, and face unknown vulnerabilities and closed source supply risks, making them difficult to integrate into the development process, low automation, and vulnerabilities Single detection method.
Based on DevSecOps method, open source data is collected to establish an open source data knowledge base and security warehouse, scan open source and self-developed components of software products through security analysis engine and plug-ins, generate repair suggestions, and achieve full life cycle security through risk monitoring and alarm plug-ins. Control and provide independent and controllable, plug-in, automated and systematic vulnerability detection.
It realizes security control over the entire life cycle of software engineering, reduces development and maintenance costs, improves the degree of automation and the diversity of vulnerability detection, and enhances the security and controllability of the software supply chain.
Smart Images

Figure CN118940269A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of software development, and in particular relates to a software supply chain security governance method and system based on DevSecOps. Background Art
[0002] The software supply chain refers to the network structure formed by upstream and downstream enterprises that provide components, frameworks, software engineering, products or application services involved in the software development process to end users.
[0003] At present, the domestic software supply chain is developing rapidly, and the proportion of open source is increasing year by year. The introduction of open source software has brought great convenience to agile development. However, the violation of open source license agreements in the reference process, uncontrollable supply channels, lack of detection and repair of vulnerabilities and malicious codes, etc., have brought huge security threats to the software supply chain. In addition, my country's open source community mainly relies on foreign open source communities, with obvious shortcomings of strong dependence and weak autonomy. The international mainstream open source foundations, open source projects, and most open source licenses were born in the United States or controlled by American companies. They may be closed and cut off at any time due to the international political environment, and there is a huge risk of open source software supply interruption. Therefore, software supply chain security governance is imminent and has become an important new path to break through business defenses and technical blockades.
[0004] There are three main risk aspects in the software supply chain, namely the supply chain introduction link, software production link, and software application link, covering multiple stages in the entire software development life cycle, such as design, coding, testing, release, operation and maintenance, and final delivery. Common software development uses the Development Operations (DevOps) model, in which the development, testing, and operation stages often focus on the product's own business. Vulnerabilities introduced by open source code reuse are often ignored. Due to time costs and repair costs, security is always independent of the entire DevOps process, providing soil for the breeding of various software supply chain security issues. Therefore, in this context, the secure Development Security Operations (DevSecOps) model came into being. DevSecOps focuses on solving security compliance requirements and efficiency requirements, while reducing development and maintenance costs, shifting security work to the left, and carrying out development, testing, and operation work at the same time, and flexibly embedding it into the entire software development life cycle. Relying on the DevSecOps concept, by building a secure open source knowledge base, integrating secure project management and asset management processes, embedding security automated inspections and risk assessment warnings, etc., we conduct security management and control in the supply chain introduction link, software production link, and software application link. We will integrate security into every link of the design, development, testing, release, and operation and maintenance life cycle, promote the evolution of software development towards agility, automation, and security, and respond to the increasing software supply chain security risks.
[0005] However, in the practice of DevSecOps-based software supply chain security governance, there is a lack of security tools with good performance, high automation, high maturity and good visibility. The existing software supply chain security governance tools are often composed of a series of tool chains from different manufacturers, which are packaged or redeveloped by different open source software. The tools themselves have unknown vulnerabilities and are also facing the risk of closed source supply interruption. In addition, the tools are difficult to integrate into the existing development process, have a low degree of automation, and have a single vulnerability detection method. Therefore, it is of great significance to design a software supply chain security governance tool that is autonomous, controllable, plug-in, automated, systematic, and has diversified vulnerability detection methods. Summary of the invention
[0006] In response to the above technical problems, the present invention provides a software supply chain security governance method and system based on DevSecOps.
[0007] The technical solution adopted by the present invention to solve the technical problem is:
[0008] A software supply chain security governance method based on DevSecOps, the method comprising the following steps:
[0009] S100: Collect open source data and build an open source data knowledge base and open source software security warehouse based on the open source data;
[0010] S200: Scans the open source and self-developed components of software products based on the security analysis engine and plug-ins, analyzes the security risks of open source components, self-developed components and software products based on the open source data knowledge base, and generates repair suggestions;
[0011] S300: Automatically store open source and self-developed software components as assets in the asset library, and automatically store risk-free software products in the product warehouse;
[0012] S400: Use risk monitoring and alarm plug-ins to automatically monitor security risks and public opinion of assets in the asset library and artifacts in the artifact warehouse, as well as vulnerability and license risk alarms, to achieve security management and control of the entire life cycle of software engineering.
[0013] Preferably, S100 includes:
[0014] S110: Collect open source components, open source frameworks, vulnerabilities, licenses, and open source protocol data through data collection and cleaning techniques;
[0015] S120: Establish an open source data knowledge base based on open source components, open source frameworks, vulnerabilities, licenses, and open source protocol data;
[0016] S130: Establish an open source software security warehouse based on open source components and open source framework data; wherein, the open source software security warehouse provides security software frameworks, components and class libraries as development templates to perform demand design and product design and create software engineering.
[0017] Preferably, data collection in S110 uses a web crawler to collect, classify and summarize data in open source communities and open source repositories; data cleaning is performed by formulating data cleaning rules to deduplicate, format, standardize and filter the crawled data.
[0018] Preferably, S200 includes:
[0019] S210: In the coding phase, the security analysis engine and plug-ins provide IDE security analysis plug-ins and code repository security detection plug-ins. When the project uses IDE programs to write code, the IDE security analysis plug-in automatically performs dependency component analysis and open source license analysis on the code. When the project uses code repositories to manage code, the code repository security detection plug-in automatically performs code homology analysis and code cloning analysis on the code, and provides corresponding repair suggestions for detected security risks.
[0020] S220: During the build phase, the security analysis engine and plug-ins provide a build platform security detection plug-in. When the project uses the build platform for continuous code integration and build testing, the build platform security detection plug-in automatically performs code homology analysis and code cloning analysis on the code to be tested, and provides corresponding repair suggestions for the detected security risks.
[0021] S230: During the testing phase, the project conducts security testing and dynamic testing, and uses the security analysis engine and plug-ins to manually or automatically perform binary component analysis and binary homology analysis on the products submitted for testing, and provide corresponding repair suggestions for the detected security risks;
[0022] S240: During the release phase, the security analysis engine and plug-ins provide a release platform security detection plug-in. When the project uses the release platform to build and release, the release platform security detection plug-in automatically performs binary component analysis and binary homology analysis on the products to be released, and provides corresponding repair suggestions for the detected security risks.
[0023] Preferably, the dependency component analysis in S210 refers to matching the object model and detecting the object source through different rules based on the project object model management file, and then matching the information of open source components, open source frameworks and vulnerabilities by detecting the object model based on the open source data knowledge base, and performing vulnerability risk assessment; open source license analysis refers to matching the information of open source licenses and open source agreements by detecting the object model based on the open source data knowledge base, and performing closed source and illegal infringement risk assessment.
[0024] Preferably, the code homology analysis in S210 and S220 refers to matching code snippets and code sources based on source code through different rules, and then matching the information of open source components, open source frameworks and vulnerabilities by detecting the code snippets based on the open source data knowledge base, and performing vulnerability risk assessment; code clone analysis refers to matching the code source based on the compiled binary file by extracting bytecode feature values, input tables, output tables and disassembly, and then matching the information of open source components, open source frameworks and vulnerabilities by detecting the code source based on the open source data knowledge base, and performing vulnerability risk assessment.
[0025] Preferably, the binary component analysis in S230 and S240 refers to building a compiled binary file, matching feature sources by extracting bytecode feature values, input tables and output tables, and then matching open source components, open source frameworks and vulnerability information by detecting feature sources based on the open source data knowledge base, and performing vulnerability risk assessment; binary homology analysis refers to building a compiled binary file, matching code snippets and code sources through disassembly, and then matching open source components, open source frameworks and vulnerability information by detecting code snippets based on the open source data knowledge base, and performing vulnerability risk assessment.
[0026] Preferably, S300 specifically includes: automatically storing the open source components and self-developed components of the software detected by the security analysis engine and plug-ins during the coding stage, construction stage, testing stage, and release stage as assets into the asset library, and automatically storing the risk-free software products into the product warehouse.
[0027] Preferably, the risk monitoring and alarm plug-in in S400 is used for asset and product monitoring and risk alarm. Asset and product monitoring obtains change information of assets and products through regular scanning. Risk alarm conducts vulnerability, closed source and illegal infringement risk assessment based on change information combined with matching open source components, open source frameworks, vulnerabilities, open source licenses, open source agreements and international political opinion information. When the risk exceeds the threshold, a real-time alarm is issued.
[0028] The software supply chain security governance system based on DevSecOps includes open source data processing module, engineering analysis management module, asset management module and risk warning module.
[0029] The open source data processing module is used to collect open source data and establish an open source data knowledge base and an open source software security warehouse based on the open source data;
[0030] The engineering analysis management module is used to scan the open source components and self-developed components of software products based on the security analysis engine and plug-ins, analyze the security risks of open source components, self-developed components and software products based on the open source data knowledge base, and generate repair suggestions;
[0031] The asset management module is used to automatically store open source and self-developed software components as assets in the asset library, and automatically store risk-free software products in the product warehouse;
[0032] The risk warning module uses risk monitoring and alarm plug-ins to automatically monitor the security risks and public opinion of assets in the asset library and products in the product warehouse, and issue vulnerability and license risk alarms, thereby achieving security management and control of the entire life cycle of software engineering.
[0033] The above-mentioned software supply chain security governance method and system based on DevSecOps collects open source data to establish an open source data knowledge base and an open source software security warehouse, scans the open source components and self-developed components of codes and software products through self-developed security analysis engines and plug-ins, analyzes the security risks of open source components, self-developed components and software products based on the open source data knowledge base, generates repair suggestions, automatically stores the open source components and self-developed components of the software as assets into the asset library, and automatically stores the risk-free software products into the product warehouse. Finally, based on the risk monitoring and alarm plug-ins, the assets in the asset library and the products in the product warehouse are automatically monitored for security risks and public opinion, and vulnerability and license risk alarms are issued, so as to realize security management and control of the entire life cycle of software engineering. It has the advantages of autonomous control, plug-in, automation, systematization and diversified vulnerability detection methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Figure 1 It is a flow chart of a software supply chain security governance method based on DevSecOps in one embodiment of the present invention;
[0035] Figure 2 Schematic diagram of a software supply chain security governance method based on DevSecOps in one embodiment of the present invention;
[0036] Figure 3 The figure is a structural block diagram of a software supply chain security governance system based on DevSecOps in one embodiment of the present invention. DETAILED DESCRIPTION
[0037] In order to enable those skilled in the art to better understand the technical solution of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings.
[0038] In one embodiment, Figure 1 As shown, a software supply chain security governance method based on DevSecOps includes the following steps:
[0039] S100: Collect open source data and build an open source data knowledge base and open source software security warehouse based on the open source data;
[0040] S200: Scans the open source and self-developed components of software products based on the security analysis engine and plug-ins, analyzes the security risks of open source components, self-developed components and software products based on the open source data knowledge base, and generates repair suggestions;
[0041] S300: Automatically store open source and self-developed software components as assets in the asset library, and automatically store risk-free software products in the product warehouse;
[0042] S400: Use risk monitoring and alarm plug-ins to automatically monitor security risks and public opinion of assets in the asset library and artifacts in the artifact warehouse, as well as vulnerability and license risk alarms, to achieve security management and control of the entire life cycle of software engineering.
[0043] The above-mentioned software supply chain security governance method based on DevSecOps collects open source data to establish an open source data knowledge base and an open source software security warehouse, scans the open source components and self-developed components of codes and software products through self-developed security analysis engines and plug-ins, analyzes the security risks of open source components, self-developed components and software products based on the open source data knowledge base, generates repair suggestions, and automatically stores the open source components and self-developed components of the software as assets into the asset library through the asset management module, and automatically stores the risk-free software products into the product warehouse, and finally automatically monitors the security risks and public opinion of the assets in the asset library and the products in the product warehouse based on the risk monitoring and alarm plug-ins, and warns of vulnerabilities and license risks, so as to realize security management and control of the entire life cycle of software engineering; it has the advantages of autonomous control, plug-in, automation, systematization and diversified vulnerability detection methods.
[0044] In one embodiment, S100 includes:
[0045] S110: Collect open source components, open source frameworks, vulnerabilities, licenses, and open source protocol data through data collection and cleaning techniques;
[0046] S120: Establish an open source data knowledge base based on open source components, open source frameworks, vulnerabilities, licenses, and open source protocol data;
[0047] S130: Establish an open source software security warehouse based on open source components and open source framework data; wherein, the open source software security warehouse provides security software frameworks, components and class libraries as development templates to perform demand design and product design and create software engineering.
[0048] In one embodiment, data collection in S110 uses a web crawler to collect, classify and summarize data in open source communities and open source repositories; data cleaning is performed by formulating data cleaning rules to deduplicate, format, standardize and filter the crawled data.
[0049] Specifically, open source communities include Github, Gitee, Mvnrepository, debian and other communities.
[0050] In one embodiment, Figure 2 As shown, S200 includes:
[0051] S210: In the coding phase, the security analysis engine and plug-ins provide IDE security analysis plug-ins and code repository security detection plug-ins. When the project uses IDE programs to write code, the IDE security analysis plug-in automatically performs dependency component analysis and open source license analysis on the code. When the project uses code repositories to manage code, the code repository security detection plug-in automatically performs code homology analysis and code cloning analysis on the code, and provides corresponding repair suggestions for detected security risks.
[0052] S220: During the build phase, the security analysis engine and plug-ins provide a build platform security detection plug-in. When the project uses the build platform for continuous code integration and build testing, the build platform security detection plug-in automatically performs code homology analysis and code cloning analysis on the code to be tested, and provides corresponding repair suggestions for the detected security risks.
[0053] S230: During the testing phase, the project conducts security testing and dynamic testing, and uses the security analysis engine and plug-ins to manually or automatically perform binary component analysis and binary homology analysis on the products submitted for testing, and provide corresponding repair suggestions for the detected security risks;
[0054] S240: During the release phase, the security analysis engine and plug-ins provide a release platform security detection plug-in. When the project uses the release platform to build and release, the release platform security detection plug-in automatically performs binary component analysis and binary homology analysis on the products to be released, and provides corresponding repair suggestions for the detected security risks.
[0055] In one embodiment, the dependency component analysis in S210 refers to matching the object model and detecting the object source through different rules based on the project object model management file, and then matching the information of open source components, open source frameworks and vulnerabilities by detecting the object model based on the open source data knowledge base, and performing vulnerability risk assessment; open source license analysis refers to matching the information of open source licenses and open source agreements by detecting the object model based on the open source data knowledge base, and performing closed source and illegal infringement risk assessment.
[0056] In one embodiment, code homology analysis in S210 and S220 refers to matching code snippets and code sources through different rules based on source code, and then matching open source components, open source frameworks and vulnerability information by detecting code snippets based on the open source data knowledge base, and performing vulnerability risk assessment; code clone analysis refers to matching code sources based on building compiled binary files by extracting bytecode feature values, input tables, output tables and disassembly, and then matching open source components, open source frameworks and vulnerability information by detecting code sources based on the open source data knowledge base, and performing vulnerability risk assessment.
[0057] In one embodiment, the binary component analysis in S230 and S240 refers to matching feature sources by extracting bytecode feature values, input tables, and output tables based on the compiled binary file, and then matching open source components, open source frameworks, and vulnerability information by detecting feature sources based on the open source data knowledge base, and performing vulnerability risk assessment; binary homology analysis refers to matching code snippets and code sources by disassembling based on the compiled binary file, and then matching open source components, open source frameworks, and vulnerability information by detecting code snippets based on the open source data knowledge base, and performing vulnerability risk assessment.
[0058] In one embodiment, S300 specifically includes: automatically storing the open source components and self-developed components of the software detected by the security analysis engine and plug-ins during the coding stage, construction stage, testing stage, and release stage as assets into the asset library, and automatically storing the risk-free software products into the product warehouse.
[0059] In one embodiment, the risk monitoring and alarm plug-in in S400 is used for asset and product monitoring and risk alarm. Asset and product monitoring obtains change information of assets and products through regular scanning. Risk alarm conducts vulnerability, closed source and illegal infringement risk assessment based on change information combined with matching open source components, open source frameworks, vulnerabilities, open source licenses, open source agreements and international political opinion information. When the risk exceeds the threshold, a real-time alarm is issued.
[0060] Specifically, S400 is the operation and maintenance stage, during which the operation and maintenance personnel use risk monitoring and alarm plug-ins to automatically monitor the security risks and public opinion of the assets in the asset library and the products in the product warehouse, as well as vulnerability and license risk alarms, to achieve security management and control of the entire life cycle of software engineering.
[0061] Furthermore, in the initial planning stage, the spring-boot framework is obtained from the open source software security warehouse as a development template for the Web project to create a software engineering Web-project. In the coding stage, IntelliJIDEA 2022.1 tool is used for code development. Due to business needs, open source components spring-jdbc are introduced for database reading and writing, open source components httpclient are introduced for microservice interface calls, open source components spring-data-redis are introduced for Redis cache reading and writing, open source components jsoup are introduced for XML file parsing, open source components fastjson are introduced for JSON data processing, open source components javafx-swing are introduced for processing tree structure data, open source components kafka are introduced for internal message sending and receiving processing, and open source components spring-boot-starter-log4j2 are introduced for log collection and processing. In the release stage, due to installation and deployment needs, the middleware nacos-server-1.4.2 is introduced for configuration and service management. In the operation and maintenance stage, risk monitoring and alarm plug-ins are used to monitor the security risks, vulnerabilities and license risks of assets in the asset library and products in the product warehouse.
[0062] In a detailed example: developers use IntelliJ IDEA 2022.1 tools for code development during the coding phase, and use the security analysis engine and the IDE security analysis plug-in provided by the plug-in to analyze the dependency components of the development template spring-boot framework. After testing, the spring-boot framework contains 12 dependent open source components and 47 vulnerabilities were detected.
[0063] During the testing phase, the testers used the security analysis engine and the build platform security detection plug-in provided by the plug-in to perform binary homology analysis on the software engineering Web-project. After testing, the self-developed rate of the software engineering Web-project was 29.92%, including 30 open source components and 3 open source licenses.
[0064] During the release phase, the tester used the security analysis engine and the release platform security detection plug-in provided by the plug-in to perform binary component analysis on the middleware nacos-server-1.4.2. After testing, the middleware nacos-server-1.4.2 contains 4 open source components and 4 open source licenses were detected, all of which are low risk. Among them: the license GPL-2.0 has open source usage rights for commercial use, distribution, modification, and private use, has restrictions on use of liability and warranty, and requires disclosure of the source, license and copyright statement, the same license, and the conditions of use of status changes.
[0065] During the operation and maintenance phase, operation and maintenance personnel use risk monitoring and alarm plug-ins to monitor the security risks, vulnerabilities, and license risks of assets in the asset library and products in the product warehouse. After testing, the open source component across-job-modules in the asset library has the highest risk, including 105 vulnerabilities, and the feedback given by the risk monitoring and alarm plug-in is that it is strongly recommended to be repaired. The vulnerability CVE-2021-44228 associated with the open source components in the asset library has the highest risk, affecting 59 open source components, and the feedback given by the risk monitoring and alarm plug-in is that there is a fatal risk. The open source license EPL-2.0 associated with the open source components in the asset library has the highest risk, affecting 79 open source components, and the feedback given by the risk monitoring and alarm plug-in is that there is a high risk.
[0066] In one embodiment, Figure 3 As shown in the figure, the software supply chain security governance system based on DevSecOps includes open source data processing module, engineering analysis management module, asset management module and risk warning module.
[0067] The open source data processing module is used to collect open source data and establish an open source data knowledge base and an open source software security warehouse based on the open source data;
[0068] The engineering analysis management module is used to scan the open source components and self-developed components of software products based on the security analysis engine and plug-ins, analyze the security risks of open source components, self-developed components and software products based on the open source data knowledge base, and generate repair suggestions;
[0069] The asset management module is used to automatically store open source and self-developed software components as assets in the asset library, and automatically store risk-free software products in the product warehouse;
[0070] The risk warning module uses risk monitoring and alarm plug-ins to automatically monitor the security risks and public opinion of assets in the asset library and products in the product warehouse, and issue vulnerability and license risk alarms, thereby achieving security management and control of the entire life cycle of software engineering.
[0071] For the specific details of the DevSecOps-based software supply chain security governance system, please refer to the above description of the DevSecOps-based software supply chain security governance method, which will not be repeated here.
[0072] Compared with the prior art, the present invention has the following beneficial effects:
[0073] (1) The present invention uses self-developed data collection and cleaning technology to collect open source components, frameworks, vulnerabilities, licenses and open source protocol data, and uses self-developed security analysis engines and plug-ins to perform dependency component analysis, open source license analysis, code homology analysis, code clone analysis, binary component analysis and binary homology analysis on code and software products, which has the advantages of autonomous control and diversified vulnerability detection methods;
[0074] (2) The present invention flexibly integrates into the existing development process by means of automated scanning plug-ins, transforming the DevOps mode into the secure DevSecOp mode, and automatically detects potential risks of software in each link of the software development life cycle, such as design, development, testing, release, operation and maintenance. It has the advantages of plug-in, automation, and systematization.
[0075] The above is a detailed introduction to the software supply chain security governance method and system based on DevSecOps provided by the present invention. This article uses specific examples to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the core idea of the present invention. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present invention, the present invention can also be improved and modified, and these improvements and modifications also fall within the scope of protection of the claims of the present invention.
Claims
1. The software supply chain security governance method based on DevSecOps is characterized by: The method comprises the following steps: S100: Collect open source data and build an open source data knowledge base and open source software security warehouse based on the open source data; S200: Scans the open source and self-developed components of software products based on the security analysis engine and plug-ins, analyzes the security risks of open source components, self-developed components and software products based on the open source data knowledge base, and generates repair suggestions; S300: Automatically store open source and self-developed software components as assets in the asset library, and automatically store risk-free software products in the product warehouse; S400: Use risk monitoring and alarm plug-ins to automatically monitor security risks and public opinion of assets in the asset library and artifacts in the artifact warehouse, as well as vulnerability and license risk alarms, to achieve security management and control of the entire life cycle of software engineering.
2. The method according to claim 1, characterized in that: S100 includes: S110: Collect open source components, open source frameworks, vulnerabilities, licenses, and open source protocol data through data collection and cleaning techniques; S120: Establish an open source data knowledge base based on open source components, open source frameworks, vulnerabilities, licenses, and open source protocol data; S130: Establish an open source software security warehouse based on open source components and open source framework data; wherein, the open source software security warehouse provides security software frameworks, components and class libraries as development templates to perform demand design and product design and create software engineering.
3. The method according to claim 2, characterized in that Data collection in S110 uses web crawlers to collect, classify and summarize data in open source communities and open source repositories; data cleaning removes duplication, formats, standardizes and filters the crawled data by formulating data cleaning rules.
4. The method according to claim 1, characterized in that: S200 includes: S210: In the coding phase, the security analysis engine and plug-ins provide IDE security analysis plug-ins and code repository security detection plug-ins. When the project uses IDE programs to write code, the IDE security analysis plug-in automatically performs dependency component analysis and open source license analysis on the code. When the project uses code repositories to manage code, the code repository security detection plug-in automatically performs code homology analysis and code cloning analysis on the code, and provides corresponding repair suggestions for detected security risks. S220: During the build phase, the security analysis engine and plug-ins provide a build platform security detection plug-in. When the project uses the build platform for continuous code integration and build testing, the build platform security detection plug-in automatically performs code homology analysis and code cloning analysis on the code to be tested, and provides corresponding repair suggestions for the detected security risks. S230: During the testing phase, the project conducts security testing and dynamic testing, and uses the security analysis engine and plug-ins to manually or automatically perform binary component analysis and binary homology analysis on the products submitted for testing, and provide corresponding repair suggestions for the detected security risks; S240: During the release phase, the security analysis engine and plug-ins provide a release platform security detection plug-in. When the project uses the release platform to build and release, the release platform security detection plug-in automatically performs binary component analysis and binary homology analysis on the products to be released, and provides corresponding repair suggestions for the detected security risks.
5. The method according to claim 4, characterized in that Dependency component analysis in S210 refers to the management of files based on the project object model, matching object models and detecting object sources through different rules, and then matching open source components, open source frameworks and vulnerability information through the detected object model based on the open source data knowledge base, and performing vulnerability risk assessment; Open source license analysis refers to matching the information of open source licenses and open source agreements by detecting object models based on the open source data knowledge base, and conducting closed source and illegal infringement risk assessments.
6. The method according to claim 4, characterized in that Code homology analysis in S210 and S220 refers to matching code snippets and code sources based on source code through different rules, and then matching open source components, open source frameworks and vulnerability information by detecting code snippets based on the open source data knowledge base, and performing vulnerability risk assessment; code clone analysis refers to matching code sources based on the compiled binary files by extracting bytecode feature values, input tables, output tables and disassembly, and then matching open source components, open source frameworks and vulnerability information by detecting code sources based on the open source data knowledge base, and performing vulnerability risk assessment.
7. The method according to claim 4, characterized in that The binary component analysis in S230 and S240 refers to extracting bytecode feature values, input tables, and output tables to match feature sources based on the compiled binary files, and then matching open source components, open source frameworks, and vulnerability information by detecting feature sources based on the open source data knowledge base, and performing vulnerability risk assessment; Binary homology analysis refers to matching code snippets and code sources through disassembly based on the compiled binary files, and then matching the information of open source components, open source frameworks and vulnerabilities by detecting code snippets based on the open source data knowledge base, and performing vulnerability risk assessment.
8. The method according to claim 4, characterized in that S300 specifically includes: automatically storing the open source and self-developed software components detected by the security analysis engine and plug-ins during the coding, building, testing and release stages into the asset library as assets, and automatically storing risk-free software products into the product warehouse.
9. The method according to claim 8, characterized in that The risk monitoring and alarm plug-in in S400 is used for asset and product monitoring and risk alarm. Asset and product monitoring obtains change information of assets and products through regular scanning. Risk alarm conducts vulnerability, closed source and illegal infringement risk assessment based on change information combined with matching open source components, open source frameworks, vulnerabilities, open source licenses, open source agreements and international political opinion information. When the risk exceeds the threshold, a real-time alarm is issued.
10. The software supply chain security governance system based on DevSecOps is characterized by: Including open source data processing module, engineering analysis management module, asset management module and risk warning module, The open source data processing module is used to collect open source data and establish an open source data knowledge base and an open source software security warehouse based on the open source data; The engineering analysis management module is used to scan the open source components and self-developed components of software products based on the security analysis engine and plug-ins, analyze the security risks of open source components, self-developed components and software products based on the open source data knowledge base, and generate repair suggestions; The asset management module is used to automatically store open source and self-developed software components as assets in the asset library, and automatically store risk-free software products in the product warehouse; The risk warning module uses risk monitoring and alarm plug-ins to automatically monitor the security risks and public opinion of assets in the asset library and products in the product warehouse, and issue vulnerability and license risk alarms, thereby achieving security management and control of the entire life cycle of software engineering.
