Network security vulnerability implantation method and related device

Abstract

The embodiment of the invention relates to the field of digital twin models, and provides a network security vulnerability implantation method and a related device, and the method comprises the steps: obtaining a vehicle digital twin model; identifying a key interface of a network connection module in the vehicle digital twin model; performing risk assessment on the key interface of the network connection module to obtain a risk assessment result; according to the risk assessment result, determining a key interface of a to-be-implanted vulnerability; determining the vulnerability to be implanted according to the key interface of the vulnerability to be implanted; and implanting the vulnerability to be implanted into the key interface of the vulnerability to be implanted. The technical problem that in the prior art, most of existing virtual simulation vehicle testing methods focus on simulation of physical characteristics of a vehicle, and the degree of attention to the vehicle in the network level is not enough, so that the testing method for the vehicle in a virtual simulation environment is still different from the testing result for a real vehicle in a real environment is solved.

Description

Technical Field

[0001] The present application relates to the technical field of digital twin models, and specifically to a network security vulnerability implantation method and related devices. Background Art

[0002] With the rapid development of intelligent connected vehicle technology, vehicles are no longer just traditional means of transportation, but intelligent entities that integrate complex network systems and advanced sensor technologies. These vehicles exchange real-time data with other vehicles, infrastructure and cloud services through Internet of Vehicles technology, greatly improving the convenience, safety and comfort of driving.

[0003] However, although there are some methods for testing vehicles based on virtual simulation technology on the market, most of these methods focus on simulating the physical characteristics of the vehicle and do not pay enough attention to the network level of the vehicle. Therefore, it is difficult to accurately simulate the actual operating status of the vehicle in the network environment, which ultimately leads to large differences between the test methods of vehicles in virtual simulation environments and the test results of real vehicles in real environments.

[0004] In view of this, the inventor proposes a network security vulnerability implantation method and related devices. Summary of the invention

[0005] The embodiments of the present application provide a network security vulnerability implantation method and related devices to solve the technical problem that the existing virtual simulation vehicle testing methods in the prior art mostly focus on the simulation of the physical characteristics of the vehicle, but do not pay enough attention to the vehicle at the network level, resulting in differences between the testing results of the vehicle in the virtual simulation environment and the testing results of the real vehicle in the real environment.

[0006] A first aspect of an embodiment of the present application provides a network security vulnerability implantation method, the network security vulnerability implantation method comprising:

[0007] Obtain vehicle digital twin model;

[0008] Identify key interfaces of the connected modules in the vehicle digital twin model;

[0009] Performing risk assessment on key interfaces of the network connection module to obtain risk assessment results;

[0010] Determine the key interface where the vulnerability is to be implanted based on the risk assessment results;

[0011] Determine the vulnerability to be implanted according to the key interface of the vulnerability to be implanted;

[0012] Implant the vulnerability to be implanted into the key interface of the vulnerability to be implanted.

[0013] Furthermore, identifying the key interfaces of the network connection module in the vehicle digital twin model includes:

[0014] Build a vehicle network topology diagram based on the vehicle digital twin model;

[0015] Determine, according to the vehicle network topology diagram, data transmission parameters between k initial network modules in the vehicle digital twin model;

[0016] Calculating importance scores of k initial network connection modules according to the data transmission parameters to obtain an importance score value set;

[0017] Based on the importance score value set, determining m key network modules from the k initial network modules;

[0018] The interface corresponding to each key networking module in the m key networking modules is determined as a key interface.

[0019] Further, according to the data transmission parameters, the importance scores of the k initial network connection modules are calculated to obtain an importance score set, and the calculation formula of the importance score is as follows:

[0020]

[0021] Among them, S is the importance score, w f is the frequency weight of data transmission, w s is the size weight of data transmission, w p is the weight of data priority, w c is the sensitivity weight of data transmission, w r is the weight of the real-time data transmission, f is the frequency of data transmission, s is the size of data transmission, p is the data priority, c is the sensitivity index of the data, and r is the real-time index of data transmission.

[0022] Furthermore, a risk assessment is performed on the key interfaces of the network connection module to obtain risk assessment results, including:

[0023] Configure the traffic controller to simulate attack vectors;

