Security detection management method and system for software development environment

Abstract

The invention discloses a safety detection management method and system for a software development environment, and relates to the technical field of vehicle monitoring software development environment detection, and the method comprises the steps: determining a core emphasis in each monitoring direction through the attribute of a target vehicle, and facilitating the integration and matching of the core emphasis in the subsequent monitoring direction. The core emphasis in the monitoring direction of the to-be-developed vehicle monitoring software is integrated, the core emphasis is allocated to each software development stage, the specific demand of the vehicle monitoring software is quantified and allocated to each development stage, an evaluation baseline is formulated in a targeted manner, and the safety of a development environment and the reliability of detection completion are improved. Each software development stage is detected through the preset detection strategy, and the evaluation index of each software development stage is generated by referring to the evaluation baseline corresponding to each software development stage, so that improvement and optimization of software development are facilitated, and the adaptability of software development environment detection is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle monitoring software development environment detection, and in particular to a safety detection management method and system for a software development environment. Background Art

[0002] Vehicle monitoring software is an important tool for modern vehicle management. It improves transportation safety and management efficiency and reduces operating costs by tracking vehicle location, speed, fuel consumption and other information in real time. Security detection management is crucial in the software development process. It involves network isolation, access control, configuration management, vulnerability scanning, penetration testing and other aspects to ensure that the boundaries between the development and testing environment and the production environment are clear and prevent security issues from penetrating. For vehicle monitoring software, security detection management is not only related to the stable operation and performance of software functions, but also directly affects the security of vehicle data and the protection of user privacy. Therefore, implementing strict security detection management in the software development environment is the key to ensuring the safe and reliable operation of vehicle monitoring software.

[0003] In the prior art, the security and completion detection of the software development environment only refers to the code implementation level for detection, without considering the specific needs of the vehicle monitoring direction. There is no unified detection standard rule, which makes the security detection of the software development environment low in adaptability and poor in detection reliability.

[0004] Therefore, how to improve the adaptability and reliability of safety testing in the vehicle software development environment is a technical problem that needs to be solved. Summary of the invention

[0005] The purpose of the present invention is to solve the problems of low adaptability and poor detection reliability of security detection of software development environment in the prior art, and to propose a security detection management method for software development environment, which is applied to an automobile monitoring platform and includes:

[0006] Collect the monitoring direction of the target vehicle, determine the core focus of each monitoring direction through the attributes of the target vehicle, obtain the vehicle monitoring software project information to be developed for the target vehicle, and match the monitoring direction of the vehicle monitoring software to be developed according to the vehicle monitoring software project information to be developed;

[0007] Determine all software development stages based on the project information of the vehicle monitoring software to be developed, integrate the core focus of the monitoring direction of the vehicle monitoring software to be developed, and allocate the core focus to each software development stage, thereby converting it into an evaluation baseline for each software development stage;

[0008] Each software development stage is tested through a preset detection strategy, and the evaluation indicators of each software development stage are generated by referring to the evaluation baseline corresponding to each software development stage;

[0009] The evaluation indicators of each software development stage are integrated to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed, and the evaluation indicators of the development environment of the vehicle monitoring software to be developed are referred to to help improve and optimize software development.

[0010] In some embodiments of the present application, the monitoring direction of the target vehicle includes one or more of vehicle operating status monitoring, vehicle safety performance monitoring, vehicle energy efficiency monitoring, driving behavior monitoring and vehicle fault monitoring.

[0011] In some embodiments of the present application, the core focus in each monitoring direction is determined by the attributes of the target vehicle, including:

[0012] The attributes of the target vehicle include vehicle purpose, vehicle type and vehicle past data, and the core focus includes safety indicators, real-time indicators, accuracy indicators and scalability indicators;

[0013] Analyze the vehicle purpose and vehicle type respectively to determine the first core focus interval and the second core focus interval in each monitoring direction of the target vehicle;

[0014] The vehicle's past data includes other vehicle reference data and maintenance accident data. When the target vehicle is a new vehicle, the data of vehicles of the same type and with the same performance as the target vehicle are found based on the other vehicle reference data, and the third core focus interval in each monitoring direction of the target vehicle is determined by combining the data of vehicles of the same type and with the same performance. When the target vehicle is an old vehicle, the maintenance accident data is used to identify vulnerable parts or vulnerable systems, and the causes of the vulnerable parts or vulnerable systems are traced back to determine the fourth core focus interval in each monitoring direction of the target vehicle based on the causes of the vulnerable parts or vulnerable systems.

