Device and method for updating software
The software update device with a risk management unit and control unit ensures that vehicle software updates are within acceptable risk ranges, addressing inefficiencies in existing processes and enhancing cybersecurity by prohibiting updates that may compromise vehicle security.
Patent Information
- Application Number
- PCT/JP2024/014253
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-01
- Filing Date
- 2024-04-08
- Publication Date
- 2024-11-07
AI Technical Summary
Existing software update processes for vehicles are inefficient in addressing cybersecurity vulnerabilities, particularly in ensuring that updates are within the acceptable risk tolerance range over time, and do not effectively prevent updates that may compromise vehicle security.
A software update device with a risk management unit that manages vulnerability information and risk tolerance conditions, including a software update control unit that prohibits updates if they do not meet permissible conditions, ensuring that updates are within the acceptable risk range.
The solution enables determination of whether updated content is within the risk tolerance range, reducing the risk to vehicle security and preventing updates that may compromise the system, thereby enhancing cybersecurity.
Smart Images

Figure JP2024014253_07112024_PF_FP_ABST
Abstract
Description
Software update device and method
[0001] The present invention relates to a software update apparatus and method for managing software updates for target devices.
[0002] In recent years, there has been an increasing demand for ensuring cybersecurity safety in electronic control units (ECUs) installed in vehicles and the like due to improvements in autonomous driving technology and the rise of communication technologies such as OTA (Over The Air).
[0003] In particular, if any vulnerability is discovered in a product, there is a risk that tens of thousands of vehicles could be affected by cyber attacks targeting that vulnerability, so a prompt response is required.
[0004] An organization called PSIRT (Product Security Incident Response Team) is established within the vehicle manufacturer (OEM: Original Equipment Manufacturer). The PSIRT obtains public vulnerability information and industry vulnerability information from various industry organizations, and works with each department within the OEM to investigate whether any of the suppliers have products that are vulnerable to the obtained vulnerabilities.
[0005] When a product is found to be vulnerable, PSIRT conducts various evaluation tests, such as risk assessments and reproduction tests, to investigate the severity of the vulnerability. If the impact is determined to be very severe, feedback is provided to the development project to update the product specifications. Finally, to accommodate products already on the market, software is reprogrammed, for example, via OTA, and the products are fixed before shipping.
[0006] However, in reality, the above process is extremely difficult, and even if a vulnerability is discovered after a product has been shipped, it is not easy to update the software to address the vulnerability, as it takes several months to investigate the impact of software changes.
[0007] Furthermore, the above-mentioned demand for improved cybersecurity is also the result of the enforcement of relevant laws and regulations, but these laws do not require the immediate removal of discovered vulnerabilities, but rather require accountability based on the results of risk assessments of those vulnerabilities.
[0008] On the other hand, vehicles are expected to be in operation for long periods of time, typically nearly 20 years, and it is possible that conditions that were initially determined to be tolerable in terms of risk when a vulnerability was discovered may fall outside the acceptable risk range during subsequent operation.
[0009] An example of a technology for such risk management is Patent Document 1. This document describes an invention relating to a threat information analysis server that includes a risk level update unit that associates threat information with the risk level of an IoT device based on update information and updates related threat information, and an output unit that outputs related threat information managed by the related threat information management unit.
[0010] International Publication No. 2020 / 080222
[0011] However, even if the technology described in Patent Document 1 is used, it is not possible to make a determination that corresponds to the risk tolerance range that changes over time, as described above.
[0012] The present invention has been made in consideration of the above problems, and aims to provide a software update device that can determine whether the update content is within an acceptable risk range when updating software for a target device installed in a vehicle, etc. Further features related to the present invention will become apparent from the description of this specification and the accompanying drawings. In addition, problems, configurations, and effects other than those described above will become apparent from the description of the following embodiments.
[0013] In order to solve the above problem, a software update device according to one embodiment of the present invention includes a risk management unit that manages vulnerability information of a target device and acceptable conditions for risks in the vulnerability information, and a software update control unit that prohibits a software update when it is determined that the update content does not satisfy the acceptable conditions when a software update is performed on the target device.
[0014] According to the present invention, when updating software of a target device installed in a vehicle or the like, it is possible to determine whether the update content is within an acceptable risk range. Further features related to the present invention will become apparent from the description of this specification and the accompanying drawings. Furthermore, problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments.
[0015] 1 is a block diagram showing the functional configuration of a software update device according to an embodiment of the present invention and its relationship with external organizations. A diagram explaining the processing (events) expected after a vulnerability is discovered. A flowchart showing the processing executed when updating software. A diagram showing the processing for updating risk management information after a vulnerability is discovered. A diagram explaining the updated content of risk management information. A diagram showing the processing for updating software. A diagram showing risk tolerance conditions referenced when updating software. A flowchart showing the verification processing of risk tolerance conditions executed when updating software. A diagram showing the processing for applying a vulnerability patch. A diagram showing the applied content of a vulnerability patch. A diagram explaining the updated content of risk management information. A block diagram showing the functional configuration of a software update device according to a modified example of the present invention and its relationship with external organizations.
[0016] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0017] 1 is a block diagram showing the functional configuration of a software update device according to an embodiment of the present invention and its relationship with external organizations. The software update device according to this embodiment is implemented as a central gateway (CGW) 100 device in a vehicle.
[0018] The software update device 100 according to this embodiment includes, as its functional units, a communication unit 11, a risk management unit 12, a software update control unit 13, a risk verification unit 14, a risk update unit 15, an update information acquisition unit 16, and an update content determination unit 17, and also includes, as a storage unit, risk management information 18. The risk management information 18 includes relevant vulnerabilities 19 and risk tolerance conditions 20.
[0019] The software update device 100 also receives risk tolerance conditions and update programs from the OEM / supplier 200 via the OTA center 300, accepts application / service updates from the service provider / user 400, and receives update programs from the dealer 500.
[0020] The software update device 100 includes a CPU (not shown), a ROM (not shown), and a RAM (not shown), and the following functions are realized by the CPU expanding a program stored in the ROM into the RAM and executing it.
[0021] The communication unit 11 transmits and receives information to and from external organizations. The risk management unit 12 manages vulnerability information and the risk tolerance conditions in the vulnerability information. The software update control unit 13 controls software updates. The risk verification unit 14 verifies whether the software update satisfies the risk tolerance conditions. The risk update unit 15 updates the risk tolerance conditions based on the update information of the tolerance conditions. The update information acquisition unit 16 acquires update programs via the communication unit 11. The update content determination unit 17 determines whether to update the tolerance conditions or update the software when a software update request is received. The relevant vulnerabilities 19 and risk tolerance conditions 20 contained in the risk management information 18 will be described later.
[0022] 2 is a diagram for explaining several patterns that may occur after a vulnerability is discovered in a product. Note that the present invention is based on the premise that the risk of a vulnerability discovered in a product will be tolerated at least once.
[0023] Once a vulnerability is discovered and the risk is accepted, there are three possible outcomes: (1) updating the program, (2) applying a vulnerability patch, or (3) discovering a new vulnerability.
[0024] A flowchart illustrating the above process is shown in Figure 3. After determining the risk acceptability of the discovered vulnerability, when the software update device receives a program, the software update control unit 13 checks the update type (step S301). Here, it is determined whether the program is an update to risk management information (step S302), and if it is an update to risk management information, the update is executed (step S303).
[0025] If the program is not an update of risk management information, it is next determined whether the program is related to a program update or a vulnerability patch update (step S304). If it is related to a program update, the process proceeds to the above-mentioned stage (1), and the program update / update prohibition process of steps S306 to S309 is performed. If it is related to patch update processing, the process proceeds to stage (2), and the patch update process of step S305 is performed. These processes will be described in detail later. If a new vulnerability is discovered after these processes, the process proceeds to the above-mentioned stage (3).
[0026] The process executed when a vulnerability is first discovered and after a risk tolerance decision is made will be described with reference to Figures 4 and 5. Figure 4 is a chart showing the risk management information update process, and Figure 5 is a diagram for explaining the update contents.
[0027] First, the OEM / supplier that has determined the risk tolerance generates new risk management information (step S401) and performs the update package generation process (step S402). An update package is a collection of update types, relevant vulnerabilities, and risk tolerance conditions. The update type is an identifier that indicates the type of update content. Update content includes, for example, risk management information updates, program updates, vulnerability patch updates, etc.
[0028] The generated package is sent to the OTA center (step S403), and then to the vehicle's software update device, which simultaneously starts the package update process (steps S404 and S405). The software update device checks the update type of the software included in the package (step S406), and updates its own risk management information 18 (step S407).
[0029] A specific example of updated risk management information will be described with reference to Fig. 5. As shown in Fig. 5, the risk management information includes relevant vulnerabilities and risk tolerance conditions. Here, it is assumed that no information is registered in the relevant vulnerabilities and risk tolerance conditions before the update, as shown in Figs. 5(a) and 5(c).
[0030] Let us assume that the received package contains information such as "Vulnerability ID: CVE-2022-AAA, Countermeasure Status: Risk Retained" as shown in Figure 5(b). This means that the vulnerability identified by the ID has been discovered, but the risk posed by this vulnerability has been determined to be tolerable (it does not pose a threat even if left unattended).
[0031] In this case, the package contains information like that shown in Figure 5(d) as its risk tolerance conditions. This means that the risk tolerance type is "Alternative with existing countermeasures" and the tolerance condition is "Countermeasure A" which has already been implemented in the product, and that the risk of the newly discovered vulnerability can be tolerated by this countermeasure. Also, the risk tolerance type is "No attack path applicable" and the tolerance condition is "No remote service" means that there is no remote (wireless) access path to the product, meaning that there is no risk of it being targeted by attackers, and therefore the risk is tolerable.
[0032] Next, the process of executing a program update after the initial risk acceptance decision described above, that is, the process at stage (1) in FIG. 2, will be described with reference to FIGS.
[0033] 6, first, the OEM / supplier generates risk impact details related to the vulnerabilities that it has accepted as risks (step S601), and then generates a package (step S602). The package includes the update type, risk impact details, and update program.
[0034] The generated package is sent to the dealer / OTA center (step S603), and is also sent to the vehicle's software update device, which simultaneously starts the package update process (steps S604 and S605).
[0035] The software update device that receives the package unpacks the package and checks the update type (step S606). This step corresponds to step S304 in the flowchart shown in Figure 3. Here, it is assumed that the update type is a program update rather than a patch update. That is, the process proceeds to step S306 in the flowchart shown in Figure 3.
[0036] The software update device then verifies the risk tolerance conditions (step S607). This step corresponds to step S306 in the flowchart of Fig. 3. Then, depending on the verification results, the software update device performs a program update process or update prohibition process (step S608).
[0037] The verification of the risk tolerance conditions will be explained using Figures 7 and 8. In verifying the risk tolerance conditions, it is necessary to consider the risk impact details shown in Figure 7(b) in addition to the relevant vulnerabilities and risk tolerance conditions already explained and shown in Figures 7(a) and (c).
[0038] The risk impact details indicate the scope and details of the impact when an update program included in the package is executed. In this embodiment, executing the update program will have an impact on the in-vehicle device ECU_1, and the impact details are registered as "Impact type: attack path not applicable" and "Impact details: no remote service (remote service added)." This means that when this update program is executed, a remote service that can be accessed by the in-vehicle device ECU_1 will be added.
[0039] Here, the risk acceptance condition in FIG. 7(c) is referenced. Before the program update, the risk of the vulnerability in ECU_1 identified by vulnerability ID: CVE-2022-AAA was accepted because the acceptance condition: no remote services was valid. However, considering the risk impact described above, a remote service that can access ECU_1 would be added, which would invalidate the validity of that condition. Therefore, a program update that has such an impact is prohibited. If the validity of the condition is not invalidated, the program update may be executed.
[0040] The above process will be explained using the flowchart in Figure 8. First, the software update device checks the contents of the received package and determines whether or not there are any vulnerabilities that pose a risk (step S801). If it is determined that there are no vulnerabilities that pose a risk, this means that there is no need to consider risk tolerance, and so the program update process is executed (step S807).
[0041] If there is a vulnerability that requires risk protection, the process proceeds to step S802, where the risk impact details as shown in Figure 7(b) are acquired. Then, the corresponding risk tolerance type is searched for in the risk management information (step S803). Next, it is determined whether or not there are valid risk tolerance conditions in the searched risk tolerance types (step S804). If there are no valid risk tolerance conditions, this means that there are no risk tolerance conditions that will be invalidated by the program update, and the program update process is executed (step S807).
[0042] If there are valid risk tolerance conditions, it is determined whether the program update will cause a deviation from the risk tolerance conditions (step S805). If there is no deviation, the risk tolerance conditions will remain satisfied even after the program is updated, so the program update is executed (step S807). If there is a deviation from the tolerance conditions, processing is executed to prohibit the program update (step S806). The above is the risk tolerance condition verification processing, which corresponds to steps S306 to S309 in the overall processing described in Figure 3.
[0043] In addition, regarding the program update prohibition process described above, there may be cases where a further detailed analysis of the prohibited software is conducted and it is determined that the prohibited software does not violate the risk tolerance conditions. In such cases, the program update using the prohibited software may be executed.
[0044] Next, the case where vulnerability patches are applied after the risk tolerance is first determined, that is, the case (2) in FIG. 2, will be described with reference to FIGS.
[0045] When applying a vulnerability patch, the OEM / supplier generates a risk avoidance range (step S901). The risk avoidance range indicates the range of vulnerabilities that can be avoided by applying the patch. Then, a package including this range is generated (step S902).
[0046] The generated package is sent to the dealer / OTA center (step S903), and then sent to the vehicle's software update device, which simultaneously starts the package update process (steps S904, S905).
[0047] The software update device unpacks the received package and checks the update type (step S906). In this case, the update type is a patch application, which does not affect the risk tolerance conditions, so the program update process is carried out as is (step S907). Finally, the risk management information that has been changed by the patch application is updated, and the process ends (step S908).
[0048] Figure 10 shows the risk avoidance range and the changed risk management information. In this example, the risk avoidance range was the vulnerability identified by vulnerability ID: CVE-2022-AAA, as shown in Figure 10(a). Then, by applying a patch to this vulnerability, the risk associated with this vulnerability is eliminated, so the corresponding vulnerability becomes "risk avoidance," as shown in Figures 10(b) and 10(c), and the risk tolerance conditions are also reset.
[0049] Finally, the case where a new vulnerability is discovered after the initial risk tolerance decision, that is, the case (3) in FIG. 2, will be described with reference to FIG.
[0050] When a new vulnerability is discovered, the corresponding vulnerability and risk tolerance conditions in the risk management information are updated as shown in Fig. 11. In this embodiment, as shown in Fig. 11(b), a new vulnerability identified by vulnerability ID: CVE-2022-BBB is discovered as the corresponding vulnerability, and as shown in Fig. 11(d), it can be seen that the risk tolerance type for the in-vehicle device ECU_2 is "substitution with existing measures" and the tolerance conditions are "measure B."
[0051] In the above description, the software update device is installed in the vehicle. However, as a modification of the present invention, it is also possible to provide the functionality of the software update device to an OTA center 300 that is communicably connected to the vehicle / ECU, as shown in FIG.
[0052] According to this embodiment, it is possible to perform processing collectively by the OTA center connected to a large number of vehicles / ECUs, and it is possible to achieve centralization of processing.
[0053] The above-described embodiment of the present invention provides the following advantageous effects: (1) A software update device according to an embodiment of the present invention includes a risk management unit that manages vulnerability information of a target device and acceptable conditions for risks in the vulnerability information, and a software update control unit that, when a software update is performed on the target device, prohibits the software update if it is determined that the update content does not satisfy the acceptable conditions.
[0054] With the above configuration, when updating the software of a target device installed in a vehicle, etc., it is possible to determine whether the update content is within an acceptable risk range, thereby preventing program updates that may pose a risk to the security of the vehicle.
[0055] (2) A risk verification unit is further provided to verify whether the update content satisfies the tolerance conditions when a software update is performed. The function of this risk verification unit makes it possible to compare the update content in (1) with the tolerance conditions.
[0056] (3) A risk update unit is further provided that updates the tolerance conditions based on update information for the tolerance conditions. The tolerance conditions for risks relate to whether or not software updates are possible, and therefore must always be kept up to date. Such a risk update unit is useful.
[0057] (4) The device further includes an update information acquisition unit that acquires update information for the acceptable conditions and updates to be used in the software update, and an update content determination unit that determines whether to execute an update of the acceptable conditions or a software update. Because the priority of updates of the acceptable conditions and software updates varies depending on their content, adopting such a configuration makes it possible to select an appropriate process.
[0058] (5) A software update method according to an embodiment of the present invention corresponds to the software update device of (1) and has the same effects as (1).
[0059] It should be noted that the present invention is not limited to the above-described embodiments, and various modifications are possible. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to embodiments that include all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment. It is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to delete part of the configuration of each embodiment, or to add or replace other configurations.
[0060] 12 Risk management unit, 13 Software update control unit, 14 Risk verification unit, 15 Risk update unit, 16 Update information acquisition unit, 17 Update content determination unit, 100 Software update device
Claims
1. A software update device comprising: a risk management unit that manages vulnerability information of a target device and acceptable conditions for risks in the vulnerability information; and a software update control unit that, when a software update is performed on the target device, prohibits the software update when it is determined that the update content does not satisfy the acceptable conditions.
2. A software update device as claimed in claim 1, further comprising a risk verification section which verifies whether the update contents satisfy the permissible conditions when the software update is performed.
3. A software update device according to claim 1, further comprising a risk update section that updates the acceptable conditions based on update information for the acceptable conditions.
4. A software update device as described in claim 3, further comprising: an update information acquisition unit that acquires update information for the acceptable conditions and an update program to be used for the software update; and an update content determination unit that determines whether to execute the update of the acceptable conditions or the software update.
5. A software update method comprising: acquiring vulnerability information of a target device and acceptable conditions for risks in the vulnerability information; and, when a software update is to be performed on the target device, prohibiting the software update if it is determined that the update contents do not satisfy the acceptable conditions.
Citation Information
Patent Citations
Vulnerability influence evaluation system
JP2020113090A
Software package update supporting device, method for updating software package, and software package update supporting program
JP2020135678A
Application development support system, and application development support method
JP2021157401A
Systems and methods for program code defect and acceptability for use determination
WO2022182440A1
