Aviation airborne software supply chain security risk detection system and method

Abstract

The invention belongs to the technical field of aviation airborne software supply chains, and relates to an aviation airborne software supply chain security risk detection system and method, and the system comprises a risk data collection module which is used for collecting risk data in a software supply chain; the vulnerability risk data analysis module is used for receiving data of a vulnerability risk data acquisition unit in the risk data acquisition module, analyzing and calculating vulnerability risk indexes and transmitting the vulnerability risk indexes to the overall risk analysis module; the component risk data analysis module is used for receiving data of a component risk data acquisition unit in the risk data acquisition module, analyzing and calculating a component risk index and transmitting the component risk index to the overall risk analysis module; the overall risk analysis module is used for receiving data of the vulnerability risk data analysis module and the component risk data analysis module, analyzing and calculating an overall risk index of the software supply chain and transmitting the overall risk index to the early warning module; the early warning module is used for receiving the data of the overall risk analysis module, carrying out judgment and early warning on the overall risk index and transmitting early warning results to the man-machine interaction module, and the early warning results include early warning needing and early warning not needing; and the man-machine interaction module is used for performing man-machine interaction display on the data

Description

Technical Field

[0001] The present invention belongs to the technical field of aviation airborne software supply chain, and relates to an aviation airborne software supply chain security risk detection system and method. Background Art

[0002] The aviation airborne software supply chain is a collection of software packages organized according to the calling relationship during the development or operation of the software system. In the ICT era, software is an important component and basis of enterprise applications and plays an increasingly important role. Once a software security risk occurs, it will affect the normal operation of the entire business system. For the software supply chain, there are many risk components, among which the most important source of risk is the software vulnerability risk. If there is a security vulnerability in a software product, it will have a serious impact on the system security involving the software product.

[0003] Software supply chain security vulnerabilities refer to security weaknesses or defects in the design, development or deployment process of the software itself, that is, vulnerabilities in the overall construction or design of the software, which may be exploited by attackers to cause system threats. Usually, they are detected and evaluated through static analysis, dynamic analysis, vulnerability scanning tools, code review and other technologies, with the aim of identifying software weaknesses and vulnerabilities that may be exploited, such as buffer overflows, code injections, logical vulnerabilities, etc.

[0004] Component vulnerabilities usually refer to security vulnerabilities or vulnerability risks in third-party components, libraries, or dependencies used in the software. These components are part of the entire software system. Component vulnerabilities usually need to rely on third-party vulnerability databases or specific component vulnerability detection tools to be discovered, such as various known vulnerabilities recorded in the CVE database.

[0005] Software supply chain security vulnerabilities differ from component vulnerabilities in the following ways:

[0006] 1. Different detection methods: Software security vulnerabilities are mainly detected by analyzing the software code or execution path, while component vulnerabilities usually rely on third-party vulnerability databases or specific component security assessment tools.

[0007] 2. Different repair responsibilities: The repair of software security vulnerabilities is usually the responsibility of the software developer, while the responsibility for repairing component vulnerabilities may be shared by the component provider or integrator.

[0008] 3. Different risk propagation: Component vulnerabilities may spread across multiple software projects, especially popular open source components, whose vulnerabilities may affect products in multiple software supply chains.

[0009] In practical applications, the security detection system of the software supply chain needs to comprehensively consider the security vulnerabilities of the software supply chain and component vulnerabilities to comprehensively assess the security risks of the software. By simultaneously detecting and analyzing overall vulnerabilities and component vulnerabilities, potential risks in the software supply chain can be effectively identified and repaired, thereby improving the overall security and reliability of the software system.

[0010] After searching, Chinese patent CN114077741B, relates to a method and device for supply chain security detection of aviation airborne software, electronic equipment and storage medium, wherein the method comprises: obtaining a binary file to be detected, extracting features to be analyzed of the binary file to be detected, the features to be analyzed include intra-function features, inter-function features and inter-module features; inputting the features to be analyzed into a feature vector generation model, outputting at least one feature vector to be analyzed corresponding to the binary file to be detected; obtaining the distance between each two vectors of at least one feature vector to be analyzed and at least one reference feature vector corresponding to the reference file, so as to obtain the similarity between the binary file to be detected and the reference file; based on the similarity, detecting the reuse relationship between the binary file to be detected and the reference file. The technical solution disclosed in this patent cannot detect whether the binary program reuses third-party code, code defects, associated vulnerabilities or malicious code and other supply chain security risks.

[0011] At present, most of the existing security risk detection systems for the software supply chain only detect software security vulnerabilities to determine whether the software has security risks, but do not measure the risks of components, and thus cannot discover high-risk components in the components. Summary of the invention