[0015] The first core focus interval, the second core focus interval and the third core focus interval in each monitoring direction of the target vehicle are integrated, or the first core focus interval, the second core focus interval and the fourth core focus interval in each monitoring direction of the target vehicle are integrated to determine the core focus target interval in each monitoring direction;

[0016] Among them, the first core focus interval, the second core focus interval, the third core focus interval and the fourth core focus interval are all numerical intervals of security indicators, real-time indicators, accuracy indicators and scalability indicators.

[0017] In some embodiments of the present application, the core focus of the monitoring direction of the vehicle monitoring software to be developed is integrated, including:

[0018] Each monitoring direction corresponds to a standard value of the core focus. The standard value and target interval of the same core focus under the same monitoring direction are compared to obtain the deviation value of each core focus. When the standard value is less than the target interval, the deviation value is the difference between the standard value and the target interval, otherwise, the deviation value is 0.

[0019] Evaluate the risk hazard and risk probability involved in the implementation of each core focus under each monitoring direction, and determine the priority of each monitoring direction based on the deviation value of the core focus;

[0020]

[0021] Among them, L i is the i-th monitoring direction of the vehicle monitoring software to be developed, β i is the conversion coefficient of the i-th monitoring direction of the vehicle monitoring software to be developed, 4 represents the safety index, real-time index, accuracy index and scalability index, α i , j is the risk weight of the jth core focus in the ith monitoring direction, Q i , j is the risk hazard degree of the jth core focus in the ith monitoring direction, W i , j is the probability of occurrence of the risk of the jth core focus in the ith monitoring direction, C i , j is the deviation value of the jth core focus in the ith monitoring direction, k1 j is the constant corresponding to the jth core focus, k2 i is the constant corresponding to the i-th monitoring direction.

[0022] In some embodiments of the present application, the core focus is allocated to each software development stage, thereby converting it into an evaluation baseline for each software development stage, including:

[0023] Allocate multiple initial core focus target intervals for each software development stage according to the core focus target interval under each monitoring direction; if multiple initial core focus target intervals under the same core focus of the same software development stage have a common intersection interval, then use the common intersection interval as the target interval under the core focus of the software development stage; otherwise, determine the partial intersection intervals and non-intersection intervals of multiple initial core focus target intervals under the same core focus of the same software development stage, and select one of the partial intersection intervals and non-intersection intervals as the target interval under the core focus of the software development stage according to the priority of the monitoring direction;

[0024] Generate an evaluation baseline for each detection indicator based on the target intervals of all core focuses under each software development stage.

[0025] In some embodiments of the present application, each software development stage is tested by a preset detection strategy, including:

[0026] The software development stage includes the coding stage. The detection strategy for the coding stage is:

[0027] Use static analysis tools to perform static analysis on the coded code and generate actual values ​​of multiple detection indicators of static analysis;

[0028] The dynamic analysis tool is used to dynamically analyze the already encoded code to generate actual values ​​of multiple detection indicators of the dynamic analysis.

[0029] In some embodiments of the present application, the evaluation indicators for each software development stage are generated by referring to the evaluation baseline corresponding to each software development stage, including:

[0030] In the coding stage, the actual values ​​of multiple detection indicators of static analysis and dynamic analysis are compared with the evaluation baseline. When the actual value meets or exceeds the evaluation baseline, a positive value is assigned according to the difference between the actual value and the evaluation baseline. When the actual value does not meet or exceed the evaluation baseline, a negative value is assigned according to the difference between the actual value and the evaluation baseline.

[0031] The multiple detection indicators of dynamic analysis are divided into stability indicators and instability indicators, and the evaluation indicators of the coding stage are generated by the positive and negative values ​​of the multiple detection indicators of static analysis and the stability indicators and instability indicators of dynamic analysis;

[0033]

[0034] Among them, Z is the evaluation index of the encoding stage, τ1 and τ2 are the combination coefficients of static analysis detection indicators and dynamic analysis instability indicators, respectively, n1, n2, and n3 are the number of static analysis detection indicators, the number of dynamic analysis instability indicators, and the number of dynamic analysis stability indicators, respectively. are the weight of the x1th static analysis detection index, the weight of the x2th dynamic analysis instability index, and the weight of the x3th dynamic analysis stability index, respectively. is the positive or negative value of the x1th static analysis detection index, the positive or negative value of the x2th dynamic analysis unstable index, the positive or negative value of the x3th dynamic analysis stable index, and k3 is a preset constant.

[0035] In some embodiments of the present application, the evaluation indicators of each software development stage are integrated to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed, including:

[0036] The software development phase also includes the testing phase, deployment phase, and operation and maintenance phase;