[0024] Acquire the attack vectors used to attack the key interface until the key interface is breached, and the number of attacks and the post-attack status to obtain the attack result data set;

[0025] Calculating the attack vector defense coefficient of each of the key interfaces according to the attack result data set;

[0026] According to the attack vector defense coefficient, the risk assessment result of each of the key interfaces is determined.

[0027] Further, according to the risk assessment result, a risk level assessment is performed on a key interface of the network connection module to obtain a risk assessment level;

[0028] Randomly extracting a preset number of the key interfaces from the risk assessment levels to obtain a screening key interface data set;

[0029] The key interfaces in the key interface data set are screened and determined as the key interfaces to be implanted with vulnerabilities.

[0030] Further, according to the key interface of the vulnerability to be implanted, the vulnerability to be implanted is determined, including:

[0031] Extract vulnerability datasets from security vulnerability databases;

[0032] Matching the key interface of the vulnerability to be implanted with the vulnerability data set to obtain a matching result;

[0033] According to the matching results, the vulnerability to be implanted is determined.

[0034] A second aspect of an embodiment of the present application provides a network security vulnerability implantation device, the device comprising:

[0035] A first acquisition unit, used to acquire a vehicle digital twin model;

[0036] A first processing unit, configured to identify key interfaces of a network connection module in the vehicle digital twin model;

[0037] A second processing unit is used to perform risk assessment on the key interfaces of the network connection module to obtain a risk assessment result;

[0038] A third processing unit is used to determine a key interface where a vulnerability is to be implanted according to the risk assessment result;

[0039] A fourth processing unit is used for the key interface of the vulnerability to be implanted, and determines the vulnerability to be implanted;

[0040] The fifth processing unit is used to implant the vulnerability to be implanted into the key interface of the vulnerability to be implanted.

[0041] A third aspect of an embodiment of the present application provides an electronic device, comprising a processor, an input device, an output device and a memory, wherein the processor, input device, output device and memory are interconnected, wherein the memory is used to store a machine program, the machine program includes program instructions, and the processor is configured to call the program instructions to execute the network security vulnerability implantation method as described in the first aspect.

[0042] Beneficial effects:

[0043] The present embodiment provides a method for implanting a security vulnerability and a related device, wherein, in the method, firstly, the network model of the acquired vehicle digital twin model is identified to identify the key interfaces of the networked model, and then the risk assessment is performed on these identified key interfaces to obtain the risk assessment results, thereby determining the key interfaces of the vulnerabilities to be implanted through the risk assessment results, and then matching the corresponding vulnerabilities to be implanted according to the characteristics of the key interfaces of the vulnerabilities to be implanted, and finally implanting the vulnerabilities to be implanted. Through this arrangement, system vulnerabilities that may exist in the real vehicle can be replicated in the digital twin model, so that the environment of the digital twin model at the network defense level is kept consistent with that of the real vehicle as much as possible, and the digital twin model is successively brought closer to the real vehicle, so as to solve the technical problem that the existing virtual simulation vehicle testing methods in the prior art mostly focus on the simulation of the physical characteristics of the vehicle, but do not pay enough attention to the vehicle at the network level, resulting in differences between the testing methods of the vehicle in the virtual simulation environment and the testing results of the real vehicle in the real environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1 A schematic diagram of the overall process of a network security vulnerability implantation method is provided for an embodiment of the present application;

[0046] Figure 2 A schematic diagram of the process of identifying key interfaces in a network security vulnerability implantation method is provided for an embodiment of the present application;

[0047] Figure 3 A schematic diagram of a process for risk assessment of key interfaces in a network security vulnerability implantation method is provided for an embodiment of the present application;

[0048] Figure 4 A schematic diagram of a process for determining a key interface to be implanted with a vulnerability in a network security vulnerability implantation method is provided for an embodiment of the present application;

[0049] Figure 5 A schematic diagram of a process of determining a vulnerability to be implanted according to a key interface of a vulnerability to be implanted in a network security vulnerability implantation method is provided for an embodiment of the present application;

[0050] Figure 6 A schematic diagram of the structure of a network security vulnerability implantation device is provided for an embodiment of the present application;

[0051] Figure 7 A structural schematic diagram of an electronic device is provided for an embodiment of the present application.

[0052] Reference numerals:

[0053] First acquisition unit-001, first processing unit-002, second processing unit-003, third processing unit-004, fourth processing unit-005, fifth processing unit-006. DETAILED DESCRIPTION

[0054] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0055] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0056] Reference to "embodiments" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments.

[0057] In order to better understand the network security vulnerability implantation method provided by the embodiment of the present application, the following first briefly introduces the scenario of applying the network security vulnerability implantation method. The application scenario of this embodiment is mainly the scenario of adjusting the vehicle digital twin model after the vehicle digital twin model is constructed. The vehicle digital twin model is used to simulate the test of the vehicle in reality. Before applying the method provided by this embodiment, the constructed vehicle digital twin model focuses on the simulation of the physical characteristics of the vehicle during modeling, and the simulation of the vehicle network is not considered, so the final test results may deviate from the actual test results.

[0058] In summary, in order to solve the technical problem that the existing virtual simulation vehicle testing methods in the prior art mostly focus on the simulation of the physical characteristics of the vehicle, but do not pay enough attention to the vehicle at the network level, resulting in differences between the test results of the vehicle in the virtual simulation environment and the test results of the real vehicle in the real environment, such as Figure 1 As shown, this embodiment provides a network security vulnerability implantation method, including:

[0059] S1. Obtain a vehicle digital twin model;

[0060] S2. Identify the key interfaces of the network connection module in the vehicle digital twin model. This embodiment is preferred, such as Figure 2 As shown, specifically including:

[0061] S201. Construct a vehicle network topology map based on the vehicle digital twin model.

[0062] S202. Determine the data transmission parameters between the k initial networked modules in the vehicle digital twin model according to the vehicle network topology diagram, wherein the data transmission parameters include data transmission frequency, data size, data priority, data transmission sensitivity and data transmission real-time index.

[0063] S203. Calculate the importance scores of k initial network connection modules according to the data transmission parameters to obtain an importance score set. As a preferred solution of this embodiment, the calculation formula of the importance score is as follows:

[0064]

[0065] Among them, S is the importance score, w f is the frequency weight of data transmission, w s is the size weight of data transmission, w p is the weight of data priority, w c is the sensitivity weight of data transmission, w r is the weight of the real-time data transmission, f is the frequency of data transmission, s is the size of data transmission, p is the data priority, c is the sensitivity index of the data, and r is the real-time index of data transmission. Through the calculation formula of the above importance score value, the importance score value in the vehicle network topology diagram can be calculated in turn.

[0066] S204. Based on the importance score value set, m key networked modules are determined from the k initial networked modules. Therefore, by comparing the comprehensive importance score values, the interfaces that have the greatest impact on the vehicle network module can be determined. By confirming these interfaces as key interfaces, the deviation between the test results of the vehicle in a virtual environment through the digital twin model and the actual vehicle test results can be reduced while reducing the processing load.

[0067] S205: Determine the interface corresponding to each key networking module in the m key networking modules as a key interface.

[0068] As another preferred scheme of this embodiment, in addition to steps S201-S205 provided in this embodiment as a display method, in addition to this method, methods such as data flow analysis methods, communication protocol analysis methods, interface protocol analysis methods, interface specification review methods, functional safety analysis, attack surface analysis, expert review methods and historical data analysis methods can also be used to identify and analyze key interfaces. This embodiment uses the importance assessment method for identification only as an example and is not limiting.

[0069] S3. Perform risk assessment on the key interfaces of the network connection module to obtain risk assessment results. In this embodiment, it is preferred that Figure 3 As shown, including:

[0070] S301, configure the traffic device to simulate the attack vector;

[0071] S302, acquiring the attack vectors used to attack the key interface until the number of attacks and the post-attack status when the key interface is breached, and obtaining an attack result data set;

[0072] S303, calculating the attack vector defense coefficient of each of the key interfaces according to the attack result data set;

[0073] S304: Determine the risk assessment result of each of the key interfaces according to the attack vector defense coefficient.

[0074] S4. Determine the key interface to implant the vulnerability according to the risk assessment result, as a preferred solution of this embodiment, including:

[0075] S401, determining the key interfaces of the network connection module according to the risk assessment result to perform risk level assessment and obtain a risk assessment level;