[0012] Purpose of the present invention: Most of the existing security risk detection systems for software supply chains only detect software security vulnerabilities to determine whether the software has security risks, but do not measure the risks of components, so they cannot discover high-risk components in the components.

[0013] In view of this, the present application proposes an aviation airborne software supply chain security risk detection system and method, which detects the risks of components while detecting software vulnerability risks, and then conducts comprehensive detection and analysis of various risks existing in the software supply chain. By measuring the risks of components, high-risk components in the components are discovered to achieve the purpose of correcting the risks of the components. By measuring the risks of the component structure network, the overall risk of the software is evaluated, the comprehensiveness of risk detection is improved, and the security of the software supply chain is increased.

[0014] Technical Solution

[0015] An aviation airborne software supply chain security risk detection system, comprising:

[0016] Risk data collection module: used to collect risk data in the software supply chain;

[0017] Vulnerability risk data analysis module: used to receive data from the vulnerability risk data collection unit in the risk data collection module, analyze and calculate the vulnerability risk index, and transmit it to the overall risk analysis module;

[0018] Component risk data analysis module: used to receive data from the component risk data collection unit in the risk data collection module, analyze and calculate the component risk index, and transmit it to the overall risk analysis module;

[0019] Overall risk analysis module: used to receive data from the vulnerability risk data analysis module and the component risk data analysis module, analyze and calculate the overall risk index of the software supply chain, and transmit it to the early warning module;

[0020] Early warning module: used to receive data from the overall risk analysis module, make a warning on the overall risk index, and transmit the warning result to the human-computer interaction module. The warning result is either "need warning" or "no warning";

[0021] Human-computer interaction module: used for human-computer interactive display of data.

[0022] Furthermore, the risk data collection module includes a vulnerability risk data collection unit and a component risk data collection unit; risk data includes vulnerability risk data and component risk data; the vulnerability risk data collection unit collects vulnerability risk data in the software supply chain based on CVE, and transmits it to the vulnerability risk data analysis module; vulnerability risk data includes the number of vulnerabilities, vulnerability risk value and vulnerability level; CVE is common vulnerabilities and exposures, which is a list of publicly known network security vulnerabilities and exposures. Each item in the list is based on a specific vulnerability or exposure found in a specific software product, and collects known network security vulnerabilities and exposures; the component risk data collection unit is used to collect component risk data in the software supply chain and transmit it to the component risk data analysis module; component risk data includes but is not limited to component attributes, nodes, edges and weights.

[0023] Furthermore, the component risk data analysis module includes a complexity analysis unit, a severity analysis unit, and a comprehensive analysis unit; the component risk index is a risk measurement index of the component;

[0024] The complexity analysis unit is used to analyze and calculate the complexity of the component and transmit it to the comprehensive analysis unit; the severity analysis unit is used to analyze and calculate the severity of the component and transmit it to the comprehensive analysis unit; the comprehensive analysis unit is used to receive data from the complexity analysis unit and the severity analysis unit, and perform comprehensive analysis and calculation on the component risk index.

[0025] Furthermore, the correspondence between the vulnerability risk value and the risk level in CVE is: when the vulnerability risk value score is 0 to 4, excluding 4, the vulnerability level is low; when the vulnerability risk value score is 4 to 7, excluding 7, the vulnerability level is medium; when the vulnerability risk value score is 7 to 10, the vulnerability level is high.

[0026] A method for analyzing and calculating a vulnerability risk index by a vulnerability risk data analysis module in an aviation airborne software supply chain security risk detection system.

[0027] The vulnerability risk data analysis module analyzes and calculates the vulnerability risk index using the following formula: Wherein, L is the vulnerability risk index, f(low) is the risk value of the low risk level, f(mid) is the risk value of the medium risk level, f(high) is the risk value of the high risk level, k1 is the proportional factor of f(low), k2 is the proportional factor of f(mid), k3 is the proportional factor of f(high), k1, k2 and k3 satisfy k1+k2+k3=1, and k1<k2<k3;

[0028] The calculation formula for the risk value of the low risk level is: Among them, x1 is the number of low-risk vulnerabilities, m1 is the highest risk value among low-risk vulnerabilities, and m1 satisfies 0≤m1<4;

[0029] The formula for calculating the risk value of the medium risk level is: Among them, x2 is the number of medium-risk vulnerabilities, m2 is the highest risk value among medium-risk vulnerabilities, and m2 satisfies 4≤m2<7;

[0030] The calculation formula for the high risk level risk value is: Among them, x3 is the number of high-risk vulnerabilities, m3 is the highest risk value among high-risk vulnerabilities, and m3 satisfies 7≤m3≤10.