[0037] The evaluation indicators of the development environment of the vehicle monitoring software to be developed are generated by integrating the evaluation indicators of the coding stage, testing stage, deployment stage and operation and maintenance stage.

[0038] Correspondingly, the present application also provides a security detection management system for a software development environment, which is applied to an automobile monitoring platform and includes:

[0039] A determination module is used to collect the monitoring directions of the target vehicle, determine the core focus of each monitoring direction through the attributes of the target vehicle, obtain the vehicle monitoring software project information to be developed of the target vehicle, and match the monitoring direction of the vehicle monitoring software to be developed according to the vehicle monitoring software project information to be developed;

[0040] An allocation module is used to determine all software development stages according to the project information of the vehicle monitoring software to be developed, integrate the core emphasis of the monitoring direction of the vehicle monitoring software to be developed, and allocate the core emphasis to each software development stage, thereby converting it into an evaluation baseline for each software development stage;

[0041] A detection module is used to detect each software development stage through a preset detection strategy, and generate evaluation indicators for each software development stage by referring to the evaluation baseline corresponding to each software development stage;

[0042] The optimization module is used to integrate the evaluation indicators of each software development stage to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed, and refer to the evaluation indicators of the development environment of the vehicle monitoring software to be developed to help improve and optimize software development.

[0043] Compared with the prior art, the present invention has the following beneficial effects:

[0044] 1. Determine the core focus of each monitoring direction through the attributes of the target vehicle, determine the core focus of each vehicle monitoring direction, and facilitate the integration and matching of the core focus of the subsequent monitoring direction. Integrate the core focus of the monitoring direction of the vehicle monitoring software to be developed, and assign the core focus to each software development stage, thereby converting it into an evaluation baseline for each software development stage, quantifying the specific requirements of the vehicle monitoring software, and assigning it to each development stage, and formulating evaluation baselines in a targeted manner, thereby improving the security of the development environment and the reliability of completed detection.

[0045] 2. Each software development stage is tested through preset detection strategies, and the evaluation indicators of each software development stage are generated by referring to the evaluation baseline corresponding to each software development stage, so as to help improve and optimize software development, improve the adaptability of software development environment detection, and ensure the safe and stable operation of the software development process. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 A flowchart of a security detection management method for a software development environment proposed by the present invention;

[0047] Figure 2 This is a structural diagram of a security detection management system for a software development environment proposed by the present invention. DETAILED DESCRIPTION

[0048] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments.

[0049] Reference Figure 1 , a security detection management method for a software development environment, applied to an automobile monitoring platform, comprises the following steps:

[0050] Step S101, collect the monitoring directions of the target vehicle, determine the core focus of each monitoring direction through the attributes of the target vehicle, obtain the vehicle monitoring software project information to be developed for the target vehicle, and match the monitoring direction of the vehicle monitoring software to be developed according to the vehicle monitoring software project information to be developed.

[0051] In this embodiment, the target vehicle is the vehicle used by the developed software, and different vehicles may have different software requirements. The monitoring direction includes operating status, safety performance, driving behavior, energy consumption, etc. The vehicle monitoring software project information to be developed includes the functions to be implemented, whether it is a single monitoring direction or multiple monitoring direction functions.

[0052] In some embodiments of the present application, the monitoring direction of the target vehicle includes one or more of vehicle operating status monitoring, vehicle safety performance monitoring, vehicle energy efficiency monitoring, driving behavior monitoring and vehicle fault monitoring.

[0053] In some embodiments of the present application, the core focus in each monitoring direction is determined by the attributes of the target vehicle, including:

[0054] The attributes of the target vehicle include vehicle purpose, vehicle type and vehicle past data, and the core focus includes safety indicators, real-time indicators, accuracy indicators and scalability indicators;

[0055] Analyze the vehicle purpose and vehicle type respectively to determine the first core focus interval and the second core focus interval in each monitoring direction of the target vehicle;

[0056] The vehicle's past data includes other vehicle reference data and maintenance accident data. When the target vehicle is a new vehicle, the data of vehicles of the same type and with the same performance as the target vehicle are found based on the other vehicle reference data, and the third core focus interval in each monitoring direction of the target vehicle is determined by combining the data of vehicles of the same type and with the same performance. When the target vehicle is an old vehicle, the maintenance accident data is used to identify vulnerable parts or vulnerable systems, and the causes of the vulnerable parts or vulnerable systems are traced back to determine the fourth core focus interval in each monitoring direction of the target vehicle based on the causes of the vulnerable parts or vulnerable systems.