[0076] S402, randomly extracting a preset number of the key interfaces from the risk assessment levels to obtain a screening key interface data set;

[0077] S403, the key interfaces in the filtered key interface data set are determined as the key interfaces to be implanted with vulnerabilities. In this embodiment, the key interfaces to be implanted with vulnerabilities are preferably determined as the DSRC communication interface of the V2X module, the OBD-II diagnostic interface, the software update mechanism interface of the CCU, and the Wi-Fi interface of the vehicle infotainment system as the key interfaces to be implanted with vulnerabilities.

[0078] S5. Determine the vulnerability to be implanted according to the key interface of the vulnerability to be implanted. Specifically, this embodiment preferably includes:

[0079] S501, extracting a vulnerability data set from a security vulnerability database;

[0080] S502. Match the key interface where the vulnerability is to be implanted with the vulnerability data set to obtain a matching result. Specifically, the matching process includes: first analyzing the characteristics of the target system to understand the functions and architecture of the target components of the current joint interface; then considering the attack surface and threat model; studying the historical vulnerability data and trends of the current joint interface; finally evaluating the potential impact, and then evaluating the severity of the current vulnerability based on the potential impact, and then matching the exploitable vulnerability with the current key interface to obtain a matching result.

[0081] S503: Determine the vulnerability to be implanted according to the matching result.

[0082] S6. Implant the vulnerability to be implanted into the key interface of the vulnerability to be implanted. This embodiment is preferred. This embodiment demonstrates the implantation process of 4 vulnerabilities as follows:

[0083] For implanting vulnerabilities in the interface of the Wi-Fi module of the connected vehicle, the preferred embodiment uses the GNU debugger to inject vulnerabilities, including:

[0084] First, identify the key functions in the Wi-Fi protocol stack that process input data to locate the target;

[0085] Deliberately omitting input length checks in data processing functions to create vulnerable conditions;

[0086] Use a buffer of predefined size to store input data to allocate a fixed buffer;

[0087] Use unsafe string copy functions to allow writing data beyond the buffer boundaries, thereby copying unsafe data;

[0088] Keep other processing logic of the connected vehicle Wi-Fi module unchanged to ensure normal functionality.

[0089] Vulnerabilities were implanted in the interfaces of the V2X-DSRC message authentication module, including:

[0090] First, identify the key functions responsible for verifying V2X messages;

[0091] Use weak encryption algorithms to replace existing strong encryption methods;

[0092] Embed fixed encryption keys in the code without using secure key management;

[0093] Remove and / or simplify some verification steps, use timestamp checks or replay protection;

[0094] Ensure that the modified function interface is the same as the original function, avoid changes in other parts of the system, and ensure stability. This embodiment is preferred, and specifically, the implementation steps include:

[0095] Use IDA Pro to open the binary file of the V2X program that needs to be modified;

[0096] Find the key functions responsible for verifying V2X messages in IDA Pro, such as VerifyMessage;

[0097] Open the source code file associated with the function in Visual Studio Code;

[0098] Find the code block responsible for verification in the source code file, such as if (VerifySignature (message, signature));

[0099] Replace the VerifySignature function with a function that uses a weak encryption algorithm, such as VerifySignature_Weak;

[0100] Implement a weak encryption algorithm, such as RC4, in the VerifySignature_Weak function;

[0101] Replace fixed encryption keys with hard-coded keys;

[0102] Simplify the verification process, such as removing timestamp checks or replay protection;

[0103] Keep the interface consistent and make the modified function interface the same as the original function;

[0104] Save the modified source code file and recompile to generate a new binary file.

[0105] In this embodiment, for the OBD-II interface, an insufficient access control vulnerability is implanted, specifically including:

[0106] Open the hardware design file that contains the OBD-II interface design.

[0107] Find the connection point of the OBD-II interface in the design files and check if there is any physical locking or shielding mechanism.

[0108] If present, remove or bypass it.

[0109] Locate additional circuit elements in the design files that may be used to restrict access and remove or simplify them.

[0110] Ensure that the modified interface design still complies with the OBD-II standard to maintain basic functionality.

[0111] Remove any references or requirements to access control from design documents.

[0112] Save the modified design file.