[0031] A method for analyzing and calculating the complexity of a component by a complexity analysis unit in a component risk data analysis module in an aviation airborne software supply chain safety risk detection system. The specific process of analyzing and calculating the complexity of a component by the complexity analysis unit in the component risk data analysis module is as follows:

[0032] Step S01: Express the complexity of the component as an n-ary function expression: C = f(u1,u2,u3…u n ), where C is the complexity of the component, ui is the i-th attribute of the component, i = 1, 2, 3...n;

[0033] Step S02: Calculate the complexity of the jth component based on the Euclidean distance: Where Cj is the complexity of the jth component. If there are J components in total, then j = 1, 2, 3, ... J;

[0034] Simplifying formula ③ yields:

[0035] Step S03: Normalize formula ④ to obtain a new formula: Where Cj is the complexity of the jth component. If there are J components in total, Cmax is the maximum complexity of the J components of the software, and Cmin is the minimum complexity of the J components of the software.

[0036] The complexity of a component is a measure of the complexity of the reference relationships between its components. A basic simple component is a component with no components and no reference relationships. Its complexity is 0, and all indicators of the basic simple component are 0. This component is the origin of the indicator system. Therefore, the complexity of the component can be calculated by calculating the Euclidean distance from the basic simple component. The farther away from the basic simple component, that is, the larger the Euclidean distance calculation value, the higher the complexity of the component.

[0037] A method for analyzing and calculating the severity of a component by a severity analysis unit in a component risk data analysis module in an aviation airborne software supply chain safety risk detection system. The formula for analyzing and calculating the severity of a component by the severity analysis unit in the component risk data analysis module is: Where Yj is the severity of the jth component. If there are J components in total, then j = 1, 2, 3, ... J. E(G) is the average network efficiency of the software topology network under normal conditions. Assuming that component j fails, the average network efficiency of the software topology network of the failed network under the premise of component j failure is E(Gj).

[0038] If the network topology of the software contains three basic elements, namely nodes R, edges T and weights P, then the software topology network can be expressed as G = (R, T, P). Therefore, for a network containing N nodes, the connection matrix [Vab] N*N can be used to describe G;

[0039] Therefore, G = [Vab]N*N; where Vab is the strength of the relationship between the ath node and the bth node, and the strength between nodes refers to the sum of the weights of the edges connected to the nodes;

[0040] N is the total number of nodes in the software topology network of the failed network under the premise that component j fails, and Vab′ is the strength of the relationship between the ath node and the bth node in the software topology network of the failed network.

[0041] A method for comprehensively analyzing and calculating component risk indexes by a comprehensive analysis unit in an aviation airborne software supply chain safety risk detection system. The formula for comprehensively analyzing and calculating component risk indexes by the comprehensive analysis unit is: Where Z′ is the component risk index. If there are J components in total, then j = 1, 2, 3, ... J; Z j =C j *Y j , where Zj is the risk index of component j, 0≤Cj≤1, 0≤Yj≤1.

[0042] A method for calculating an overall risk index by an overall risk analysis module in an aviation airborne software supply chain safety risk detection system. The formula for calculating the overall risk index by the overall risk analysis module is: Among them, δ is the overall risk index; the larger the value of the overall risk index δ is, the higher the overall risk coefficient of the software supply chain is and the lower the security is.

[0043] A method for calculating the overall risk index by an overall risk analysis module in an aviation airborne software supply chain safety risk detection system.

[0044] The specific process of the early warning module to determine and warn the overall risk index is as follows:

[0045] Step S11: If the overall risk index δ ≥ the judgment threshold IY, it is determined that an early warning is required, and at this time, data is transmitted to the human-computer interaction module and an early warning instruction is sent to the management personnel;

[0046] Step S12: If the overall risk index δ is less than the judgment threshold IY, it is determined that no warning is needed. At this time, only data is transmitted to the human-computer interaction module, and no warning instruction is sent to the management personnel;

[0047] The value of the determination threshold IY satisfies IY≤20%.

[0048] Beneficial Effects

[0049] The present invention proposes an aviation airborne software supply chain security risk detection system and method, which are conducive to analyzing and calculating the vulnerability risk index and the component risk index, obtaining the final component risk index by comparing and analyzing the complexity and severity of the components, and conducting a combined analysis of the vulnerability risk and the component risk, thereby laying a foundation for the subsequent overall risk analysis of the software supply chain. At the same time, while detecting the software vulnerability risk, the component risk is also detected, and then the various risks existing in the software supply chain are comprehensively detected and analyzed. By measuring the risk of the component, the high risk existing in the component is discovered, so as to achieve the purpose of correcting the risk of the component, and the overall risk of the software is evaluated by measuring the risk of the component structure network, thereby improving the comprehensiveness of risk detection and increasing the security of the software supply chain. DETAILED DESCRIPTION