[0057] The first core focus interval, the second core focus interval and the third core focus interval in each monitoring direction of the target vehicle are integrated, or the first core focus interval, the second core focus interval and the fourth core focus interval in each monitoring direction of the target vehicle are integrated to determine the core focus target interval in each monitoring direction;

[0058] Among them, the first core focus interval, the second core focus interval, the third core focus interval and the fourth core focus interval are all numerical intervals of security indicators, real-time indicators, accuracy indicators and scalability indicators.

[0059] In this embodiment, the core focuses include safety indicators, real-time indicators, precision indicators (accuracy) and scalability indicators, and these four core focuses are involved in each monitoring direction. The vehicle purpose (commercial, ordinary private) and vehicle type (electric vehicle, oil vehicle, hybrid vehicle) are analyzed separately to determine the first core focus interval and the second core focus interval in each monitoring direction of the target vehicle. For example, since commercial vehicles are usually used for cargo transportation or passenger transportation, the requirements for safety indicators, real-time indicators, precision indicators and scalability indicators are different, and the scalability requirements may be higher. Considering that commercial vehicles may need to be modified or upgraded according to different transportation needs, the monitoring system should have a certain degree of scalability to adapt to future changes. The requirements for safety indicators, real-time indicators, precision indicators and scalability indicators will vary depending on the vehicle type.

[0060] In this embodiment, vehicle data of the same type and vehicle data of the same performance as the target vehicle are found based on other vehicle reference data. Vehicle data of the same type refers to vehicle data of similar type and level to the target vehicle, and vehicle data of the same performance refers to vehicle data of similar configuration and performance to the target vehicle. The third core focus interval is determined with reference to these data. The fourth core focus interval in each monitoring direction of the target vehicle is determined based on the cause of vulnerability, and the fourth core focus interval is determined by analyzing the cause of vulnerability. Finally, the first core focus interval, the second core focus interval, the third core focus interval, and the fourth core focus interval are comprehensively considered to determine the core focus target interval, and the core focus target interval includes specific intervals of safety indicators, real-time indicators, accuracy indicators, and scalability indicators.

[0061] Step S102, determining all software development stages according to the project information of the vehicle monitoring software to be developed, integrating the core emphasis in the monitoring direction of the vehicle monitoring software to be developed, and allocating the core emphasis to each software development stage, thereby converting it into an evaluation baseline for each software development stage.

[0062] In this embodiment, generally speaking, the software development stage includes several major stages in the coding stage, the testing stage, the deployment stage, and the operation and maintenance stage (this stage may not be included), and this stage can be further subdivided. The core focus of the monitoring direction of the vehicle monitoring software to be developed (safety indicators, real-time indicators, accuracy indicators, and scalability indicator requirements) is allocated to each specific development stage to form an evaluation baseline. The evaluation baseline can be understood as a threshold, which is the threshold of the detection indicator after each stage detection.

[0063] In some embodiments of the present application, the core focus of the monitoring direction of the vehicle monitoring software to be developed is integrated, including:

[0064] Each monitoring direction corresponds to a standard value of the core focus. The standard value and target interval of the same core focus under the same monitoring direction are compared to obtain the deviation value of each core focus. When the standard value is less than the target interval, the deviation value is the difference between the standard value and the target interval, otherwise, the deviation value is 0.

[0065] Evaluate the risk hazard and risk probability involved in the implementation of each core focus under each monitoring direction, and determine the priority of each monitoring direction based on the deviation value of the core focus;

[0066]

[0067] Among them, L i is the i-th monitoring direction of the vehicle monitoring software to be developed, β iis the conversion coefficient of the i-th monitoring direction of the vehicle monitoring software to be developed, 4 represents the safety index, real-time index, accuracy index and scalability index, α i , j is the risk weight of the jth core focus in the ith monitoring direction, Q i , j is the risk hazard degree of the jth core focus in the ith monitoring direction, W i , j is the probability of occurrence of the risk of the jth core focus in the ith monitoring direction, C i , j is the deviation value of the jth core focus in the ith monitoring direction, k1 j is the constant corresponding to the jth core focus, k2 i is the constant corresponding to the i-th monitoring direction.

[0068] In this embodiment, each monitoring direction corresponds to a standard value of a core focus, and the standard value here is the value of each core focus that is generally determined in advance according to the monitoring direction. The risk faced by implementing each core focus is analyzed separately, and the risks that each core focus may face during the implementation process are evaluated, including technical risks, security risks, business risks, etc. These risks are integrated to determine the overall risk hazard and probability, and the product of the two is the risk amount or risk degree. Indicates the correction of the risk amount by the deviation value, C i , j When it is 0,

