Software updating device and method
The software update device manages vulnerability information and risk tolerance conditions to ensure updates are within acceptable risk ranges, addressing inefficiencies in existing processes by prohibiting updates that violate risk tolerance, thereby enhancing vehicle security.
Patent Information
- Application Number
- JP2023075766
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-01
- Publication Date
- 2024-11-14
AI Technical Summary
Existing software update processes for vehicles are inefficient in addressing changing risk tolerance ranges over time, especially in the context of cyber vulnerabilities, and do not ensure that updates are within acceptable risk limits.
A software update device with a risk management unit and control unit that manages vulnerability information and risk tolerance conditions, prohibiting updates if they do not meet permissible conditions, and includes a verification unit to ensure updates are within acceptable risk ranges.
Enables determination of whether updated software content is within acceptable risk ranges, reducing the risk of cyber threats by preventing updates that violate risk tolerance conditions, thus enhancing vehicle security.
Smart Images

Figure 2024160595000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a software update apparatus and method for managing software updates for a target device. [Background technology]
[0002] In recent years, there has been an increasing demand for ensuring the cybersecurity safety of electronic control units (ECUs) installed in vehicles, etc. 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 rapid response is required.
[0004] An organization called PSIRT (Product Security Incident Response Team) is established in the vehicle manufacturer (OEM: Original Equipment Manufacturer). PSIRT obtains public vulnerability information and industry vulnerability information from various industry groups, and while working with each department within the OEM, investigates whether any of the suppliers have products that are subject to the obtained vulnerabilities.
[0005] If a product is found to be vulnerable, the PSIRT will conduct various evaluation tests, such as risk assessment and reproduction tests, to investigate the extent of the impact of the vulnerability. If the impact is determined to be very large, feedback is provided to the development project to update the product specifications. Finally, to accommodate products already on the market, software reprogramming is performed, for example, using OTA, and the shipped products are corrected.
[0006] However, in reality, the above process is extremely difficult, and even if a vulnerability is discovered after a product is shipped, it is not easy to update the software to address the vulnerability, because it takes several months to investigate the impact of software changes.
[0007] Furthermore, the above-mentioned requirement to improve cybersecurity is also a result of the enforcement of relevant laws and regulations, but these laws do not require the immediate removal of discovered vulnerabilities; rather, they require accountability based on the results of risk assessments of those vulnerabilities.
[0008] On the other hand, vehicles are expected to be in long-term operation, usually for nearly 20 years, and it is possible that conditions that were initially determined to be tolerable risks when vulnerabilities were discovered may subsequently exceed the acceptable range of risk during 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. [Prior art documents] [Patent documents]
[0010] [Patent Document 1] International Publication No. 2020 / 080222 Summary of the Invention [Problem to be solved by the invention]
[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, when updating software of a target device installed in a vehicle, etc., can 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 the present specification and the accompanying drawings. Furthermore, the objects, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Means for solving the problem]
[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, 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. Effect of the Invention
[0014] According to the present invention, when updating software of a target device mounted on 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 the present specification and the accompanying drawings. Furthermore, the objects, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]
[0015] [Figure 1] 1 is a block diagram showing a functional configuration of a software updating device according to an embodiment of the present invention and a relationship with an external organization. [Diagram 2] A diagram explaining the processes (events) that are expected after a vulnerability is discovered. [Diagram 3] 4 is a flowchart showing a process executed during software update. [Figure 4] FIG. 13 is a diagram showing a process for updating risk management information after a vulnerability is discovered. [Diagram 5]FIG. 13 is a diagram for explaining updated content of risk management information. [Figure 6] FIG. 4 is a diagram showing a process of updating software. [Figure 7] FIG. 13 is a diagram showing risk tolerance conditions that are referenced when updating software. [Figure 8] 10 is a flowchart showing a process for verifying risk tolerance conditions executed when updating software. [Figure 9] FIG. 1 is a diagram showing a process for applying a vulnerability patch. [Figure 10] A diagram showing the contents of the vulnerability patch applied. [Figure 11] FIG. 11 is a diagram for explaining updated content of risk management information. [Figure 12] FIG. 13 is a block diagram showing the functional configuration of a software updating device according to a modified example of the present invention and its relationship with an external organization. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0017] 1 is a block diagram showing a functional configuration of a software update device according to an embodiment of the present invention and a relationship with an external organization. The software update device according to the embodiment is implemented as a device CGW (Central Gate Way) 100 in a vehicle.
[0018] The software update device 100 according to the present 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 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 updating 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 an update program 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 is tolerated at least once.
[0023] Once a vulnerability is discovered and the risk is accepted, the next steps are: (1) updating the program, (2) applying a vulnerability patch, or (3) discovering a new vulnerability.
[0024] A flow chart for explaining the above development is shown in Fig. 3. After the risk tolerance of the discovered vulnerability is determined, when the software update device receives an arbitrary program, the update type is confirmed by the software update control unit 13 (step S301). Here, it is determined whether the program is an update of risk management information (step S302), and if it is an update of 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, it is stage (1) above, and the process moves to program update / update prohibition processing in steps S306 to S309. If it is related to patch update processing, it is stage (2), and the process moves to patch update processing in step S305. These processes will be described in detail later. If a new vulnerability is discovered after these processes, it is stage (3) above.
[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 an 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 contents include, for example, risk management information updates, program updates, vulnerability patch updates, etc.
[0028] The generated package is transmitted to the OTA center (step S403), and is then transmitted 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 Fig. 5(a) and (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 above ID has been discovered, but the risk posed by this vulnerability has been determined to be tolerable (it will not pose a threat if left unattended).
[0031] In this case, the package contains information such as that shown in Figure 5(d) as its risk tolerance conditions. This means that the risk tolerance type is "Alternative with existing measures" and the tolerance condition is "Measure A" which has already been implemented in the product, and that the risk of the newly discovered vulnerability can be tolerated by this measure. Also, the risk tolerance type is "No attack path applicable" and the tolerance condition is "No remote services" means that there is no remote (wireless) access path to the product, meaning 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 above-mentioned initial risk acceptance decision, 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 vulnerability that it has accepted as a risk (step S601), and then generates a package (step S602). The package includes an update type, risk impact details, and an update program.
[0034] The generated package is transmitted to the dealer / OTA center (step S603), and is also transmitted 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 process 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 process 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 / update prohibition process (step S608).
[0037] The verification of the above-mentioned 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, shown in Figures 7(a) and (c).
[0038] The risk impact content indicates the scope and content of the impact when the update program included in the package is executed, and in this embodiment, when the update program is executed, it affects the in-vehicle device ECU_1, and the impact content is registered as "impact type: attack path not applicable" and "impact content: 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 is added.
[0039] Here, the risk acceptance condition in FIG. 7(c) is referred to. 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 service was valid. However, when the above-mentioned risk impact contents are taken into consideration, a remote service that can access ECU_1 is added, and the validity of the condition is lost. Therefore, a process is performed to prohibit a program update having such an impact. If the validity of the condition is not lost, the program update may be executed.
[0040] The above process will be explained using the flowchart in Fig. 8. First, the software update device checks the contents of the received package and judges whether or not there is a vulnerability that poses a risk (step S801). If it is judged that there is no vulnerability that poses a risk, this means that there is no need to consider risk tolerance, so the program update process is executed (step S807).
[0041] If there is a vulnerability that requires risk retention, the process proceeds to step S802, and risk impact details as shown in Fig. 7(b) are acquired. Then, the corresponding risk tolerance type is searched for from the risk management information (step S803). Next, it is determined whether or not there is a valid risk tolerance condition in the searched risk tolerance type (step S804). If there is no valid risk tolerance condition, this means that there is no risk tolerance condition that will be invalidated by the program update, so the program update process is executed (step S807).
[0042] If there are valid risk tolerance conditions, it is determined whether the risk tolerance conditions will be exceeded by updating the program (step S805). If there is no deviation, the risk tolerance conditions will remain satisfied even if the program is updated, so the program update is executed (step S807). If there is a deviation from the tolerance conditions, a process is executed to prohibit the update of the program (step S806). The above is the verification process of the risk tolerance conditions, which corresponds to steps S306 to S309 in the overall processing described in FIG. 3.
[0043] In addition, in the above-mentioned program update prohibition process, there may be cases where a further detailed analysis is performed on the software whose update was prohibited, and it is determined that the software did not deviate from the risk tolerance conditions. In such cases, the program update using the 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 is generated (step S902).
[0046] The generated package is transmitted to the dealer / OTA center (step S903), and then transmitted to the vehicle's software update device, at the same time starting 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 patch application, and since there is no effect on the risk tolerance conditions, the program update process is executed 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 embodiment, the risk avoidance range was the vulnerability identified by vulnerability ID: CVE-2022-AAA, as shown in Figure 10(a). Then, the risk related to this vulnerability is eliminated by applying a patch to this vulnerability, so the corresponding vulnerability becomes "risk avoidance" as shown in Figures 10(b) and (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 the risk tolerance condition of 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 in the on-board device ECU_2 is "substitution with existing measures" and the tolerance condition is "measure B".
[0051] In the above, the software update device has been described as being mounted on a vehicle. However, as a modified example of the present invention, it is also possible to provide the function of the software update device to an OTA center 300 communicably connected to a vehicle / ECU as shown in FIG.
[0052] According to this embodiment, the OTA center connected to a large number of vehicles / ECUs can perform processing collectively, and the processing can be centralized.
[0053] According to the embodiment of the present invention described above, the following advantageous effects are obtained. (1) 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, 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 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 that verifies whether the update content satisfies the tolerance conditions when the software is updated. 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 that updates the tolerance conditions based on the update information of the tolerance conditions is further provided. The risk tolerance conditions relate to whether or not software updates can be performed, and therefore must always be kept up to date. Such a risk update unit is useful.
[0057] (4) An update information acquisition unit that acquires update information for the acceptable conditions and updates to be used for the software update, and an update content determination unit that determines whether to execute an update of the acceptable conditions or a software update. Since the priority of updates of the acceptable conditions and software updates varies depending on their contents, adopting such a configuration makes it possible to select an appropriate process.
[0058] (5) A software updating method according to one embodiment of the present invention corresponds to the software updating device of (1) and has the same effects as (1).
[0059] 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 an embodiment having all of the configurations described. It is also possible to replace a 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 a part of the configuration of each embodiment, or to add or replace another configuration. [Explanation of symbols]
[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 risk management unit that manages vulnerability information of a target device and allowable conditions for risks in the vulnerability information; and a software update control unit that prohibits the software update when it is determined that the update content does not satisfy the permissible condition when a software update is performed on the target device. A software updating device comprising:
2. 2. The software update device according to claim 1, a risk verification unit that verifies whether the update content satisfies the permissible condition when the software update is performed; A software updating device comprising:
3. 2. The software update device according to claim 1, A risk update unit that updates the acceptable conditions based on update information of the acceptable conditions, A software updating device comprising:
4. 4. The software update device according to claim 3, an update information acquisition unit that acquires update information of the permissible conditions and an update program used for the software update; and an update content determination unit that determines whether to update the permissible condition or to update the software. A software updating device comprising:
5. Acquire vulnerability information of a target device and an acceptable condition for a risk in the vulnerability information; When a software update is performed on the target device, the software update is prohibited when it is determined that the update content does not satisfy the permissible condition.
13. A software update method comprising:
Citation Information
Patent Citations
Threat analysis apparatus, threat analysis method, and program
WO2020080222A1