[0050] The features and illustrative embodiments of various aspects of the present invention will be described in detail below. In the detailed description below, many specific details are proposed to provide a comprehensive understanding of the present invention. However, it is obvious to those skilled in the art that the present invention can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present invention by illustrating examples of the present invention. The present invention is by no means limited to any specific settings and methods proposed below, but covers any improvements, replacements and modifications of structures, methods, devices without departing from the spirit of the present invention. In the following description, known structures and technologies are not shown to avoid unnecessary ambiguity in the present invention.

[0051] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other, and the embodiments can refer to and quote each other. The present invention will be described in detail below in conjunction with the embodiments.

[0052] Embodiment 1:

[0053] Provide an aviation airborne software supply chain security risk detection system, including a risk data acquisition module, a vulnerability risk data analysis module, a component risk data analysis module, an overall risk analysis module, an early warning module, and a human-computer interaction module;

[0054] The risk data collection module is used to collect risk data in the software supply chain. The risk data collection module includes a vulnerability risk data collection unit and a component risk data collection unit. Risk data includes vulnerability risk data and component risk data. The vulnerability risk data collection unit collects vulnerability risk data in the software supply chain based on CVE and transmits it to the vulnerability risk data analysis module. Vulnerability risk data includes the number of vulnerabilities, vulnerability risk value and vulnerability level. CVE stands for Common Vulnerability and Exposures, which is a list of publicly known network security vulnerabilities and exposures. Each item in the list is based on a specific vulnerability or exposure found in a specific software product, and collects known network security vulnerabilities and exposures. The component risk data collection unit is used to collect component risk data in the software supply chain and transmit it to the component risk data analysis module. Component risk data includes but is not limited to component attributes, nodes, edges and weights.

[0055] The vulnerability risk data analysis module is used to receive data from the vulnerability risk data collection unit in the risk data collection module, analyze and calculate the vulnerability risk index, and transmit it to the overall risk analysis module;

[0056] The component risk data analysis module is used to receive data from the component risk data collection unit in the risk data collection module, analyze and calculate the component risk index, and transmit it to the overall risk analysis module; the component risk data analysis module includes a complexity analysis unit, a severity analysis unit and a comprehensive analysis unit; the component risk index is a risk measurement index of the component;

[0057] The complexity analysis unit is used to analyze and calculate the complexity of the components and transmit the results to the comprehensive analysis unit;

[0058] The severity analysis unit is used to analyze and calculate the severity of the component and transmit it to the comprehensive analysis unit;

[0059] The comprehensive analysis unit is used to receive data from the complexity analysis unit and the severity analysis unit, and perform comprehensive analysis and calculation on the component risk index;

[0060] The overall risk analysis module is used to receive data from the vulnerability risk data analysis module and the component risk data analysis module, analyze and calculate the overall risk index of the software supply chain, and transmit it to the early warning module;

[0061] The early warning module is used to receive data from the overall risk analysis module, make a judgment and early warning on the overall risk index, and transmit the early warning result to the human-computer interaction module; the early warning result is divided into two types: early warning is needed and no early warning is needed;

[0062] The human-computer interaction module is used to display data in a human-computer interactive manner.

[0063] The correspondence between the vulnerability risk value and risk level in CVE is: when the vulnerability risk value score is 0 to 4 (excluding 4), the vulnerability level is low; when the vulnerability risk value score is 4 to 7 (excluding 7), the vulnerability level is medium; when the vulnerability risk value score is 7 to 10, the vulnerability level is high.

[0064] The vulnerability risk data analysis module analyzes and calculates the vulnerability risk index using the following formula: Wherein, L is the vulnerability risk index, f(low) is the risk value of the low risk level, f(mid) is the risk value of the medium risk level, f(high) is the risk value of the high risk level, k1 is the proportional factor of f(low), k2 is the proportional factor of f(mid), k3 is the proportional factor of f(high), k1, k2 and k3 satisfy k1+k2+k3=1, and k1<k2<k3;

[0065] The calculation formula for the risk value of the low risk level is: Among them, x1 is the number of low-risk vulnerabilities, m1 is the highest risk value among low-risk vulnerabilities, and m1 satisfies 0≤m1<4;

[0066] The formula for calculating the risk value of the medium risk level is: Among them, x2 is the number of medium-risk vulnerabilities, m2 is the highest risk value among medium-risk vulnerabilities, and m2 satisfies 4≤m2<7;