[0069] In some embodiments of the present application, the core focus is allocated to each software development stage, thereby converting it into an evaluation baseline for each software development stage, including:

[0070] Allocate multiple initial core focus target intervals for each software development stage according to the core focus target interval under each monitoring direction; if multiple initial core focus target intervals under the same core focus of the same software development stage have a common intersection interval, then use the common intersection interval as the target interval under the core focus of the software development stage; otherwise, determine the partial intersection intervals and non-intersection intervals of multiple initial core focus target intervals under the same core focus of the same software development stage, and select one of the partial intersection intervals and non-intersection intervals as the target interval under the core focus of the software development stage according to the priority of the monitoring direction;

[0071] Generate an evaluation baseline for each detection indicator based on the target intervals of all core focuses under each software development stage.

[0072] In this embodiment, multiple initial core focus target intervals are allocated in consideration of the nature and situation of each development stage, and each monitoring direction corresponds to an initial core focus target interval. When multiple initial core focus target intervals have a common intersection interval, that is, all initial core focus target intervals will have an intersection, then the intersection is used as the target interval under the core focus. When multiple initial core focus target intervals have partial intersection intervals, the priority of the partial intersection interval and the priority of the non-intersection interval are compared to determine which is the target interval. The priority of the partial intersection interval (the priority of multiple monitoring directions) and the priority of the non-intersection interval (the priority of the monitoring direction) are compared to determine the target interval. Then, the target intervals of security, real-time, accuracy and scalability are converted into the evaluation baseline of each detection indicator involved in each development stage.

[0073] It should be noted that simply adjusting the four core focuses of security, real-time, accuracy, and scalability to the maximum value may not necessarily meet the actual monitoring requirements. This is because in actual applications, these four focuses often have a mutually restrictive relationship, and factors such as resource limitations, technical feasibility, and cost-effectiveness must also be considered. For example, improving security may require adding redundant systems or more frequent data checks, which may sacrifice some real-time performance. Improving real-time performance sometimes requires reducing data processing time, which may reduce the strictness of security checks. Therefore, it is necessary to determine the appropriate value (target range) for each core focus.

[0074] Step S103, detecting each software development stage through a preset detection strategy, and generating evaluation indicators for each software development stage with reference to the evaluation baseline corresponding to each software development stage.

[0075] In this embodiment, for the coding stage, the detection strategy adopted is to combine static analysis with dynamic analysis to determine the evaluation index, and general detection techniques such as functional testing, performance testing, and security testing are adopted for the testing stage, deployment stage, and operation and maintenance stage. Static analysis, as the name implies, is a method of checking and analyzing the code without running the code. It helps developers find potential errors, loopholes, and places that do not follow the coding specifications by deeply analyzing the syntax, structure, logic, etc. of the code. Static analysis is usually used as a link in the code development process to improve code quality and maintainability. Dynamic analysis is a method for monitoring and analyzing the performance and behavior of the code during the code running process. It evaluates the performance and stability of the code by collecting data during the code running process, such as memory usage, CPU occupancy, response time, etc. Dynamic analysis can help developers find performance bottlenecks, memory leaks, thread competition, etc. in the code, thereby optimizing the performance of the code and improving the stability of the software. Combine static analysis with dynamic analysis to determine the evaluation indicators of the coding stage.

[0076] It is understandable that the evaluation baseline of each detection indicator is generated according to the target interval of all core focuses in each software development stage. Because the core focus is not very specific for each detection indicator, it needs to be converted. First, determine the core focus involved or represented by each detection indicator. For example, the detection indicators after static analysis include the number of code errors and code complexity. The number of code errors may involve security indicators, accuracy indicators, and scalability indicators. The evaluation baseline (threshold) corresponding to the number of code errors is determined based on these three. The evaluation baseline of other detection indicators is determined in the same way. The detection indicators after static analysis often do not involve real-time performance.

[0077] In some embodiments of the present application, each software development stage is tested by a preset detection strategy, including:

[0078] The software development stage includes the coding stage. The detection strategy for the coding stage is:

[0079] Use static analysis tools to perform static analysis on the coded code and generate actual values ​​of multiple detection indicators of static analysis;

[0080] The dynamic analysis tool is used to dynamically analyze the already encoded code to generate actual values ​​of multiple detection indicators of the dynamic analysis.

[0081] In some embodiments of the present application, the evaluation indicators for each software development stage are generated by referring to the evaluation baseline corresponding to each software development stage, including:

[0082] In the coding stage, the actual values ​​of multiple detection indicators of static analysis and dynamic analysis are compared with the evaluation baseline. When the actual value meets or exceeds the evaluation baseline, a positive value is assigned according to the difference between the actual value and the evaluation baseline. When the actual value does not meet or exceed the evaluation baseline, a negative value is assigned according to the difference between the actual value and the evaluation baseline.

[0083] The multiple detection indicators of dynamic analysis are divided into stability indicators and instability indicators, and the evaluation indicators of the coding stage are generated by the positive and negative values ​​of the multiple detection indicators of static analysis and the stability indicators and instability indicators of dynamic analysis;

[0084]

[0085] Among them, Z is the evaluation index of the encoding stage, τ1 and τ2 are the combination coefficients of static analysis detection indicators and dynamic analysis instability indicators, respectively, n1, n2, and n3 are the number of static analysis detection indicators, the number of dynamic analysis instability indicators, and the number of dynamic analysis stability indicators, respectively. are the weight of the x1th static analysis detection index, the weight of the x2th dynamic analysis instability index, and the weight of the x3th dynamic analysis stability index, respectively. is the positive or negative value of the x1th static analysis detection index, the positive or negative value of the x2th dynamic analysis unstable index, the positive or negative value of the x3th dynamic analysis stable index, and k3 is a preset constant.

[0086] In this embodiment, multiple detection indicators of dynamic analysis are divided into stability indicators (crash rate, exception rate, etc., to evaluate the reliability of the code) and instability indicators (performance indicators (including response time, throughput, memory usage, etc., to evaluate the operating efficiency of the code), resource utilization (analyzing the occupation of system resources by the code during operation, such as CPU, memory, etc.)). A positive value is a positive number, and a negative value is a negative number. A positive value indicates the completion of the detection indicator, and a negative value indicates that the detection indicator is not completed.

[0087] In this embodiment, It indicates the overall completion degree after integrating the detection indicators of static analysis and dynamic instability indicators. It represents the correction of the overall completion by the dynamic stability index, and then takes the average value to describe the completion of this stage.

[0088] Step S104, integrating the evaluation indicators of each software development stage to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed, and referring to the evaluation indicators of the development environment of the vehicle monitoring software to be developed to help improve and optimize software development.

[0089] In this embodiment, the evaluation indicators of the development environment of the vehicle monitoring software to be developed are used to describe the overall completion and safety of the vehicle monitoring software development process. When helping to improve and optimize software development, reference can be made based on the evaluation indicators of the specific development stage or specific detection indicators.

[0090] In some embodiments of the present application, the evaluation indicators of each software development stage are integrated to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed, including:

[0091] The software development phase also includes the testing phase, deployment phase, and operation and maintenance phase;

[0092] The evaluation indicators of the development environment of the vehicle monitoring software to be developed are generated by integrating the evaluation indicators of the coding stage, testing stage, deployment stage and operation and maintenance stage.

[0093] Compared with the prior art, the present invention has the following beneficial effects:

[0094] 1. Determine the core focus of each monitoring direction through the attributes of the target vehicle, determine the core focus of each vehicle monitoring direction, and facilitate the integration and matching of the core focus of the subsequent monitoring direction. Integrate the core focus of the monitoring direction of the vehicle monitoring software to be developed, and assign the core focus to each software development stage, thereby converting it into an evaluation baseline for each software development stage, quantifying the specific requirements of the vehicle monitoring software, and assigning it to each development stage, and formulating evaluation baselines in a targeted manner, thereby improving the security of the development environment and the reliability of completed detection.

[0095] 2. Each software development stage is tested through preset detection strategies, and the evaluation indicators of each software development stage are generated by referring to the evaluation baseline corresponding to each software development stage, so as to help improve and optimize software development, improve the adaptability of software development environment detection, and ensure the safe and stable operation of the software development process.

[0096] Through the description of the above implementation methods, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each implementation scenario of the present invention.

[0097] Correspondingly, the present application also provides a security detection management system for a software development environment, which is applied to a vehicle monitoring platform, such as Figure 2Shown include,

[0098] A determination module is used to collect the monitoring directions of the target vehicle, determine the core focus of each monitoring direction through the attributes of the target vehicle, obtain the vehicle monitoring software project information to be developed of the target vehicle, and match the monitoring direction of the vehicle monitoring software to be developed according to the vehicle monitoring software project information to be developed;

[0099] An allocation module is used to determine all software development stages according to the project information of the vehicle monitoring software to be developed, integrate the core emphasis of the monitoring direction of the vehicle monitoring software to be developed, and allocate the core emphasis to each software development stage, thereby converting it into an evaluation baseline for each software development stage;