[0113] As a preferred solution of this embodiment, a CCU software update signature verification vulnerability is implanted, including:

[0114] Use IDA Pro to open the binary file of the CCU program that needs to be modified.

[0115] In IDA Pro, find the function responsible for verifying the signature of the software update package, such as VerifySignature.

[0116] Open the source code file associated with the function in Visual Studio Code.

[0117] Find the code block responsible for verification in the source code file, such as if (VerifySignature (package)).

[0118] Add a conditional check to the function to check if the file size meets a certain threshold.

[0119] If the file size meets this threshold, signature verification is skipped.

[0120] Choose a threshold that seems reasonable but actually causes security issues, such as file size exceeding 2KB.

[0121] Add logic to the conditional judgment and retain the original signature verification logic for situations where special conditions are not met.

[0122] Add misleading comments in the code explaining this "optimization" and making it look like a performance improvement.

[0123] Save the modified source code file and recompile to generate a new binary file.

[0124] As a preferred solution of this embodiment, it also includes:

[0125] S7. Perform vulnerability verification test to verify each implanted vulnerability. For the four implanted vulnerabilities, the verification process is as follows:

[0126] a) Wi-Fi Buffer Overflow:

[0127] Use Wireshark to capture Wi-Fi traffic and determine the IP address and port of the vehicle infotainment system.

[0128] Write a Python script to generate an extra-long Wi-Fi packet whose length exceeds the packet size limit of the Wi-Fi protocol.

[0129] Use the Wi-Fi simulator tool to send the generated extra-long data packets to the in-vehicle infotainment system.

[0130] Observe whether the system crashes or executes arbitrary code, and record relevant logs or memory dump files.

[0131] Analyze logs or memory dump files to determine if there is a buffer overflow vulnerability.

[0132] b) V2X-DSRC authentication bypass:

[0133] Use Wireshark or similar tool to capture V2X messages.

[0134] Analyze captured V2X messages to understand their format and structure.

[0135] Generate a forged V2X message using a known fixed key, ensuring that its format is consistent with the captured V2X message.

[0136] Use Wireshark to send a fake V2X message to the vehicle’s V2X module.

[0137] Observe the vehicle’s response to verify acceptance of the forged V2X message.

[0138] c) OBD-II Unauthorized Access:

[0139] Physically connect to the OBD-II port

[0140] Attempts to send diagnostic commands and read sensitive data

[0141] Confirm whether access is possible without authentication

[0142] d) CCU update vulnerability:

[0143] You can use Python scripts to construct malicious update packages larger than 1MB

[0144] Use of invalid signatures, including: using incorrect or expired signing keys, using randomly generated signatures, using unauthorized signing keys to sign malicious update packages, etc.

[0145] Try to install the update package to the CCU via OTA or wired flash.

[0146] Verify that the signature check is bypassed.

[0147] S8. Record the vulnerabilities and mark them for explanation. This embodiment takes the above four vulnerability processes as examples, as follows:

[0148] Example record (for Wi-Fi vulnerability):

[0149] Vulnerability ID: CVE-2023-XXXX

[0150] Target component: In-vehicle infotainment system Wi-Fi module

[0151] Vulnerability Type: Buffer Overflow (CWE-120)

[0152] Description: A stack buffer overflow vulnerability exists when processing Wi-Fi packets. An attacker can trigger this vulnerability by sending specially crafted Wi-Fi packets.

[0153] Impact: Could result in denial of service or remote code execution.

[0154] CVSS score: 8.8 (High).

[0155] Exploitation conditions: The attacker needs to be within the vehicle's Wi-Fi range.

[0156] Detection method: By sending extremely long Wi-Fi packets and monitoring the system response.

[0157] Mitigation: Update Wi-Fi firmware to add input validation and length checks.

[0158] S9. Implement mitigation strategies for each vulnerability. In this preferred embodiment, examples of the above four vulnerabilities are given, including:

[0159] a) Wi-Fi Buffer Overflow:

[0160] Update Wi-Fi driver and add input length check

[0161] Implementing Address Space Layout Randomization (ASLR)

[0162] Enable Data Execution Prevention (DEP)

[0163] b) V2X-DSRC authentication vulnerability:

[0164] Implement dynamic key exchange based on Public Key Infrastructure (PKI)