[0067] The calculation formula for the high risk level risk value is: Among them, x3 is the number of high-risk vulnerabilities, m3 is the highest risk value among high-risk vulnerabilities, and m3 satisfies 7≤m3≤10.

[0068] The calculation formulas for the low-risk level risk value, medium-risk level risk value, and high-risk level risk value are all derived from the Sigmoid function. The Sigmoid function takes values ​​from 0.5 to 1 infinitely as x approaches infinity from 0. The range of its x value does not conform to the actual vulnerability risk situation. In the actual vulnerability risk analysis, when x = 0, it means that there is no vulnerability in the system, and the risk value is 0 at this time. Therefore, it is necessary to move the Sigmoid function curve to change the function value when x = 0 to 0. The formula is: At this time, the value range of the function value S1(x) is 0 and infinitely close to 0.5. In order to facilitate the calculation of the vulnerability, the formula value is multiplied by 2 to round it up, and formula ① becomes: At this time, the value range of the function value S2(x) is from 0 to 1. According to the principle that the vulnerability risk value is not lower than the risk value of the highest risk vulnerability and does not exceed the current interval, the value range of S2(x) needs to be expanded. Therefore, the m value is introduced, and m is the highest risk value among the vulnerabilities existing in the current software.

[0069] The specific process of the complexity analysis unit in the component risk data analysis module to analyze and calculate the complexity of the component is as follows:

[0070] Step S01: Express the complexity of the component as an n-ary function expression: C = f(u1,u2,u3…u n ), where C is the complexity of the component, ui is the i-th attribute of the component, i = 1, 2, 3...n;

[0071] Step S02: Calculate the complexity of the jth component based on the Euclidean distance: Where Cj is the complexity of the jth component. If there are J components in total, then j = 1, 2, 3, ... J;

[0072] Simplifying formula ③ yields:

[0073] Step S03: Normalize formula ④ to obtain a new formula: Where Cj is the complexity of the jth component. If there are J components in total, Cmax is the maximum complexity of the J components of the software, and Cmin is the minimum complexity of the J components of the software.

[0074] The complexity of a component is the degree of complexity of the reference relationship between the components of the component. A basic simple component refers to a component without components and reference relationships. Its complexity is 0. All indicators of the basic simple component are 0. This component is the origin of the indicator system. Therefore, the complexity of the component can be calculated by calculating the Euclidean distance from the basic simple component. The farther away from the basic simple component, that is, the larger the Euclidean distance calculation value, the higher the complexity of the component.

[0075] Exemplarily, the components of a component can be the source code files of the component and the functions therein. The complexity of the component can be measured by attributes such as the number and size of the source code files, the number of functions included, and the number of lines of functions included. The complexity of the reference relationship between components can be measured by the mutual calling relationship between the functions included in the source code files and between the source code files.

[0076] The formula used by the severity analysis unit in the component risk data analysis module to analyze and calculate the severity of the component is: Where Yj is the severity of the jth component. If there are J components in total, then j = 1, 2, 3, ... J. E(G) is the average network efficiency of the software topology network under normal conditions. Assuming that component j fails, the average network efficiency of the software topology network of the failed network under the premise of component j failure is E(Gj).

[0077] If the network topology of the software contains three basic elements, namely nodes R, edges T and weights P, then the software topology network can be expressed as G = (R, T, P). Therefore, for a network containing N nodes, the connection matrix [Vab] N*N can be used to describe G;

[0078] Therefore, G = [Vab]N*N; where Vab is the strength of the relationship between the ath node and the bth node, and the strength between nodes refers to the sum of the weights of the edges connected to the nodes;

[0079] N is the total number of nodes in the software topology network of the failed network under the premise that component j fails, and Vab′ is the strength of the relationship between the ath node and the bth node in the software topology network of the failed network.

[0080] The formula for the comprehensive analysis unit to conduct comprehensive analysis and calculation of the component risk index is: Where Z′ is the component risk index. If there are J components in total, then j = 1, 2, 3, ... J; Zj =C j *Y j , where Zj is the risk index of component j, 0≤Cj≤1, 0≤Yj≤1.

[0081] The formula used by the overall risk analysis module to calculate the overall risk index is: Among them, δ is the overall risk index; the larger the value of the overall risk index δ is, the higher the overall risk coefficient of the software supply chain is and the lower the security is.

[0082] The specific process of the early warning module to determine and warn the overall risk index is as follows:

[0083] Step S11: If the overall risk index δ ≥ the judgment threshold IY, it is determined that an early warning is required, and at this time, data is transmitted to the human-computer interaction module and an early warning instruction is sent to the management personnel;