[0100] A detection module is used to detect each software development stage through a preset detection strategy, and generate evaluation indicators for each software development stage by referring to the evaluation baseline corresponding to each software development stage;

[0101] The optimization module is used to integrate the evaluation indicators of each software development stage to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed, and refer to the evaluation indicators of the development environment of the vehicle monitoring software to be developed to help improve and optimize software development.

[0102] Those skilled in the art will appreciate that the accompanying drawings are merely schematic diagrams of a preferred implementation scenario, and the modules or processes in the accompanying drawings are not necessarily required for implementing the present invention.

[0103] Those skilled in the art will appreciate that the modules in the system in the implementation scenario can be distributed in the system of the implementation scenario according to the implementation scenario description, or can be changed accordingly and located in one or more systems different from the implementation scenario. The modules in the above implementation scenario can be combined into one module, or can be further split into multiple submodules.

[0104] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A security detection management method for a software development environment, applied to an automobile monitoring platform, characterized in that: include, Collect the monitoring direction of the target vehicle, determine the core focus of each monitoring direction through the attributes of the target vehicle, obtain the vehicle monitoring software project information to be developed for the target vehicle, and match the monitoring direction of the vehicle monitoring software to be developed according to the vehicle monitoring software project information to be developed; Determine all software development stages based on the project information of the vehicle monitoring software to be developed, integrate the core focus of the monitoring direction of the vehicle monitoring software to be developed, and allocate the core focus to each software development stage, thereby converting it into an evaluation baseline for each software development stage; Each software development stage is tested through a preset detection strategy, and the evaluation indicators of each software development stage are generated by referring to the evaluation baseline corresponding to each software development stage; The evaluation indicators of each software development stage are integrated to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed, and the evaluation indicators of the development environment of the vehicle monitoring software to be developed are referred to to help improve and optimize software development.

2. The method for security detection and management of a software development environment according to claim 1, characterized in that: The monitoring directions of the target vehicle include one or more of vehicle operation status monitoring, vehicle safety performance monitoring, vehicle energy efficiency monitoring, driving behavior monitoring and vehicle fault monitoring.

3. The method for security detection and management of software development environment according to claim 2, characterized in that: The core focus of each monitoring direction is determined by the attributes of the target vehicle, including: The attributes of the target vehicle include vehicle purpose, vehicle type and vehicle past data, and the core focus includes safety indicators, real-time indicators, accuracy indicators and scalability indicators; Analyze the vehicle purpose and vehicle type respectively to determine the first core focus interval and the second core focus interval in each monitoring direction of the target vehicle; The vehicle's past data includes other vehicle reference data and maintenance accident data. When the target vehicle is a new vehicle, the data of vehicles of the same type and with the same performance as the target vehicle are found based on the other vehicle reference data, and the third core focus interval in each monitoring direction of the target vehicle is determined by combining the data of vehicles of the same type and with the same performance. When the target vehicle is an old vehicle, the maintenance accident data is used to identify vulnerable parts or vulnerable systems, and the causes of the vulnerable parts or vulnerable systems are traced back to determine the fourth core focus interval in each monitoring direction of the target vehicle based on the causes of the vulnerable parts or vulnerable systems. The first core focus interval, the second core focus interval and the third core focus interval in each monitoring direction of the target vehicle are integrated, or the first core focus interval, the second core focus interval and the fourth core focus interval in each monitoring direction of the target vehicle are integrated to determine the core focus target interval in each monitoring direction; Among them, the first core focus interval, the second core focus interval, the third core focus interval and the fourth core focus interval are all numerical intervals of security indicators, real-time indicators, accuracy indicators and scalability indicators.

4. The method for security detection and management of a software development environment according to claim 3, characterized in that: Integrate the core focus of the monitoring direction of the vehicle monitoring software to be developed, include, Each monitoring direction corresponds to a standard value of the core focus. The standard value and target interval of the same core focus under the same monitoring direction are compared to obtain the deviation value of each core focus. When the standard value is less than the target interval, the deviation value is the difference between the standard value and the target interval, otherwise, the deviation value is 0. Evaluate the risk hazard and risk probability involved in the implementation of each core focus under each monitoring direction, and determine the priority of each monitoring direction based on the deviation value of the core focus; Among them, L i is the i-th monitoring direction of the vehicle monitoring software to be developed, β i is the conversion coefficient of the i-th monitoring direction of the vehicle monitoring software to be developed, 4 represents the safety index, real-time index, accuracy index and scalability index, α i , j is the risk weight of the jth core focus in the ith monitoring direction, Q i , j is the risk hazard degree of the jth core focus in the ith monitoring direction, W i , j is the probability of occurrence of the risk of the jth core focus in the ith monitoring direction, C i , j is the deviation value of the jth core focus in the ith monitoring direction, k1 j is the constant corresponding to the jth core focus, k2 i is the constant corresponding to the i-th monitoring direction.