[0165] Add message timestamp and anti-replay mechanism

[0166] Regularly rotate encryption keys

[0167] c) OBD-II Unauthorized Access:

[0168] Add physical access controls, such as locking mechanisms

[0169] Implement role-based access control (RBAC)

[0170] Add abnormal access detection and alarm mechanism

[0171] d) CCU update vulnerability:

[0172] Fixed the signature verification logic to ensure that all update packages are verified

[0173] Implement multi-factor authentication

[0174] Added update package integrity check.

[0175] S10. Update the system security baseline based on discovered vulnerabilities and developed mitigation strategies, including:

[0176] Software Development Specifications: Add mandatory requirements for buffer overflow protection measures, including:

[0177] a) Buffer overflow protection:

[0178] Enforce the use of safe string and memory handling functions (such as strncpy, snprintf, etc.).

[0179] Requires that all array operations include bounds checking.

[0180] Forces compiler warnings and error checking to be enabled (like gcc's -Wall-Wextra-Werror option).

[0181] Requires that all code be checked using a static code analysis tool such as Coverity or SonarQube.

[0182] b) Input Validation:

[0183] It is required that all external inputs must be strictly validated and sanitized.

[0184] Define and use a safe input handling library.

[0185] c) Error handling:

[0186] Requires that all function return values ​​be checked and handled appropriately.

[0187] Disable detailed error messages in production environments.

[0188] d) Secure Coding Training:

[0189] Require all developers to attend secure coding training at least once a year.

[0190] Cryptography Usage Policy: Prohibit the use of hard-coded keys and require the use of strong encryption algorithms, including:

[0191] a) Key Management:

[0192] Hard-coding keys in code is prohibited.

[0193] Requires that all keys be stored in a secure hardware module such as a TPM or HSM.

[0194] Implement an automatic key rotation mechanism at least every 90 days.

[0195] b) Encryption algorithm:

[0196] It is stipulated that only proven strong encryption algorithms (such as AES-256, RSA-2048 or higher) can be used.

[0197] It is forbidden to use encryption algorithms with known vulnerabilities (such as MD5, SHA-1).

[0198] Physical security requirements: Add physical access control requirements for diagnostic interfaces, including:

[0199] a) Diagnostic interface control:

[0200] All OBD-II interfaces must have a physical locking mechanism.

[0201] Specify that only authorized personnel can access the diagnostic interface and require that all access be logged.

[0202] b) Equipment safety:

[0203] All key hardware components (such as ECUs) must have anti-tampering mechanisms.

[0204] Security screws and seals are specified to prevent unauthorized physical access.

[0205] c) Storage media security:

[0206] Requires that all removable storage media must be encrypted.

[0207] Mandate secure erasure when devices are scrapped.

[0208] Software update process: All update packages must be verified for integrity and signature. Specifically, the following are required:

[0209] a) Update package verification:

[0210] All update packages must be digitally signed.

[0211] Mandate the use of multiple authentication mechanisms, including hash verification and version control.

[0212] b) Update process:

[0213] A rollback mechanism is required to be implemented in case of update failure.

[0214] It is required that important updates must be approved by multiple people.

[0215] c)Test requirements:

[0216] Requires that all updates be thoroughly tested in an isolated environment.

[0217] Requires automated regression testing.

[0218] Network security architecture: Implement a defense-in-depth strategy and increase network segmentation, including:

[0219] Network segmentation:

[0220] It is required to divide the in-vehicle network into multiple security domains (such as infotainment, driving control, and diagnosis).

[0221] It is stipulated that the communication between different security domains must be strictly controlled and monitored.

[0222] b) Firewall configuration:

[0223] It is required to deploy firewalls at key network interfaces.

[0224] It is stipulated that the principle of least privilege should be implemented and only necessary ports and services should be opened.

[0225] c) Wireless Security:

[0226] Requires that all wireless communications (such as Wi-Fi, Bluetooth) must use strong encryption.

[0227] Make it a rule to change your wireless network password regularly.

[0228] Security monitoring: Deploy intrusion detection systems (IDS) and security information and event management (SIEM) systems, including:

[0229] a) Intrusion Detection System (IDS):

[0230] It is required to deploy IDS at key network nodes.