[0084] Step S12: If the overall risk index δ is less than the judgment threshold IY, it is determined that no warning is needed. At this time, only data is transmitted to the human-computer interaction module, and no warning instruction is sent to the management personnel;

[0085] The value of the determination threshold IY satisfies IY≤20%.

[0086] The present invention is provided with a vulnerability risk data analysis module and a component risk data analysis module, which is conducive to analyzing and calculating the vulnerability risk index and the component risk index. The final component risk index is obtained by comparing and analyzing the complexity and severity of the components, and the vulnerability risk and component risk are combined for analysis, which lays a foundation for the subsequent overall risk analysis of the software supply chain. At the same time, while detecting the software vulnerability risk, the component risk is also detected, and then the various risks existing in the software supply chain are comprehensively detected and analyzed. By measuring the risk of the component, the high risk of the component is found, so as to achieve the purpose of correcting the risk of the component. The overall risk of the software is evaluated by measuring the risk of the component structure network, which improves the comprehensiveness of risk detection and increases the security of the software supply chain.

[0087] Embodiment 2:

[0088] The method steps for using a software supply chain security risk detection system are as follows:

[0089] Step A1: Collect risk data in the software supply chain, including vulnerability risk data and component risk data;

[0090] Step A2: Calculate the risk value of the low risk level, the risk value of the medium risk level, and the risk value of the high risk level, and analyze and calculate the vulnerability risk index by combining the risk value of the low risk level, the risk value of the medium risk level, and the risk value of the high risk level;

[0091] Step A3: The complexity of the component is expressed in the form of an n-variable function, the complexity is calculated based on the Euclidean distance and normalized, and the severity of the component is analyzed and calculated using the formula, and then the component risk index is analyzed and calculated based on the complexity and severity using the formula;

[0092] The formula for analyzing and calculating the severity of a component is: Where Yj is the severity of the jth component. If there are J components in total, then j = 1, 2, 3, ... J. E(G) is the average network efficiency of the software topology network under normal conditions. Assuming that component j fails, the average network efficiency of the software topology network of the failed network under the premise of component j failure is E(Gj).

[0093] If the network topology of the software contains three basic elements, namely nodes R, edges T and weights P, then the software topology network can be expressed as G = (R, T, P). Therefore, for a network containing N nodes, the connection matrix [Vab] N*N can be used to describe G;

[0094] Therefore, G = [Vab]N*N; where Vab is the strength of the relationship between the ath node and the bth node, and the strength between nodes refers to the sum of the weights of the edges connected to the nodes;

[0095] N is the total number of nodes in the software topology network of the failed network under the premise that component j fails, Vab′ is the strength of the relationship between the ath node and the bth node in the software topology network of the failed network;

[0096] The formula for comprehensive analysis and calculation of component risk index is: Where Z′ is the component risk index. If there are J components in total, then j = 1, 2, 3, ... J; Z j =C j *Y j , where Zj is the risk index of component j, 0≤Cj≤1, 0≤Yj≤1;

[0097] Step A4: Analyze and calculate the overall risk index of the software supply chain using the formula;

[0098] Among them, δ is the overall risk index; the larger the value of the overall risk index δ is, the higher the overall risk coefficient of the software supply chain is and the lower the security is;

[0099] Step A5: Determine and warn the overall risk index. If the overall risk index is greater than or equal to the determination threshold, it is determined that a warning is required. If the overall risk index is less than the determination threshold, it is determined that no warning is required.

[0100] In summary, the system and method of the present invention have the following characteristics:

[0101] 1. The vulnerability risk data analysis module calculates the vulnerability risk index from three perspectives: low risk, medium risk, and high risk. It conducts a comprehensive detection and analysis of software vulnerability risks, increases the comprehensiveness of vulnerability risk detection, improves the accuracy of vulnerability risk detection, and lays the foundation for subsequent overall risk analysis of the software supply chain.

[0102] 2. The component risk data analysis module calculates the complexity and severity of the components, and obtains the final component risk index by comparing and analyzing the complexity and severity of the components. By measuring the risk of the components, the high risks in the components are discovered, and the purpose of correcting the risk of the components is achieved, laying the foundation for the subsequent overall risk analysis of the software supply chain.

[0103] 3. Combine vulnerability risk and component risk for analysis. While testing software vulnerability risk, component risk is also tested, and then various risks existing in the software supply chain are comprehensively tested and analyzed, which improves the comprehensiveness of risk detection and increases the security of the software supply chain.

[0104] The difference between the present invention and the prior art and the significance of the invention

[0105] 1. The difference between the present invention and the prior art:

[0106] The difference between the present invention and the prior art is that the prior art security risk detection systems for software supply chains mostly only detect software security vulnerabilities to determine whether the software has security risks, but do not measure the risks of components, thereby failing to discover high-risk components in the components. Therefore, the comprehensiveness of the security risk detection process for the software supply chain needs to be improved. However, in the process of detecting the security risks of the software supply chain, the present invention not only detects the vulnerability risks of the software, but also measures the risk factors existing in the components, comprehensively considers and analyzes the risk situation of the software supply chain from the perspective of software security vulnerabilities and component risks, thereby improving the comprehensiveness of the software supply chain risk analysis.

[0107] 2. Significance of the invention:

[0108] The present invention takes component risk factors into consideration when analyzing software supply chain risks, and further conducts a comprehensive analysis based on the complexity and severity of the components to obtain a risk index for the component risk factors. By combining the risks of security vulnerabilities with component risks to conduct a comprehensive analysis of the risks of the software supply chain, the comprehensiveness of the software supply chain risk analysis is improved, making the analysis results of the software supply chain risk more accurate.

[0109] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the field can easily think of various equivalent modifications or substitutions within the technical scope disclosed by the present invention, and these modifications or substitutions should all be covered within the protection scope of the present invention.

Claims

1. An aviation airborne software supply chain security risk detection system, characterized in that: include: Risk data collection module: used to collect risk data in the software supply chain; Vulnerability risk data analysis module: used to receive data from the vulnerability risk data collection unit in the risk data collection module, analyze and calculate the vulnerability risk index, and transmit it to the overall risk analysis module; Component risk data analysis module: used to receive data from the component risk data collection unit in the risk data collection module, analyze and calculate the component risk index, and transmit it to the overall risk analysis module; Overall risk analysis module: used to receive data from the vulnerability risk data analysis module and the component risk data analysis module, analyze and calculate the overall risk index of the software supply chain, and transmit it to the early warning module; Early warning module: used to receive data from the overall risk analysis module, make a warning on the overall risk index, and transmit the warning result to the human-computer interaction module. The warning result is either "need warning" or "no warning"; Human-computer interaction module: used for human-computer interactive display of data.

2. The aviation airborne software supply chain security risk detection system according to claim 1 is characterized in that: The risk data collection module includes a vulnerability risk data collection unit and a component risk data collection unit; risk data includes vulnerability risk data and component risk data; the vulnerability risk data collection unit collects vulnerability risk data in the software supply chain based on CVE and transmits it to the vulnerability risk data analysis module; vulnerability risk data includes the number of vulnerabilities, vulnerability risk value and vulnerability level; CVE stands for common vulnerabilities and exposures, which is a list of publicly known network security vulnerabilities and exposures. Each item in the list is based on a specific vulnerability or exposure found in a specific software product, and collects known network security vulnerabilities and exposures; the component risk data collection unit is used to collect component risk data in the software supply chain and transmit it to the component risk data analysis module; component risk data includes but is not limited to component attributes, nodes, edges and weights.

3. The aviation airborne software supply chain security risk detection system according to claim 2 is characterized in that: The component risk data analysis module includes a complexity analysis unit, a severity analysis unit, and a comprehensive analysis unit; the component risk index is a risk measurement index of the component; The complexity analysis unit is used to analyze and calculate the complexity of the component and transmit it to the comprehensive analysis unit; the severity analysis unit is used to analyze and calculate the severity of the component and transmit it to the comprehensive analysis unit; the comprehensive analysis unit is used to receive data from the complexity analysis unit and the severity analysis unit, and perform comprehensive analysis and calculation on the component risk index.

4. The aviation airborne software supply chain security risk detection system according to claim 2 is characterized in that: The correspondence between the vulnerability risk value and risk level in CVE is: when the vulnerability risk value score is 0 to 4, excluding 4, the vulnerability level is low; when the vulnerability risk value score is 4 to 7, excluding 7, the vulnerability level is medium; when the vulnerability risk value score is 7 to 10, the vulnerability level is high.

5. A method for analyzing and calculating the vulnerability risk index by a vulnerability risk data analysis module in the aviation airborne software supply chain security risk detection system as described in any one of claims 1 to 4, characterized in that: The vulnerability risk data analysis module analyzes and calculates the vulnerability risk index using the following formula: Wherein, L is the vulnerability risk index, f(low) is the risk value of the low risk level, f(mid) is the risk value of the medium risk level, f(high) is the risk value of the high risk level, k1 is the proportional factor of f(low), k2 is the proportional factor of f(mid), k3 is the proportional factor of f(high), k1, k2 and k3 satisfy k1+k2+k3=1, and k1<k2<k3; The calculation formula for the risk value of the low risk level is: Among them, x1 is the number of low-risk vulnerabilities, m1 is the highest risk value among low-risk vulnerabilities, and m1 satisfies 0≤m1<4; The formula for calculating the risk value of the medium risk level is: Among them, x2 is the number of medium-risk vulnerabilities, m2 is the highest risk value among medium-risk vulnerabilities, and m2 satisfies 4≤m2<7; The calculation formula for the high risk level risk value is: Among them, x3 is the number of high-risk vulnerabilities, m3 is the highest risk value among high-risk vulnerabilities, and m3 satisfies 7≤m3≤10.