5. The method for security detection and management of software development environment according to claim 3, characterized in that: And allocate the core focus to each software development stage, thus transforming it into an evaluation baseline for each software development stage. include, Allocate multiple initial core focus target intervals for each software development stage according to the core focus target interval under each monitoring direction; if multiple initial core focus target intervals under the same core focus of the same software development stage have a common intersection interval, then use the common intersection interval as the target interval under the core focus of the software development stage; otherwise, determine the partial intersection intervals and non-intersection intervals of multiple initial core focus target intervals under the same core focus of the same software development stage, and select one of the partial intersection intervals and non-intersection intervals as the target interval under the core focus of the software development stage according to the priority of the monitoring direction; Generate an evaluation baseline for each detection indicator based on the target intervals of all core focuses under each software development stage.

6. The method for security detection and management of software development environment according to claim 5, characterized in that: Each software development stage is tested through preset detection strategies, including: The software development stage includes the coding stage. The detection strategy for the coding stage is: Use static analysis tools to perform static analysis on the coded code and generate actual values ​​of multiple detection indicators of static analysis; The dynamic analysis tool is used to dynamically analyze the already encoded code to generate actual values ​​of multiple detection indicators of the dynamic analysis.

7. The method for security detection and management of software development environment according to claim 6, characterized in that: Refer to the evaluation baseline corresponding to each software development stage to generate the evaluation indicators for each software development stage, including: In the coding stage, the actual values ​​of multiple detection indicators of static analysis and dynamic analysis are compared with the evaluation baseline. When the actual value meets or exceeds the evaluation baseline, a positive value is assigned according to the difference between the actual value and the evaluation baseline. When the actual value does not meet or exceed the evaluation baseline, a negative value is assigned according to the difference between the actual value and the evaluation baseline. The multiple detection indicators of dynamic analysis are divided into stability indicators and instability indicators, and the evaluation indicators of the coding stage are generated by the positive and negative values ​​of the multiple detection indicators of static analysis and the stability indicators and instability indicators of dynamic analysis; Among them, Z is the evaluation index of the encoding stage, τ1 and τ2 are the combination coefficients of static analysis detection indicators and dynamic analysis instability indicators, respectively, n1, n2, and n3 are the number of static analysis detection indicators, the number of dynamic analysis instability indicators, and the number of dynamic analysis stability indicators, respectively. are the weight of the x1th static analysis detection index, the weight of the x2th dynamic analysis instability index, and the weight of the x3th dynamic analysis stability index, respectively. is the positive or negative value of the x1th static analysis detection index, the positive or negative value of the x2th dynamic analysis unstable index, the positive or negative value of the x3th dynamic analysis stable index, and k3 is a preset constant.

8. The method for security detection and management of software development environment according to claim 7, characterized in that: Integrate the evaluation indicators of each software development stage to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed. include, The software development phase also includes the testing phase, deployment phase, and operation and maintenance phase; The evaluation indicators of the development environment of the vehicle monitoring software to be developed are generated by integrating the evaluation indicators of the coding stage, testing stage, deployment stage and operation and maintenance stage.

9. A security detection and management system for a software development environment, applied to an automobile monitoring platform, characterized in that: include, A determination module is used to collect the monitoring directions of the target vehicle, determine the core focus of each monitoring direction through the attributes of the target vehicle, obtain the vehicle monitoring software project information to be developed of the target vehicle, and match the monitoring direction of the vehicle monitoring software to be developed according to the vehicle monitoring software project information to be developed; An allocation module is used to determine all software development stages according to the project information of the vehicle monitoring software to be developed, integrate the core emphasis of the monitoring direction of the vehicle monitoring software to be developed, and allocate the core emphasis to each software development stage, thereby converting it into an evaluation baseline for each software development stage; A detection module is used to detect each software development stage through a preset detection strategy, and generate evaluation indicators for each software development stage by referring to the evaluation baseline corresponding to each software development stage; The optimization module is used to integrate the evaluation indicators of each software development stage to obtain the evaluation indicators of the development environment of the vehicle monitoring software to be developed, and refer to the evaluation indicators of the development environment of the vehicle monitoring software to be developed to help improve and optimize software development.

Images