Software gene-based power system software security detection method and device
By comparing the software genes and preset libraries and judging their call data types, the problem of high false alarm rate in software security detection is solved, the detection efficiency is improved and the false alarm rate is reduced, and the data update of the software gene library is enhanced and Accuracy of subsequent testing.
Patent Information
- Application Number
- CN202411104500.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-13
- Publication Date
- 2024-11-08
AI Technical Summary
In the prior art, the false alarm rate of software genes is high when used for software security detection, and the specific functions of the software cannot be effectively identified, resulting in low detection efficiency and high false alarm rate.
By obtaining the software genes of the software to be detected and comparing them with the preset software gene database, we determine whether the software gene calls irrelevant data, determine whether there is a safety hazard, and configure the software genes with safety hazards in the software gene database, and update the gene database to Improve subsequent testing efficiency.
It reduces the false alarm rate of software security detection, improves detection efficiency, and ensures the update of software gene database data and the accuracy of subsequent detection.
Smart Images

Figure CN118916885A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of software security detection, and in particular to a method and device for detecting software security of a power system based on software genes. Background Art
[0002] Software is the basic component for building power system information. The existence of security vulnerabilities and undeclared functions (backdoors) in software is the root cause of frequent security incidents. With the rapid advancement of the digital transformation of the power grid and the in-depth application of new technologies such as "cloud, big data, Internet of Things, mobile and intelligence", the exposure of new power systems based on new energy is expanding, and in terms of network security, they will face inherent risks such as network integration, transmission security, and vulnerabilities. Source code security testing before the information system goes online has become an important means to ensure the inherent safety of the system. With the continuous evolution of development models and changes in information security trends, traditional source code detection technology can no longer meet the needs of rapid and secure launch of information systems.
[0003] Software genes are binary fragments with functions or information on the software body. The concept is inspired by biological genes and has strong association analysis and homology discrimination capabilities. Unlike traditional feature detection technology, software gene detection technology can effectively reveal the essential connections and laws between carrier structures, transmission pathways, and information carried. It can not only identify target samples, but also analyze other potential samples that are similar or homologous to target samples, realize association mining and exploration of derived evolutionary laws, discover software defects from a microscopic perspective, and effectively make up for the deficiencies of static analysis technology from a macroscopic perspective in false positive and false negative rates. Therefore, conducting research on software gene security detection technology, discovering security defects from the software gene level, and improving the means and accuracy of information system security code security detection are of great significance for supporting information system pre-online security detection and improving the quality and security level of power enterprise information system code.
[0004] However, in the prior art, when software genes are used to perform security testing on software, the false positive rate is high because the specific functions of the software cannot be effectively identified based on the software genes. Summary of the invention
[0005] The present invention provides a software gene-based power system software safety detection method and device to solve the problem of high false alarm rate of software safety detection methods in the prior art.
[0006] In a first aspect, the present invention provides a method for detecting power system software security based on software genes, comprising: Obtaining software genes of the software to be tested; Comparing the obtained software gene with the preset software gene in the software gene library; When the software gene is consistent with the preset software gene, it is determined that the software gene has a security risk; When the software gene is inconsistent with the preset software gene, determining the data called by the software gene; Determining whether the software gene has a security risk according to whether the software gene calls irrelevant data; When the software gene does not have any potential safety hazard, the detection of the software gene is terminated; When the software gene has a potential safety hazard, the software gene is configured in a software gene library and the software gene is marked.
[0007] In a possible implementation, after determining the data of the software gene call, the method further includes: If the software gene has no call data, it is determined that the software gene does not have any security risks.
[0008] In a possible implementation, determining whether the software gene has a security risk according to whether the software gene calls irrelevant data includes: If the software gene has call data, determine the source of the data called by the software gene; Whether the software gene has a security risk is determined based on whether the software gene calls an irrelevant data source.
[0009] In a possible implementation, determining whether the software gene has a security risk according to whether the software gene calls an irrelevant data source includes: Get the data source types that are manually classified in advance; Determining the data source type of the software gene call based on the data source type manually classified in advance; Based on the correlation between different data source types and software genes, as well as the data source type called by the software gene, it is determined whether the software gene has security risks.
[0010] In a possible implementation, obtaining the software gene of the software to be detected includes: Get the software to be tested; The code of the software to be detected is fragmented to obtain the software gene.
[0011] In a possible implementation manner, the software gene includes a software code for implementing at least one function.
[0012] In a possible implementation, there are multiple software gene libraries; each software gene library corresponds to a type of software; accordingly, comparing the acquired software gene with a preset software gene in the software gene library includes: Determining the type of the software to be detected; According to the type of the software to be detected, determining a software gene library corresponding to the software type; The obtained software gene is compared with a preset software gene in a software gene library corresponding to the software type to obtain a comparison result.
[0013] In a possible implementation manner, determining the type of the software to be detected includes: The type of the software to be detected is determined by pre-manual classification, and the determined software type is identified as identification data.
[0014] In a possible implementation manner, the identifying the software gene includes: identifying the software gene according to the type of the software gene.
[0015] In a second aspect, the present invention provides a power system software safety detection device based on software genes, comprising: An acquisition module, used to acquire the software gene of the software to be detected; A comparison module, used for comparing the acquired software gene with a preset software gene in a software gene library; A first safety determination module, configured to determine that the software gene has a safety hazard when the software gene is consistent with a preset software gene; A data determination module, used for determining the data called by the software gene when the software gene is inconsistent with the preset software gene; A second safety determination module, used to determine whether the software gene has a safety hazard according to whether the software gene calls irrelevant data; A detection end module, used for ending the detection of the software gene when there is no potential safety hazard in the software gene; The software gene library update module is used to configure the software gene in the software gene library and mark the software gene when there is a potential safety hazard in the software gene.
[0016] Compared with the prior art, the present invention has the following advantages: 1. The present invention determines whether the software gene has a safety hazard based on the data called by the software gene. During the power system software safety detection process, it can be conveniently determined whether the software gene calls irrelevant data based on the data type called by the software gene, thereby better determining whether the software has a safety hazard and reducing the false alarm rate.
[0017] 2. The present invention can quickly determine whether the software has security risks by comparing the software gene with the preset software gene in the preset software gene library. When the preset software gene is consistent with the software gene, it means that the software has security risks, which improves the software detection efficiency and helps to reduce the false alarm rate.
[0018] 3. When the software gene of the present invention has potential safety hazards, the software gene is configured in the software gene library, which increases the data in the software gene library and can effectively improve the detection efficiency of the software and reduce the false alarm rate in the subsequent detection process. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0020] Figure 1 This is an application scenario diagram of the power system software safety detection method based on software genes provided by an embodiment of the present invention; Figure 2 It is a flow chart of the implementation of the power system software safety detection method based on software gene provided by an embodiment of the present invention; Figure 3 It is a structural schematic diagram of a power system software safety detection device based on software genes provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0021] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present invention. However, it should be clear to those skilled in the art that the present invention may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present invention.
[0022] In order to make the purpose, technical solutions and advantages of the present invention more clear, specific embodiments will be described below in conjunction with the accompanying drawings.
[0023] Figure 1 The application scenario diagram of the power system software security detection method based on software gene provided by the embodiment of the present invention. The embodiment of the present invention can be applied to a variety of application scenarios, which involve power system software security detection. The specific application scenarios are not limited here. For example, refer to Figure 1,In an application scenario, the power system software to be tested can be input in a variety of ways, and the ,security detection method can be executed on the server side based on the ,software gene library to determine whether there are security risks in the power ,system software.
[0024] The embodiment of the present invention provides a power system software safety detection method based on software genes, which first performs safety detection through a preset software gene library, then calls data on the software gene detection for which no safety hazards are detected, and then determines whether there are safety hazards in the power system software.
[0025] Figure 2 The implementation flow chart of the power system software safety detection method based on software gene provided by the embodiment of the present invention is described in detail as follows: Step 201, obtaining the software gene of the software to be detected; Step 202, comparing the acquired software gene with a preset software gene in a software gene library; Step 203, when the software gene is consistent with the preset software gene, it is determined that the software gene has a security risk; Step 204, when the software gene is inconsistent with the preset software gene, determining the data called by the software gene; Step 205, determining whether the software gene has a security risk according to whether the software gene calls irrelevant data; Step 206, when the software gene does not have any potential safety hazard, the detection of the software gene is terminated; Step 207: When the software gene has a potential safety hazard, the software gene is configured in a software gene library and the software gene is marked.
[0026] Usually, software with different functions calls different types of data. Taking the software for monitoring the power system as an example, the software for monitoring the power system only needs the monitoring function. The data types it calls are usually various parameters when the power system is running, and other types of data are not involved, such as statistical data, etc.
[0027] Therefore, the called data can effectively identify whether the software has security risks. For example, when the software for monitoring the power system needs to call statistical data, it can be directly determined that the software has security risks.
[0028] Therefore, when conducting software security testing, it is determined whether the software has security risks based on the data of the software gene call, which greatly improves the accuracy of software security testing and can effectively reduce the false alarm rate.
[0029] Specifically, software genes based on source code pointing analysis determine whether different memory references in the program source code point to the same memory area, determine the object or storage location pointed to by a pointer, calculate the reachable boundaries of variables, and judge the variables and objects affected by statements and pointers during the compilation process. This realizes association mining and exploration of derivative evolution laws, discovers software security defects more comprehensively, and effectively reduces the missed reporting rate of security detection.
[0030] After the source code is compiled, the detectable program execution path that is homologous to the target sample is analyzed. According to the function call relationship, control flow information, variable alias information, pointer information, data dependency relationship and interface information generated after compilation, defect identification based on homology detection is realized, which effectively reduces the false alarm rate and improves the efficiency of software security defect detection.
[0031] The sample library to be tested is decompiled into assembly code to be sliced and extracted, and segmented into gene fragments with certain functional characteristics according to the lexical, grammatical, semantic, functional and calling relationships in the assembly code. The gene attribute vector is marked, and an assembly-based semantic slicing segmentation model that does not rely on software gene libraries is established to solve the problem of low gene recognition accuracy due to the inability to deploy offline due to continuous updating of the gene library and malicious program changes.
[0032] The research on key technologies for genetic security detection of software in information systems of power enterprises first focuses on typical application scenarios of code security detection before information systems go online, develops software genetic evolution detection technology based on source code pointing analysis, and optimizes security detection methods before source code compilation.
[0033] On this basis, we carry out research on software gene evolution detection technology based on source code pointing analysis, and realize defect identification based on homology detection according to the function call relationship, control flow information, variable alias information, pointer information, data dependency relationship and interface information generated after compilation.
[0034] In combination with the information system of electric power enterprises, research on software genetic security detection technology based on semantic slicing is carried out, and a semantic slicing segmentation model based on assembly and independent of software gene library is established to solve the problem of low gene recognition accuracy due to the inability to deploy offline due to continuous updating of gene library and malicious program transformation, thus forming a lightweight and high recognition accuracy software genetic security detection tool for electric power enterprise information system.
[0035] Compared with the prior art, the embodiments of the present invention have the following advantages: 1. The present invention determines whether the software gene has a safety hazard based on the data called by the software gene. During the power system software safety detection process, it can be conveniently determined whether the software gene calls irrelevant data based on the data type called by the software gene, thereby better determining whether the software has a safety hazard and reducing the false alarm rate.
[0036] 2. The present invention can quickly determine whether the software has security risks by comparing the software gene with the preset software gene in the preset software gene library. When the preset software gene is consistent with the software gene, it means that the software has security risks, which improves the software detection efficiency and helps to reduce the false alarm rate.
[0037] 3. When the software gene of the present invention has potential safety hazards, the software gene is configured in the software gene library, which increases the data in the software gene library and can effectively improve the detection efficiency of the software and reduce the false alarm rate in the subsequent detection process.
[0038] In a possible implementation, after determining the data of the software gene call, the method further includes: If the software gene has no call data, it is determined that the software gene does not have any security risks.
[0039] When the software gene calls itself, although the software gene does not call other data, the software gene itself is also a kind of data. Therefore, when the software gene calls itself, it is also necessary to determine whether the software gene has security risks. Usually, manual methods can be used to determine whether the software gene has security risks.
[0040] In a possible implementation, determining whether the software gene has a security risk according to whether the software gene calls irrelevant data includes: If the software gene has call data, determine the source of the data called by the software gene; Whether the software gene has a security risk is determined based on whether the software gene calls an irrelevant data source.
[0041] Since malware usually needs to call irrelevant data to perform corresponding damage, by determining whether the software under test calls other data, it can be effectively determined that the software has security risks. In addition, determining whether the software under test calls data is relatively simple and does not require a large number of complex calculations, thereby improving detection efficiency and enabling rapid security detection.
[0042] When the software under test calls data, it may be due to the data call for realizing the software function. When the software calls data, it is necessary to determine whether the data called by the software under test is the data necessary to realize the software function. When the data called by the software is not the data to realize the software function itself, it can be determined that the software has security risks.
[0043] In a possible implementation, determining whether the software gene has a security risk according to the source of the called data may be performed manually according to the source of the called data. Alternatively, determining whether the software gene has a security risk according to the source of the called data may be performed by manually classifying all data sources and automatically determining whether the software gene has a security risk according to different classifications.
[0044] Compared with manually determining whether software genes have safety hazards, using automatic methods to determine whether software genes have safety hazards is more efficient and has lower labor intensity for workers.
[0045] In a possible implementation, determining whether the software gene has a security risk according to whether the software gene calls an irrelevant data source includes: Get the data source types that are manually classified in advance; Determining the data source type of the software gene call based on the data source type manually classified in advance; Based on the correlation between different data source types and software genes, as well as the data source type called by the software gene, it is determined whether the software gene has security risks.
[0046] Power system software is highly professional. Therefore, the types of data called by the power system are relatively few, usually various parameters during the operation of the power system. In other words, the data called by the power system can usually be easily classified to automatically determine whether there are safety hazards in the software genes.
[0047] There are not too many types of data in the power system, and the differences between various data are relatively obvious. The data types are classified in advance, and then the data type called by the software is automatically determined through the corresponding algorithm. Compared with manually determining the type of called data, it has a higher detection rate and can effectively reduce the labor intensity of operators.
[0048] In a possible implementation, obtaining the software gene of the software to be detected includes: Get the software to be tested; The code of the software to be detected is fragmented to obtain the software gene.
[0049] In a possible implementation manner, the software gene includes a software code for implementing at least one function.
[0050] The software gene should include software code that implements the function. If the software gene does not include software code that implements the function, the software security cannot be effectively tested. Therefore, the software gene should include software code that implements at least one function. Usually, the software gene code should be as small as possible, or the functions implemented should be as small as possible, so as to improve the detection accuracy and efficiency of the software gene.
[0051] In a possible implementation, there are multiple software gene libraries; each software gene library corresponds to a type of software; accordingly, comparing the acquired software gene with a preset software gene in the software gene library includes: Determining the type of the software to be detected; According to the type of the software to be detected, determining a software gene library corresponding to the software type; The obtained software gene is compared with a preset software gene in a software gene library corresponding to the software type to obtain a comparison result.
[0052] The type of software to be detected is determined by manual classification, and the determined software type is identified and identified. Different types of software gene libraries are configured for different types of software, so that the preset software genes in the software gene library are all preset software genes of similar or identical types of software to be detected. When performing software gene detection, the data volume of the software gene library is relatively small, thereby improving the detection efficiency of the software.
[0053] The embodiment of the present invention adopts a classification detection method to perform security detection on the software to be tested, which can further improve the security detection efficiency of the software.
[0054] In a possible implementation manner, determining the type of the software to be detected includes: The type of the software to be detected is determined by pre-manual classification, and the determined software type is identified as identification data.
[0055] In a possible implementation manner, the identifying the software gene includes: identifying the software gene according to the type of the software gene.
[0056] In the step of identifying the software gene according to the type of the software gene, the type of the software gene is determined manually.
[0057] Usually software genes realize different functions. In practice, software genes can be classified according to their functions to determine the types of software genes.
[0058] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.
[0059] The following is an embodiment of the device of the present invention. For details not described in detail therein, reference may be made to the corresponding method embodiment described above.
[0060] Figure 3 The following is a schematic diagram of the structure of a power system software safety detection device based on software genes provided by an embodiment of the present invention. For ease of explanation, only the parts related to the embodiment of the present invention are shown, which are described in detail as follows: like Figure 3 As shown, a power system software safety detection device 3 based on software gene includes: An acquisition module 31 is used to acquire the software gene of the software to be detected; A comparison module 32, used for comparing the acquired software gene with a preset software gene in a software gene library; A first safety determination module 33, configured to determine that the software gene has a safety hazard when the software gene is consistent with a preset software gene; A data determination module 34, for determining the data called by the software gene when the software gene is inconsistent with the preset software gene; A second safety determination module 35, for determining whether the software gene has a safety hazard according to whether the software gene calls irrelevant data; A detection end module 36, used for ending the detection of the software gene when there is no potential safety hazard in the software gene; The software gene library update module 37 is used to configure the software gene in the software gene library and mark the software gene when there is a potential safety hazard in the software gene.
[0061] Compared with the prior art, the embodiments of the present invention have the following advantages: 1. The present invention determines whether the software gene has a safety hazard based on the data called by the software gene. During the power system software safety detection process, it can be conveniently determined whether the software gene calls irrelevant data based on the data type called by the software gene, thereby better determining whether the software has a safety hazard and reducing the false alarm rate.
[0062] 2. The present invention can quickly determine whether the software has security risks by comparing the software gene with the preset software gene in the preset software gene library. When the preset software gene is consistent with the software gene, it means that the software has security risks, which improves the software detection efficiency and helps to reduce the false alarm rate.
[0063] 3. When the software gene of the present invention has potential safety hazards, the software gene is configured in the software gene library, which increases the data in the software gene library and can effectively improve the detection efficiency of the software and reduce the false alarm rate in the subsequent detection process.
[0064] The present invention also provides a power system software safety detection device based on software genes, which is used to implement the above-mentioned power system software safety detection method based on software genes, comprising: A software gene acquisition module is used to acquire the software gene of the software to be detected, wherein the software gene can be acquired by manual input or by automatic recognition; A storage module, used to store the acquired software genes, or the software genes can also be acquired by calling, for example, the required software genes can be called and stored in a software gene database; A comparison module, used to compare the obtained software gene with a preset software gene preset in a software gene library, the comparison module automatically comparing the obtained software gene with the software gene in the gene library; The analysis module is used to determine the data called by the software gene, and determine whether the software gene has a security risk according to the data type called by the software gene; for example, when the data called by the software gene is data for realizing the software function, the software gene has no security risk, and when the data called by the software gene is irrelevant to the function realized by the software, the software gene may have a security risk. Usually, manual methods can be used to determine the accuracy, for example, when the software function is to monitor the operating status of the equipment, the software gene only needs to call the data of the equipment operating parameters, and does not need to call other data about the equipment; The archiving module is used to archive data. When the software gene does not have any potential safety hazard, the detection of the software gene is terminated. When the software gene has any potential safety hazard, the software gene is configured in a software gene library and the software gene is marked.
[0065] The initial construction of the software gene library can be carried out by manual selection. For example, the software genes of the malware are first determined, and then the malware genes are stored in the software gene library manually or automatically for backup.
[0066] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0067] Those of ordinary skill in the art will appreciate that the templates, units, and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0068] If the module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, it can implement the steps of the above-mentioned embodiments of the power system software safety detection method based on software genes. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device that can carry the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory, random access memory, electric carrier signal, telecommunication signal and software distribution medium.
[0069] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.
Claims
1. A software gene-based power system software security detection method, characterized in that: include: Obtaining software genes of the software to be tested; Comparing the obtained software gene with the preset software gene in the software gene library; When the software gene is consistent with the preset software gene, it is determined that the software gene has a security risk; When the software gene is inconsistent with the preset software gene, determining the data called by the software gene; Determining whether the software gene has a security risk according to whether the software gene calls irrelevant data; When the software gene does not have any potential safety hazard, the detection of the software gene is terminated; When the software gene has a potential safety hazard, the software gene is configured in a software gene library and the software gene is marked.
2. The power system software safety detection method based on software gene according to claim 1 is characterized in that: After the data of determining the gene call of the software, it also includes: If the software gene has no call data, it is determined that the software gene does not have any security risks.
3. The power system software safety detection method based on software gene according to claim 1 is characterized in that: Determining whether the software gene has a security risk according to whether the software gene calls irrelevant data includes: If the software gene has call data, determine the source of the data called by the software gene; Whether the software gene has a security risk is determined based on whether the software gene calls an irrelevant data source.
4. The power system software safety detection method based on software gene according to claim 3 is characterized in that: Determining whether the software gene has a security risk according to whether the software gene calls an irrelevant data source includes: Get the data source types that are manually classified in advance; Determining the data source type of the software gene call based on the data source type manually classified in advance; Based on the correlation between different data source types and software genes, as well as the data source type called by the software gene, it is determined whether the software gene has security risks.
5. The power system software safety detection method based on software gene according to claim 1 is characterized in that: The obtaining of software genes of the software to be detected comprises: Get the software to be tested; The code of the software to be detected is fragmented to obtain the software gene.
6. The power system software safety detection method based on software gene according to claim 1 is characterized in that: The software gene includes software code for implementing at least one function.
7. The power system software safety detection method based on software gene according to claim 1 is characterized in that: There are multiple software gene libraries; each software gene library corresponds to a type of software; accordingly, comparing the acquired software gene with the preset software gene in the software gene library includes: Determining the type of the software to be detected; According to the type of the software to be detected, determining a software gene library corresponding to the software type; The obtained software gene is compared with a preset software gene in a software gene library corresponding to the software type to obtain a comparison result.
8. The power system software safety detection method based on software gene according to claim 7 is characterized in that: Determining the type of the software to be detected includes: The type of the software to be detected is determined by pre-manual classification, and the determined software type is identified as identification data.
9. The power system software safety detection method based on software gene according to claim 1 is characterized in that: The identification of the software gene comprises: The software gene is identified according to the type of the software gene.
10. A power system software safety detection device based on software gene, characterized in that: include: An acquisition module, used to acquire the software gene of the software to be detected; A comparison module, used for comparing the acquired software gene with a preset software gene in a software gene library; A first safety determination module, configured to determine that the software gene has a safety hazard when the software gene is consistent with a preset software gene; A data determination module, used for determining the data called by the software gene when the software gene is inconsistent with the preset software gene; A second safety determination module, used to determine whether the software gene has a safety hazard according to whether the software gene calls irrelevant data; A detection end module, used for ending the detection of the software gene when there is no potential safety hazard in the software gene; The software gene library update module is used to configure the software gene in the software gene library and mark the software gene when there is a potential safety hazard in the software gene.