[0231] It is stipulated that IDS must be able to detect known and unknown threats.

[0232] b) Security Information and Event Management (SIEM):

[0233] It is required to deploy a SIEM system to centrally manage and analyze security logs.

[0234] It is stipulated that SIEM must be able to generate real-time alerts and regular reports.

[0235] c) Log management:

[0236] Require all systems and applications to generate detailed security logs.

[0237] It is stipulated that logs must be kept for at least 6 months and backed up regularly.

[0238] Regular security assessments: Require comprehensive security vulnerability scans and penetration tests every quarter.

[0239] That is, this embodiment provides a method for implanting security vulnerabilities. First, the network model of the acquired vehicle digital twin model is identified to identify the key interfaces of the networked model. Then, risk assessment is performed on these identified key interfaces to obtain risk assessment results. Through the risk assessment results, the key interfaces of the vulnerabilities to be implanted are determined. Then, the corresponding vulnerabilities to be implanted are matched according to the characteristics of the key interfaces of the vulnerabilities to be implanted. Finally, the vulnerabilities to be implanted are implanted. Through this setting, system vulnerabilities that may exist in the real vehicle can be replicated in the digital twin model, so that the environment of the digital twin model at the network defense level is kept consistent with that of the real vehicle as much as possible, and the digital twin model is brought closer to the real vehicle in turn, so as to solve the technical problem that the existing virtual simulation vehicle testing methods in the prior art mostly focus on the simulation of the physical characteristics of the vehicle, but do not pay enough attention to the vehicle at the network level, resulting in differences between the testing methods of the vehicle in the virtual simulation environment and the testing results of the real vehicle in the real environment.

[0240] For the above embodiments, please refer to Figure 7 , Figure 7 A structural schematic diagram of an electronic device provided in an embodiment of the present application, as shown in the figure, includes a processor, an input device, an output device and a memory, the processor, the input device, the output device and the memory are interconnected, wherein the memory is used to store a computer program, the computer program includes program instructions, the processor is configured to call the program instructions, and the program includes instructions for executing the following steps;

[0241] S1. Obtain a vehicle digital twin model;

[0242] S2. Identify key interfaces of the network connection module in the vehicle digital twin model;

[0243] S3. Perform risk assessment on the key interfaces of the network connection module to obtain risk assessment results;

[0244] S4. Determine the key interface to implant the vulnerability based on the risk assessment result;

[0245] S5. Determine the vulnerability to be implanted according to the key interface of the vulnerability to be implanted;

[0246] S6. Implant the vulnerability to be implanted into the key interface of the vulnerability to be implanted.

[0247] The above mainly introduces the scheme of the embodiment of the present application from the perspective of the execution process on the method side. It is understandable that, in order to realize the above functions, the electronic device includes a hardware structure and / or software module corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments provided herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware 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 application.

[0248] The embodiment of the present application can divide the terminal into functional units according to the above method example. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0249] In line with the above, see Figure 6 , Figure 6 The present invention provides a schematic diagram of a network security vulnerability implantation device. Figure 6 As shown, the device comprises:

[0250] The first acquisition unit 001 is used to acquire a vehicle digital twin model;

[0251] The first processing unit 002 is used to identify the key interface of the network connection module in the vehicle digital twin model;

[0252] The second processing unit 003 is used to perform risk assessment on the key interfaces of the network connection module to obtain a risk assessment result;

[0253] The third processing unit 004 is used to determine the key interface where the vulnerability is to be implanted according to the risk assessment result;

[0254] The fourth processing unit 005 is used to determine the vulnerability to be implanted according to the key interface of the vulnerability to be implanted;

[0255] The fifth processing unit 006 is used to implant the vulnerability to be implanted into the key interface of the vulnerability to be implanted.

[0256] An embodiment of the present application also provides a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of any one of the xx methods recorded in the above method embodiments.

[0257] An embodiment of the present application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program enables a computer to execute part or all of the steps of any one of the xx methods recorded in the above method embodiments.

[0258] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0259] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0260] In the several embodiments provided in the present application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only schematic, such as the division of the units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the device or unit can be electrical or other forms.

[0261] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0262] In addition, the functional units in the various embodiments of the application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware or in the form of software program modules.