6. A method for analyzing and calculating the complexity of a component by a complexity analysis unit in a component risk data analysis module in an aviation airborne software supply chain safety risk detection system as claimed in claim 5, characterized in that: The specific process of the complexity analysis unit in the component risk data analysis module to analyze and calculate the complexity of the component is as follows: Step S01: Express the complexity of the component as an n-ary function expression: C = f(u1,u2,u3…u n ), where C is the complexity of the component, ui is the i-th attribute of the component, i = 1, 2, 3...n; Step S02: Calculate the complexity of the jth component based on the Euclidean distance: Where Cj is the complexity of the jth component. If there are J components in total, then j = 1, 2, 3, ... J; Simplifying formula ③ yields: Step S03: Normalize formula ④ to obtain a new formula: Where Cj is the complexity of the jth component. If there are J components in total, Cmax is the maximum complexity of the J components of the software, and Cmin is the minimum complexity of the J components of the software. The complexity of a component is a measure of the complexity of the reference relationships between its components. A basic simple component is a component with no components and no reference relationships. Its complexity is 0, and all indicators of the basic simple component are 0. This component is the origin of the indicator system. Therefore, the complexity of the component can be calculated by calculating the Euclidean distance from the basic simple component. The farther away from the basic simple component, that is, the larger the Euclidean distance calculation value, the higher the complexity of the component.

7. A method for analyzing and calculating the severity of a component by a severity analysis unit in a component risk data analysis module in an aviation airborne software supply chain safety risk detection system as claimed in claim 6, characterized in that: The formula used by the severity analysis unit in the component risk data analysis module to analyze and calculate the severity of the component is: Where Yj is the severity of the jth component. If there are J components in total, then j = 1, 2, 3, ... J. E(G) is the average network efficiency of the software topology network under normal conditions. Assuming that component j fails, the average network efficiency of the software topology network of the failed network under the premise of component j failure is E(Gj). If the network topology of the software contains three basic elements, namely nodes R, edges T and weights P, then the software topology network can be expressed as G = (R, T, P). Therefore, for a network containing N nodes, the connection matrix [Vab] N*N can be used to describe G; Therefore, G = [Vab]N*N; where Vab is the strength of the relationship between the ath node and the bth node, and the strength between nodes refers to the sum of the weights of the edges connected to the nodes; N is the total number of nodes in the software topology network of the failed network under the premise that component j fails, and Vab′ is the strength of the relationship between the ath node and the bth node in the software topology network of the failed network.

8. A method for performing comprehensive analysis and calculation on component risk index by a comprehensive analysis unit in the aviation airborne software supply chain security risk detection system as claimed in claim 7, characterized in that: The formula for the comprehensive analysis unit to conduct comprehensive analysis and calculation of the component risk index is: Where Z′ is the component risk index. If there are J components in total, then j = 1, 2, 3, ... J; Z j =C j *Y j , where Zj is the risk index of component j, 0≤Cj≤1, 0≤Yj≤1.

9. A method for calculating the overall risk index by the overall risk analysis module in the aviation airborne software supply chain security risk detection system as claimed in claim 8, characterized in that: The formula used by the overall risk analysis module to calculate the overall risk index is: Among them, δ is the overall risk index; the larger the value of the overall risk index δ is, the higher the overall risk coefficient of the software supply chain is and the lower the security is.

10. A method for calculating the overall risk index by the overall risk analysis module in the aviation airborne software supply chain security risk detection system as claimed in claim 9, characterized in that: The specific process of the early warning module to determine and warn the overall risk index is as follows: Step S11: If the overall risk index δ ≥ the judgment threshold IY, it is determined that an early warning is required, and at this time, data is transmitted to the human-computer interaction module and an early warning instruction is sent to the management personnel; Step S12: If the overall risk index δ is less than the judgment threshold IY, it is determined that no warning is needed. At this time, only data is transmitted to the human-computer interaction module, and no warning instruction is sent to the management personnel; The value of the determination threshold IY satisfies IY≤20%.

Images