[0263] If the integrated unit is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, disk or optical disk and other media that can store program codes.

[0264] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable memory, which can include: a flash drive, a read-only memory, a random access memory, a magnetic disk or an optical disk, etc.

[0265] The embodiments of the present application are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core idea of ​​the present application. At the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A network security vulnerability implantation method, characterized in that: include: Obtain vehicle digital twin model; Identify key interfaces of the connected modules in the vehicle digital twin model; Performing risk assessment on key interfaces of the network connection module to obtain risk assessment results; Determine the key interface where the vulnerability is to be implanted based on the risk assessment results; Determine the vulnerability to be implanted according to the key interface of the vulnerability to be implanted; Implant the vulnerability to be implanted into the key interface of the vulnerability to be implanted.

2. The network security vulnerability implantation method according to claim 1, characterized in that: Identify the key interfaces of the connected modules in the vehicle digital twin model, including: Build a vehicle network topology diagram based on the vehicle digital twin model; Determine, according to the vehicle network topology diagram, data transmission parameters between k initial network modules in the vehicle digital twin model; Calculating importance scores of k initial network connection modules according to the data transmission parameters to obtain an importance score value set; Based on the importance score value set, determining m key network modules from the k initial network modules; The interface corresponding to each key networking module in the m key networking modules is determined as a key interface.

3. The network security vulnerability implantation method according to claim 2, characterized in that: According to the data transmission parameters, the importance scores of the k initial network connection modules are calculated to obtain an importance score set. The calculation formula of the importance score is as follows: Among them, S is the importance score, w f is the frequency weight of data transmission, w s is the size weight of data transmission, w p is the weight of data priority, w c is the sensitivity weight of data transmission, w r is the weight of the real-time data transmission, f is the frequency of data transmission, s is the size of data transmission, p is the data priority, c is the sensitivity index of the data, and r is the real-time index of data transmission.

4. The network security vulnerability implantation method according to claim 1, characterized in that: Perform risk assessment on the key interfaces of the network connection module to obtain risk assessment results, including: Configure the traffic controller to simulate attack vectors; Acquire the attack vectors used to attack the key interface until the key interface is breached, and the number of attacks and the post-attack status to obtain the attack result data set; Calculating the attack vector defense coefficient of each of the key interfaces according to the attack result data set; According to the attack vector defense coefficient, the risk assessment result of each of the key interfaces is determined.

5. The network security vulnerability implantation method according to claim 1, characterized in that: Based on the risk assessment results, determine the key interfaces where vulnerabilities are to be implanted, including: Determine the key interfaces of the network connection module according to the risk assessment results to perform risk level assessment and obtain a risk assessment level; Randomly extracting a preset number of the key interfaces from the risk assessment levels to obtain a screening key interface data set; The key interfaces in the key interface data set are screened and determined as the key interfaces to be implanted with vulnerabilities.

6. The network security vulnerability implantation method according to claim 1, characterized in that: According to the key interface of the vulnerability to be implanted, determine the vulnerability to be implanted, including: Extract vulnerability datasets from security vulnerability databases; Matching the key interface of the vulnerability to be implanted with the vulnerability data set to obtain a matching result; According to the matching results, the vulnerability to be implanted is determined.

7. A network security vulnerability implantation device, characterized in that: The device comprises: A first acquisition unit, used to acquire a vehicle digital twin model; A first processing unit, configured to identify key interfaces of a network connection module in the vehicle digital twin model; A second processing unit is used to perform risk assessment on the key interfaces of the network connection module to obtain a risk assessment result; A third processing unit is used to determine a key interface where a vulnerability is to be implanted according to the risk assessment result; A fourth processing unit is used for the key interface of the vulnerability to be implanted, and determines the vulnerability to be implanted; The fifth processing unit is used to implant the vulnerability to be implanted into the key interface of the vulnerability to be implanted.

8. An electronic device, characterized in that: It includes a processor, an input device, an output device and a memory, which are interconnected, wherein the memory is used to store a machine program, the machine program includes program instructions, and the processor is configured to call the program instructions to execute the network security vulnerability implantation method as described in any one of claims 1-6.

9. A computer storage medium, characterized in that: The computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of the network security vulnerability implantation method as described in any one of claims 1 to 6.

Images