Monitoring system and control method
The monitoring system for in-vehicle systems addresses the issue of functional restriction by selectively stopping or altering settings of specific services with vulnerabilities, minimizing the impact of abnormality handling on vehicle functions.
Patent Information
- Application Number
- JP2023071248
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-25
- Publication Date
- 2024-11-07
- Estimated Expiration
- 2043-04-25
AI Technical Summary
Conventional monitoring systems for vehicle security abnormalities risk significantly restricting vehicle functions due to excessive abnormality handling processing.
A monitoring system for in-vehicle systems that includes an abnormality detection unit, a determining unit to select specific services to stop or change settings, and an abnormality handling unit to execute these changes based on a service list, minimizing functional impact by targeting minimal vulnerability services.
The system effectively suppresses the influence on vehicle functions by selectively stopping or altering settings of specific services with potential vulnerabilities, thereby reducing the impact of abnormality response processing.
Smart Images

Figure 2024157113000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a monitoring system and a control method. [Background technology]
[0002] 2. Description of the Related Art There is known a monitoring system that monitors whether or not a security anomaly has occurred in an operating system mounted on a vehicle when the operating system is attacked from the outside (see, for example, Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 7113337 Summary of the Invention [Problem to be solved by the invention]
[0004] In the conventional monitoring system described above, there is a risk that the functionality of the vehicle may be significantly restricted by executing an abnormality response process to resolve a security abnormality.
[0005] Therefore, the present disclosure provides a monitoring system and a control method that can reduce the impact on vehicle functions caused by executing an abnormality response process. [Means for solving the problem]
[0006] A monitoring system according to one embodiment of the present disclosure is a monitoring system for monitoring an in-vehicle system installed in a vehicle, and includes an operating system, an anomaly detection unit that detects a security anomaly in the operating system, a first memory unit that stores a service list indicating a list of multiple services executed in the in-vehicle system, a judgment unit that, when a security anomaly is detected by the anomaly detection unit, judges a specific service from among the multiple services indicated in the service list that should be stopped or have its settings changed to resolve the security anomaly, and an anomaly response unit that executes an anomaly response process to stop or change the settings of the specific service based on the judgment result of the judgment unit.
[0007] These comprehensive or specific aspects may be realized by a system, a method, an integrated circuit, a computer program, or a recording medium such as a computer-readable CD-ROM (Compact Disc-Read Only Memory), or may be realized by any combination of the system, the method, the integrated circuit, the computer program, and the recording medium. Effect of the Invention
[0008] According to a monitoring system etc. relating to one aspect of the present disclosure, it is possible to reduce the impact on the vehicle's functions caused by executing an abnormality response process. [Brief description of the drawings]
[0009] [Figure 1] 1 is a conceptual diagram showing an overview of an in-vehicle system according to an embodiment; [Diagram 2] 1 is a block diagram showing an overview of an in-vehicle system according to an embodiment; [Diagram 3] 2 is a block diagram showing a functional configuration of an integrated ECU according to the embodiment; FIG. [Figure 4A] FIG. 11 is a diagram illustrating an example of detection result information according to the embodiment. [Figure 4B] FIG. 4 is a diagram showing an example of vehicle state information according to the embodiment; [Figure 4C]FIG. 13 is a diagram illustrating an example of the number of times an abnormality is handled according to the embodiment. [Diagram 5] FIG. 4 is a diagram showing an example of a service list according to the embodiment; [Figure 6] FIG. 13 is a diagram illustrating an example of an abnormality response table according to the embodiment. [Figure 7] 4 is a diagram for explaining a process of a determination unit of an integrated ECU according to an embodiment. FIG. [Figure 8] FIG. 11 is a diagram showing an example of a suspended service list according to the embodiment. [Figure 9] 3 is a sequence diagram showing a flow of an overall operation of an integrated ECU according to the embodiment; FIG. [Figure 10] 5 is a flowchart showing a flow of an operation of a determination unit of the integrated ECU according to the embodiment. [Figure 11] 5 is a flowchart showing a flow of an operation of a determination unit of the integrated ECU according to the embodiment. [Figure 12] 5 is a flowchart showing a flow of an operation of a determination unit of the integrated ECU according to the embodiment. [Figure 13] 5 is a diagram for explaining an operation of a determination unit of the integrated ECU according to the embodiment. FIG. [Figure 14] FIG. 13 is a diagram illustrating an example of an abnormality response table according to a modified example of the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] A monitoring system according to a first aspect of the present disclosure is a monitoring system for monitoring an in-vehicle system installed in a vehicle, and comprises an operating system, an anomaly detection unit that detects a security anomaly in the operating system, a first memory unit that stores a service list indicating a list of multiple services executed in the in-vehicle system, a judgment unit that, when a security anomaly is detected by the anomaly detection unit, judges from among the multiple services indicated in the service list a specific service that should be stopped or have its settings changed to resolve the security anomaly, and an anomaly response unit that executes an anomaly response process to stop or change the settings of the specific service based on the judgment result of the judgment unit.
[0011] According to this aspect, when a security anomaly is detected by the anomaly detection unit, the determination unit determines, from among the multiple services indicated by the service list, a specific service that should be stopped or the settings of which should be changed in order to resolve the security anomaly. As a result, the anomaly response unit executes anomaly response processing to stop or change the settings of a minimum number of specific services that are likely to include vulnerabilities, for example, so that it is possible to minimize the impact of executing the anomaly response processing on the functions of the vehicle.
[0012] In addition, in the monitoring system according to the second aspect of the present disclosure, in the first aspect, the monitoring system may further include a counting unit that counts an anomaly response count, which is the number of times the anomaly response process is executed by the anomaly response unit over a predetermined period of time, and the determination unit may be configured to determine, based on the number of anomaly responses, from among the multiple services indicated by the service list, the specific service that should be stopped or have its settings changed to resolve the security anomaly.
[0013] According to this aspect, as the number of abnormality responses increases, an abnormality response process can be executed to stop or change the settings of specific services, for example, in order of the likelihood of including vulnerabilities.
[0014] In addition, in the monitoring system according to the third aspect of the present disclosure, in the second aspect, the monitoring system further includes a second memory unit that stores an anomaly response table indicating the correspondence between the number of anomaly responses and the anomaly response processing, and the determination unit may be configured to determine, by referring to the anomaly response table, the specific service that should be stopped or have its settings changed to resolve the security anomaly, from among the multiple services indicated by the service list, based on the anomaly response processing corresponding to the number of anomaly responses counted by the counting unit.
[0015] According to this aspect, as the number of abnormality responses increases, an abnormality response process can be executed to stop or change the settings of specific services, for example, in order of the likelihood of including vulnerabilities.
[0016] In addition, in the monitoring system according to the fourth aspect of the present disclosure, in the second or third aspect, the monitoring system may further include an acquisition unit that acquires vehicle status information, which is information indicating the status of the vehicle, and the determination unit may be configured to determine, based on the number of abnormality responses and the vehicle status information, from among the multiple services indicated by the service list, the specific service that should be stopped or have its settings changed to resolve the security abnormality.
[0017] According to this aspect, it is possible to determine a specific service that should be stopped or have its settings changed in order to resolve a security anomaly, taking into consideration vehicle state information as well.
[0018] Also, in the monitoring system according to the fifth aspect of the present disclosure, in the fourth aspect, the vehicle status information is information indicating that the vehicle is in a state in which the vehicle is moving or stopped, and in the service list, each of the plurality of services is associated with whether the service can be stopped while the vehicle is moving or stopped, and the determination unit may be configured not to adopt as the specific service, a service among the plurality of services indicated by the service list that cannot be stopped while the vehicle is moving or stopped, based on the number of abnormality responses and the vehicle status information.
[0019] According to this aspect, by not adopting services that cannot be stopped while the vehicle is moving or stopped as specific services that should be stopped or have their settings changed, the impact on the in-vehicle system can be minimized.
[0020] In addition, in a monitoring system according to a sixth aspect of the present disclosure, in any one of the first to fifth aspects, the monitoring system may be further configured to include a notification unit that notifies the user that the specific service has been stopped or reconfigured when the specific service has been stopped or reconfigured by the abnormality response unit.
[0021] According to this aspect, the fact that a particular service has been stopped or the settings have been changed can be detected, for example, by an external monitoring server.
[0022] In addition, in the monitoring system according to the seventh aspect of the present disclosure, in the sixth aspect, the notification unit may be further configured to notify the content of the anomaly response processing executed by the anomaly response unit when the security anomaly is resolved.
[0023] According to this aspect, the details of the anomaly handling process executed by the anomaly handling unit to resolve the security anomaly can be grasped, for example, by an external monitoring server, and can be used to analyze the cause of the security anomaly.
[0024] In addition, in a monitoring system according to an eighth aspect of the present disclosure, in any one of the first to seventh aspects, the anomaly response unit may be configured to generate a duplicate operating system by replicating the operating system in which the security anomaly has been detected, when the security anomaly is detected by the anomaly detection unit.
[0025] According to this aspect, when an operating system is attacked, the settings of the original operating system (e.g., IP address, etc.) can be changed to settings that are less susceptible to attack, while allowing a copied operating system made by copying the original operating system to continue to be a target of attack.
[0026] In addition, in a monitoring system according to a ninth aspect of the present disclosure, in any one of the first to eighth aspects, a priority is associated with each of the plurality of services in the service list, and the determination unit may be configured to determine, based on the priority, from among the plurality of services indicated by the service list, the specific service that should be stopped or have its settings changed in order to resolve the security anomaly.
[0027] According to this aspect, of the multiple services indicated in the service list, for example, a service that is likely to include a vulnerability can be preferentially determined as a specific service.
[0028] In addition, in a monitoring system according to a tenth aspect of the present disclosure, in any one of the first to ninth aspects, the plurality of services in the service list may be configured to be classified into categories including at least one of network, device, vehicle function, vehicle safety function, and security.
[0029] According to this aspect, among the multiple services shown in the service list, for example, a service in a category related to the content of a security anomaly can be preferentially determined as a specific service.
[0030] In addition, a control method according to an eleventh aspect of the present disclosure is a control method in a monitoring system for monitoring an on-board system installed in a vehicle, comprising the steps of: (a) detecting a security anomaly in the operating system; (b) when the security anomaly is detected in (a), determining a specific service that should be stopped or reconfigured to resolve the security anomaly from among the multiple services indicated by a service list that lists multiple services executed in the on-board system; and (c) executing anomaly response processing to stop or reconfigure the specific service based on the determination result of (b).
[0031] According to this aspect, similarly to the monitoring system according to the first aspect, it is possible to minimize the effect on the functions of the vehicle caused by executing the abnormality response process.
[0032] In addition, these comprehensive or specific aspects may be realized by a system, a method, an integrated circuit, a computer program, or a recording medium such as a computer-readable CD-ROM, or may be realized by any combination of the system, method, integrated circuit, computer program, or recording medium.
[0033] Hereinafter, the embodiment will be specifically described with reference to the drawings.
[0034] The embodiments described below are all comprehensive or specific examples. The numerical values, shapes, materials, components, component arrangement and connection forms, steps, and order of steps shown in the following embodiments are merely examples and are not intended to limit the present disclosure. Furthermore, among the components in the following embodiments, components that are not described in an independent claim showing a top concept are described as optional components.
[0035] (Embodiment) [1. Overview of the in-vehicle system] First, an overview of an in-vehicle system 2 according to an embodiment will be described with reference to Fig. 1 and Fig. 2. Fig. 1 is a conceptual diagram showing an overview of the in-vehicle system 2 according to an embodiment. Fig. 2 is a block diagram showing an overview of the in-vehicle system 2 according to an embodiment.
[0036] As shown in FIG. 1, an in-vehicle system 2 according to an embodiment of the present invention is applied to an autonomous driving system mounted on a vehicle 4 such as an automobile, for controlling driving operations such as acceleration / deceleration, steering, and braking of the vehicle 4 to be automatically performed by an ADAS (Advanced Driver Assistance System).
[0037] The in-vehicle system 2 can communicate with the monitoring server 8 via an external network 6 such as the Internet. The in-vehicle system 2 monitors whether or not a security abnormality has occurred in the in-vehicle system 2, and notifies the monitoring server 8 of the monitoring result via the external network 6.
[0038] The monitoring server 8 is installed in, for example, a security monitoring center etc. Upon receiving a notification from the in-vehicle system 2, the monitoring server 8 grasps the occurrence status of a security abnormality in each vehicle 4 and provides advice on how to deal with the security abnormality etc.
[0039] As shown in FIG. 2, the in-vehicle system 2 includes an integrated ECU (Electronic Control Unit) 10, a gateway ECU 12, a steering ECU 14, a brake ECU 16, a zone ECU 18, a front camera ECU 20, and a rear camera ECU 22.
[0040] The integrated ECU 10 is communicatively connected to the gateway ECU 12 via a CAN (Controller Area Network) 24. The gateway ECU 12, the steering ECU 14, and the brake ECU 16 are communicatively connected to one another via a CAN 26.
[0041] The integrated ECU 10 is communicatively connected to the zone ECU 18 via an Ethernet (registered trademark) 28. The zone ECU 18, the front camera ECU 20, and the rear camera ECU 22 are communicatively connected to one another via an Ethernet (registered trademark) 30. The integrated ECU 10 is further communicatively connected to a monitoring server 8 (see FIG. 1) via an external network 6.
[0042] The integrated ECU 10 performs the following functions: (a) communication control for transmitting and receiving messages via the external network 6, the CAN 24, and Ethernet 28, (b) vehicle control for instructing the gateway ECU 12 and the zone ECU 18 to control the vehicle 4 via the CAN 24 and Ethernet 28, and (c) video output to the infotainment system and the instrument panel. The integrated ECU 10 also monitors whether or not a security abnormality (e.g., unauthorized access, etc.) has occurred in the in-vehicle system 2, and notifies the monitoring server 8 of the monitoring result. In other words, the integrated ECU 10 is an example of a monitoring system for monitoring the in-vehicle system 2 mounted in the vehicle 4.
[0043] The gateway ECU 12 mediates messages transmitted and received between the integrated ECU 10 and the steering ECU 14 and brake ECU 16 .
[0044] The steering ECU 14 controls steering by a steering wheel mounted on the vehicle 4.
[0045] The brake ECU 16 controls the operation of the brakes mounted on the vehicle 4 .
[0046] In addition to the steering ECU 14 and the brake ECU 16, the in-vehicle system 2 uses ECUs that control the engine, body, etc. of the vehicle 4 to perform various controls of the vehicle 4, such as running, turning, and stopping.
[0047] The zone ECU 18 mediates messages transmitted and received between the integrated ECU 10 and the front camera ECU 20 and rear camera ECU 22 .
[0048] The front camera ECU 20 acquires an image of the front of the vehicle 4 captured by a front camera mounted on the front part of the vehicle 4 .
[0049] The rear camera ECU 22 acquires an image of the rear of the vehicle 4 captured by a rear camera mounted on the rear of the vehicle 4 .
[0050] [2. Functional configuration of the integrated ECU] Next, the functional configuration of the integrated ECU 10 (monitoring system) will be described with reference to Figs. 3 to 8. Fig. 3 is a block diagram showing the functional configuration of the integrated ECU 10 according to the embodiment. Fig. 4A is a diagram showing an example of detection result information according to the embodiment. Fig. 4B is a diagram showing an example of vehicle state information according to the embodiment. Fig. 4C is a diagram showing an example of the number of abnormality responses according to the embodiment. Fig. 5 is a diagram showing an example of a service list according to the embodiment. Fig. 6 is a diagram showing an example of an abnormality response table according to the embodiment. Fig. 7 is a diagram for explaining the process of the determination unit 70 of the integrated ECU 10 according to the embodiment. Fig. 8 is a diagram showing an example of a stopped service list according to the embodiment.
[0051] As shown in FIG. 3, the integrated ECU 10 has, as its functional configuration, hardware 32, a virtualization platform 34, a guest virtual machine 36 (an example of an operating system), a guest virtual machine 38 (an example of an operating system), and a host virtual machine 40 (an example of an operating system).
[0052] The hardware 32 includes a processor having, for example, a CPU (Central Processing Unit) or an ECU, and provides an execution environment for multiple computer programs. Note that the hardware 32 may be configured with one processor or multiple processors.
[0053] The virtualization platform 34 is virtualization software that runs on the hardware 32 and controls the execution of the guest virtual machines 36, 38 and the host virtual machine 40. This virtualization platform 34 allows a plurality of different operating systems (guest virtual machines 36, 38 and the host virtual machine 40) to be virtualized and mounted on one piece of hardware 32. The virtualization platform 34 may be a Type 1 hypervisor that runs directly on the hardware 32, or a TYPE 2 hypervisor that runs on an operating system that runs directly on the hardware 32. Alternatively, the virtualization platform 34 may be a container. In the present embodiment, the integrated ECU 10 is realized in a virtual environment by the virtualization platform 34, but is not limited to this and may be realized by actual hardware.
[0054] The guest virtual machine 36 is an operating system such as Linux (registered trademark) or Android (registered trademark) that runs on the virtualization platform 34. The guest virtual machine 36 has an abnormality detection unit 42, an abnormality handling unit 44, and an abnormality notification unit 46 (an example of a notification unit). The guest virtual machine 36 is assigned a virtual machine number "1" for identifying the guest virtual machine 36.
[0055] The anomaly detection unit 42 detects a security anomaly in the guest virtual machine 36 by monitoring the behavior and communication state of each ECU in the in-vehicle system 2. The anomaly detection unit 42 is configured, for example, by a network IDS (Network-based Intrusion Detection System: NIDS) or a host IDS (Host-based Intrusion Detection System: HIDS).
[0056] When a security anomaly is detected by the anomaly detection unit 42, the anomaly response unit 44 executes anomaly response processing (described later) to resolve the detected security anomaly based on an anomaly response instruction (described later) from the host virtual machine 40.
[0057] When a security anomaly is detected by the anomaly detection unit 42, the anomaly notification unit 46 notifies the monitoring server 8 (see FIG. 1) of, for example, information indicating the contents of the detected security anomaly, the contents of the anomaly response process, and information indicating that a specific service (described later) has been stopped or the settings have been changed. In addition, when the security anomaly is resolved, the anomaly notification unit 46 notifies the monitoring server 8 of information indicating that the security anomaly has been resolved, the contents of the anomaly response process, and information indicating that a specific service has been stopped or the settings have been changed.
[0058] In this embodiment, the abnormality notification unit 46 notifies the monitoring server 8 of the above-mentioned various information, but is not limited thereto, and may notify, for example, the driver of the vehicle 4, nearby vehicles, nearby pedestrians, etc. For example, when notifying the driver of the vehicle 4 of various information, the abnormality notification unit 46 may display a message on a display mounted in the cabin of the vehicle 4 or turn on a lamp disposed on a button mounted in the cabin of the vehicle 4. The same applies to abnormality notification units 52 and 58 described later.
[0059] The guest virtual machine 38 is an operating system such as Linux (registered trademark) or Android (registered trademark) that runs on the virtualization platform 34. The guest virtual machine 38 has an abnormality detection unit 48, an abnormality response unit 50, and an abnormality notification unit 52 (an example of a notification unit). The guest virtual machine 38 is assigned a virtual machine number "2" for identifying the guest virtual machine 38.
[0060] The anomaly detection unit 48 detects a security anomaly in the guest virtual machine 38 by monitoring the behavior and communication state of each ECU in the in-vehicle system 2. The anomaly detection unit 48 is configured by, for example, a network IDS or a host IDS.
[0061] When a security anomaly is detected by the anomaly detection unit 48, the anomaly handler 50 executes anomaly handling processing for resolving the detected security anomaly based on an anomaly handling instruction from the host virtual machine 40.
[0062] When a security anomaly is detected by the anomaly detection unit 48, the anomaly notification unit 52 notifies the monitoring server 8 of information indicating, for example, the contents of the detected security anomaly, the contents of the anomaly response process, the fact that a specific service has been stopped or the settings have been changed, etc. In addition, when the security anomaly is resolved, the anomaly notification unit 52 notifies the monitoring server 8 of information indicating that the security anomaly has been resolved.
[0063] The host virtual machine 40 is an operating system such as Linux (registered trademark) or Android (registered trademark) that runs on the virtualization platform 34. The host virtual machine 40 includes an abnormality detection unit 54, an abnormality response unit 56, an abnormality notification unit 58 (an example of a notification unit), a detection result collection unit 60, a vehicle state acquisition unit 62 (an example of an acquisition unit), an abnormality response counting unit 64 (an example of a counting unit), a service list storage unit 66 (an example of a first storage unit), an abnormality response table storage unit 68 (an example of a second storage unit), a determination unit 70, and an instruction unit 72. The host virtual machine 40 is assigned a virtual machine number "3" for identifying the host virtual machine 40.
[0064] The anomaly detection unit 54 detects a security anomaly in the host virtual machine 40 by monitoring the behavior and communication state of each ECU in the in-vehicle system 2. The anomaly detection unit 54 is configured by, for example, a network IDS or a host IDS.
[0065] When a security anomaly is detected by the anomaly detection unit 54, the anomaly response unit 56 executes an anomaly response process for resolving the detected security anomaly based on an anomaly response instruction from the instruction unit 72.
[0066] When a security anomaly is detected by the anomaly detection unit 54, the anomaly notification unit 58 notifies the monitoring server 8 of information indicating, for example, the contents of the detected security anomaly, the contents of the anomaly response process, the fact that a specific service has been stopped or the settings have been changed, etc. In addition, when the security anomaly is resolved, the anomaly notification unit 58 notifies the monitoring server 8 of information indicating that the security anomaly has been resolved.
[0067] The detection result collection unit 60 collects information (hereinafter referred to as "detection result information") indicating the detection results of each anomaly detection unit 42, 48, 54. The detection result information includes, for example, (a) the virtual machine number of the virtual machine in which a security anomaly was detected, (b) the type of anomaly detection unit that detected the security anomaly (network IDS or host IDS), and (c) the details of the security anomaly. The detection result collection unit 60 holds the collected detection result information as, for example, a data table as shown in FIG. 4A.
[0068] The vehicle state acquisition unit 62 acquires information indicating the state of the vehicle 4 (hereinafter referred to as "vehicle state information"), for example, from the gateway ECU 12 and the zone ECU 18. The vehicle state information includes, for example, (a) the running state of the vehicle 4 (running, stopped), and (b) the operating state of the engine of the vehicle 4 (on or off). The vehicle state acquisition unit 62 holds the acquired vehicle state information as, for example, a data table as shown in FIG. 4B. Note that the vehicle state information may include, in addition to the above (a) and (b), for example, (c) auto cruise control in progress, (d) automatic driving in progress, (e) ignition ON / OFF, (f) accessory ON / OFF, (g) Internet connected, (h) GPS (Global Positioning System) information, and the like.
[0069] The abnormality response count counting unit 64 counts the number of times each of the abnormality response units 44, 50, 56 has executed an abnormality response process over a predetermined period (e.g., during the most recent hour) (hereinafter referred to as the "abnormality response count"). The abnormality response count counting unit 64 increments the abnormality response count by "1" each time any of the abnormality response units 44, 50, 56 executes an abnormality response process. The abnormality response count counting unit 64 holds the counted abnormality response counts as a data table such as that shown in FIG. 4C. The abnormality response count counting unit 64 may count the abnormality response count for each type of security abnormality.
[0070] The service list storage unit 66 is a non-volatile memory that stores a service list. The service list is a list showing a list of a plurality of services (functions) executed by the in-vehicle system 2, and is, for example, a data table as shown in Fig. 5. As shown in Fig. 5, the service list associates a service name, a virtual machine number, a priority, a category, a vehicle state, a need for reboot, and a setting value.
[0071] The “service name” in the service list is the name of the service executed in the in-vehicle system 2 .
[0072] "External vehicle communication" refers to, for example, WiFi (registered trademark), Bluetooth (registered trademark), wireless "Device connection" is a service required for communication with the outside of the vehicle 4, such as wired Internet communication and encrypted communication. "Device connection" is a service required for communication with external devices, such as USB (Universal Serial Bus) and Bluetooth (registered trademark). "Internal communication" is a service required for communication between virtual machines, communication with a hypervisor (hypercall), communication with TrustZone (Secure Monitor Call), and the like.
[0073] "In-vehicle communication" is, for example, CAN and CAN-FD (CAN with Flexible "Data Rate", FlexRay (registered trademark), Ethernet (registered trademark), and other services necessary for communications related to the control of the vehicle 4. "Software update" is a service necessary for uploading software. "Navigation" is a service necessary for, for example, navigation functions and music / radio playback. "Meter" is a service necessary for displaying vehicle speed, warnings, etc.
[0074] "Vehicle control" is a service required for various controls such as running, turning, and stopping of vehicle 4. "Firewall" is a service required for network filtering, for example. "Access control" is a service required for process access control, for example. "Intrusion detection and defense" is a service required for detecting and preventing security anomalies, for example. "Security (encryption and signatures)" is a service required for security functions using TrustZone, for example.
[0075] The "Virtual Machine Number" in the service list is the virtual machine number (for example, "1", "2", "3") of the virtual machine affected by the service stop.
[0076] "Priority" in the service list is a number that indicates the priority of the service to be stopped or the settings changed. Priority is expressed as a number from "1" to "4", for example, and the lower the number, the higher the priority (i.e., the more likely the service is to contain a vulnerability).
[0077] The "category" in the service list is the type of service, for example, network, device, vehicle function, vehicle safety function, and security.
[0078] "Vehicle status" in the service list is the status of the vehicle 4 (moving, stopped) in which the service cannot be stopped. For example, the vehicle status "Not moving" corresponding to the service name "Meter" means that the "Meter" service cannot be stopped while the vehicle 4 is moving. Note that the vehicle status "-" means that the service can be stopped regardless of the status of the vehicle 4.
[0079] "Restart required" in the service list indicates whether restart is required to stop the service. For example, restart required "not required" means that restart is not required to stop the service. For another example, restart required "system" means that the entire integrated ECU 10 needs to be restarted to stop the service. For another example, restart required "corresponding virtual machine" means that only the virtual machine in which a security anomaly has been detected needs to be restarted to stop the service.
[0080] The "setting value" in the service list is the target for changing the setting when changing the setting of a service. For example, the setting value "IP address" corresponding to the service name "External vehicle communication" means that the IP address of the "External vehicle communication" service is changed as an abnormality response process. Also, for example, the setting value "Rule / No need to stop" corresponding to the service name "Firewall" means that the rule of the "Firewall" service is changed as an abnormality response process (for example, changed to a rule that drops a specific IP address) and the service This means that no stop is necessary.
[0081] The abnormality response table storage unit 68 is a non-volatile memory that stores the abnormality response table. The abnormality response table is a data table, for example, as shown in FIG. 6, that indicates the correspondence between the number of abnormality responses and the abnormality response process.
[0082] As shown in FIG. 6, for example, in the first row of the anomaly response table, the number of anomaly responses "0" is associated with the anomaly response process "change the settings of the service with priority 1." In addition, for example, in the second row of the anomaly response table, the number of anomaly responses "1" is associated with the anomaly response process "stop the service with priority 1." In addition, for example, in the third row of the anomaly response table, the number of anomaly responses "2" is associated with the anomaly response process "change the settings of the service with priority 2." In addition, for example, in the fourth row of the anomaly response table, the number of anomaly responses "3" is associated with the anomaly response process "stop the service with priority 2." In other words, in the anomaly response table, as the number of anomaly responses increases, anomaly response processes are specified that stop or change the settings of services in order of the likelihood of including vulnerabilities.
[0083] When a security anomaly is detected by any of the anomaly detection units 42, 48, 54, the determination unit 70 acquires the detection result information from the detection result collection unit 60, the vehicle state information from the vehicle state acquisition unit 62, and the number of anomaly responses from the anomaly response counting unit 64. Then, the determination unit 70 refers to the service list and the anomaly response table, and determines a specific service that should be stopped or the setting should be changed to eliminate the security anomaly from among the multiple services indicated by the service list, based on the detection result information, the vehicle state information, and the number of anomaly responses. Then, the determination unit 70 outputs a stopped service list, which is a list of specific services that should be stopped or the setting should be changed. That is, as shown in FIG. 7, the determination unit 70 executes a process of outputting a stopped service list by inputting the detection result information, the vehicle state information, the number of anomaly responses, the service list, and the anomaly response table.
[0084] The stopped service list is, for example, a data table as shown in Fig. 8. As shown in Fig. 8, in the stopped service list, the number of times an abnormality was handled, the virtual machine number, the priority, the service name, and setting change / stop are associated with each other.
[0085] For example, when the acquired number of times of abnormality responses is 0, the determination unit 70 reads out, from the abnormality response table, an abnormality response process "change the setting of the service with priority 1" corresponding to the abnormality response number "0". Then, based on the acquired detection result information, the determination unit 70 determines that the abnormality detection unit that detected the security abnormality is the network IDS. Also, based on the acquired vehicle information, the determination unit 70 determines that the vehicle 4 is running. In this case, the determination unit 70 extracts "external vehicle communication" and "firewall" from the service list as services having a priority of "1", a category of "network" or "security", and a vehicle state of "-". Then, the determination unit 70 determines "external vehicle communication" and "firewall" as specific services to be changed in setting, and adds the services "external vehicle communication" and "firewall" to the stopped service list.
[0086] Based on the judgment result of the judgment unit 70, the instruction unit 72 outputs an abnormality response instruction to the abnormality response unit among the abnormality response units 44, 50, 56 that detected the security abnormality, instructing the abnormality response unit to stop or change the settings of the specific service judged by the judgment unit 70.
[0087] For example, when the instruction unit 72 outputs an abnormality response instruction to the abnormality handling unit 44 that detected the security abnormality, instructing the abnormality handling unit 44 to stop or change the setting of a specific service determined by the determination unit 70, the abnormality handling unit 44 may operate a duplicate guest virtual machine (an example of a duplicate operating system) that is a duplicate of the guest virtual machine 36 in which the security abnormality was detected. In this way, for example, if the guest virtual machine 36 is attacked, the settings of the original guest virtual machine 36 (e.g., IP address, etc.) can be changed to settings that are less susceptible to attacks while the duplicate guest virtual machine remains the target of the attack. Alternatively, instead of dynamically generating a duplicate guest virtual machine, a duplicate guest virtual machine may be prepared in advance.
[0088] [3. Overall operation of the integrated ECU] Next, an overall operation of the integrated ECU 10 (monitoring system) will be described with reference to Fig. 9. Fig. 9 is a sequence diagram showing a flow of an overall operation of the integrated ECU 10 according to the embodiment.
[0089] The following describes a case where a security anomaly is detected in the guest virtual machine 36. As shown in Fig. 9, first, the anomaly detection unit 42 of the guest virtual machine 36 detects a security anomaly in the guest virtual machine 36 (S101). Next, the detection result collection unit 60 of the host virtual machine 40 collects detection result information from the anomaly detection unit 42 (S102).
[0090] Next, the judgment unit 70 of the host virtual machine 40 acquires detection result information from the detection result collection unit 60 (S103), and acquires vehicle state information and the number of abnormality response times from the vehicle state acquisition unit 62 and the abnormality response time counting unit 64, respectively (S104).
[0091] Next, the judgment unit 70 refers to the service list and the anomaly response table, and based on the detection result information, vehicle condition information, and the number of anomaly responses, judges, from among the multiple services indicated by the service list, a specific service that should be stopped or have its settings changed in order to resolve the security anomaly (S105).
[0092] Next, the instruction unit 72 of the host virtual machine 40 outputs an abnormality response instruction to the anomaly response unit 44 of the guest virtual machine 36 in which a security anomaly has been detected, based on the determination result of the determination unit 70, to instruct the anomaly response unit 44 to stop or change the setting of the specific service determined by the determination unit 70 (S106). Next, the anomaly response unit 44 of the guest virtual machine 36 executes anomaly response processing to stop or change the setting of the specific service, based on the anomaly response instruction from the instruction unit 72 (S107).
[0093] Next, the abnormality notification unit 46 of the guest virtual machine 36 notifies the monitoring server 8 of information indicating the contents of the detected security abnormality, the contents of the abnormality response process, etc. (S108). As a result, the notification contents from the abnormality notification unit 46 are displayed on the display of the monitoring server 8 (S109).
[0094] In this embodiment, the case where a security anomaly is detected in the guest virtual machine 36 has been described, but similar processing to that described above is also performed when a security anomaly is detected in the guest virtual machine 38 or the host virtual machine 40.
[0095] [4. Operation of the judgment unit] Next, the operation of the determination unit 70 of the integrated ECU 10 will be described with reference to Fig. 10 to Fig. 13. Fig. 10 to Fig. 12 are flowcharts showing the flow of the operation of the determination unit 70 of the integrated ECU 10 according to the embodiment. Fig. 13 is a diagram for explaining the operation of the determination unit 70 of the integrated ECU 10 according to the embodiment.
[0096] 10, the determination unit 70 acquires detection result information from the detection result collection unit 60 (S201). Next, the determination unit 70 acquires the number of abnormality responses from the abnormality response counting unit 64. Then, it is determined whether the number of abnormality responses is N (≧1) times (S202).
[0097] If the number of abnormality handling times is 0 (NO in S202), the determination unit 70 reads the abnormality handling process corresponding to the abnormality handling time count "0" from the abnormality handling table, and adds the corresponding specific service to the stopped service list (S203).
[0098] On the other hand, if the number of abnormality responses is N (YES in S202), the determination unit 70 reads out the abnormality response process corresponding to the abnormality response number "N" from the abnormality response table, and adds the corresponding specific service to the stopped service list (S204).
[0099] 11, the determination unit 70 acquires detection result information from the detection result collection unit 60 (S301). Next, the determination unit 70 acquires vehicle state information from the vehicle state acquisition unit 62, and determines whether the state of the vehicle 4 is moving or stopped (S302).
[0100] When the state of the vehicle 4 is stopped ("Stopped" in S302), the determination unit 70 excludes, from the stopped service list, the service in the vehicle state "Not allowed while stopped" among the multiple services indicated in the service list (S303). That is, the determination unit 70 does not adopt, from the multiple services indicated in the service list, the service in the vehicle state "Not allowed while stopped" as a specific service to be stopped or the setting changed.
[0101] On the other hand, when the state of the vehicle 4 is moving ("moving" in S302), the determination unit 70 excludes, from the list of services to be stopped, any service in the vehicle state "not allowed while moving" among the multiple services indicated in the service list (S304). That is, the determination unit 70 does not adopt, from the multiple services indicated in the service list, any service in the vehicle state "not allowed while moving" as a specific service to be stopped or have its settings changed.
[0102] 12, the determination unit 70 acquires detection result information from the detection result collection unit 60 (S401). Next, the determination unit 70 determines the type of anomaly detection unit that detected the security anomaly based on the detection result information (S402, S403).
[0103] If the anomaly detection unit that detected the security anomaly is a network IDS (YES in S402), the decision unit 70 adds services in the category "Network" from among the multiple services indicated in the service list to the stopped service list (S404).
[0104] On the other hand, if the anomaly detection unit that detected the security anomaly is a host IDS (NO in S402, YES in S403), the judgment unit 70 judges whether or not it is possible to identify the service in which the security anomaly occurred (S405). If it is possible to identify the service in which the security anomaly occurred (YES in S405), the judgment unit 70 adds the identified service to the stopped service list (S406). On the other hand, if it is impossible to identify the service in which the security anomaly occurred (NO in S405), the judgment unit 70 ends the process.
[0105] Returning to step S402, if the anomaly detection unit that detected the security anomaly is neither the network IDS nor the host IDS (NO in S402, NO in S403), the determination unit 70 ends the process.
[0106] The stopped service list generated as described above is used as follows. As shown in Fig. 13, assume that the anomaly detection unit 42 of the guest virtual machine 36 detects a security anomaly while the integrated ECU 10 is operating normally. At this point, the number of anomaly handling attempts is 0, so the determination unit 70 reads out anomaly handling process corresponding to the number of anomaly handling attempts of "0" from the anomaly handling table, and adds the corresponding specific service to the stopped service list. As a result, the anomaly response unit 44 of the guest virtual machine 36 executes an anomaly response process to change the settings of the services "external vehicle communication" and "firewall" that have been added to the stopped service list. At this time, the anomaly response count unit 64 of the host virtual machine 40 increments the anomaly response count from "0" to "1."
[0107] After that, the integrated ECU 10 operates normally for a certain period of time, but for example, the anomaly detection unit 42 of the guest virtual machine 36 detects a security anomaly again. At this point, the number of anomaly responses is one, so the determination unit 70 reads out the anomaly response process corresponding to the anomaly response count "1" from the anomaly response table and adds the corresponding specific service to the stopped service list. As a result, the anomaly response unit 44 of the guest virtual machine 36 executes an anomaly response process to stop the service "external vehicle communication" added to the stopped service list, for example, and to change the setting of the service "firewall". At this time, the anomaly response counting unit 64 of the host virtual machine 40 increments the anomaly response count from "1" to "2". Note that, when the number of anomaly responses is one, only the specific service corresponding to the anomaly response process corresponding to the anomaly response count "1" in the anomaly response table may be added to the stopped service list, or the specific service corresponding to the anomaly response process corresponding to the anomaly response counts "0" and "1" in the anomaly response table may be added to the stopped service list.
[0108] After that, when the security anomaly is completely resolved, the integrated ECU 10 operates normally. Note that, when any of the anomaly detection units 42, 48, 54 detects a security anomaly, the same processing as described above is repeatedly executed.
[0109] [5. Effects] In this embodiment, when a security anomaly is detected by any of the anomaly detection units 42, 48, 54, the judgment unit 70 judges, from among the multiple services indicated by the service list, a specific service that should be stopped or have its settings changed in order to resolve the security anomaly.
[0110] This allows the execution of an abnormality response process to stop or change the settings of a minimum number of specific services that are likely to contain vulnerabilities, thereby minimizing the impact on the function of vehicle 4 caused by executing the abnormality response process.
[0111] [6. Modifications] Fig. 14 is a diagram showing an example of an abnormality handling table according to a modified example of the embodiment. As shown in Fig. 14, in the first row of the abnormality handling table, the abnormality handling count "0" is associated with the abnormality handling process "first, stop all services, start services with priority level 4 in order, after a predetermined time has passed, start services with priority level 3 in order, after a further predetermined time has passed, start services with priority level 2 in order, and after a further predetermined time has passed, start services with priority level 1 in order."
[0112] That is, the first row of the anomaly response table specifies that when the number of anomaly responses is 0, the anomaly response process is to temporarily stop all services and then start them up in order from low priority to high priority.
[0113] Furthermore, in the second row of the anomaly response table, the number of anomaly responses "1" is associated with the anomaly response process "first stop all services, and start services other than the service with priority M, starting with the lowest priority." Here, priority M is the priority of the service in which a security anomaly was detected when the number of anomaly responses was 0. For example, when priority M=2, this means that when the number of anomaly responses was 0, the service with priority 4, the service with priority 3, and the service with priority 2 were started in this order, and a security anomaly was detected at the time the service with priority 2 was started.
[0114] That is, the second row of the anomaly response table specifies an anomaly response process in which, when the number of anomaly responses is 1, all services are temporarily stopped, and then services other than the service with priority M are started in order from low to high priority. That is, for example, when priority M=2, this means that the service with priority 4, the service with priority 3, and the service with priority 1 are started in that order.
[0115] (Other variations) Although the monitoring system according to one or more aspects has been described based on the above embodiment, the present disclosure is not limited to the above embodiment. As long as it does not deviate from the spirit of the present disclosure, various modifications conceived by a person skilled in the art to the above embodiment and forms constructed by combining components in different embodiments may also be included within the scope of one or more aspects.
[0116] In the above embodiment, the present disclosure has been described as an application example of a security measure for automobiles (vehicles), but the scope of application is not limited to this. For example, the present disclosure may be applied to various types of mobility such as construction machinery, agricultural machinery, ships, trains, and airplanes, in addition to automobiles.
[0117] In the above embodiment, each component may be realized by a dedicated hardware or by executing a computer program suitable for each component. Each component may be realized by a program execution unit such as a CPU or a processor reading and executing a computer program recorded on a recording medium such as a hard disk or a semiconductor memory.
[0118] Furthermore, some or all of the functions of the monitoring system according to the above-described embodiment may be realized by a processor such as a CPU executing a computer program.
[0119] Some or all of the components constituting each of the above devices may be composed of an IC card or a standalone module that can be attached to each device. The IC card or the module is a computer system composed of a microprocessor, ROM, RAM, etc. The IC card or the module may include the above-mentioned ultra-multifunction LSI. The microprocessor operates according to a computer program, causing the IC card or the module to achieve its functions. The IC card or the module may be tamper-resistant.
[0120] The present disclosure may be the above-mentioned method. It may also be a computer program for implementing these methods by a computer, or a digital signal including the computer program. The present disclosure may also be a computer program or a digital signal recorded on a computer-readable non-transitory recording medium, such as a flexible disk, a hard disk, a CD-ROM, an MO, a DVD, a DVD-ROM, a DVD-RAM, a BD (Blu-ray (registered trademark) Disc), a semiconductor memory, or the like. It may also be the digital signal recorded on these recording media. The present disclosure may also be a computer program or a digital signal transmitted via a telecommunications line, a wireless or wired communication line, a network such as the Internet, data broadcasting, or the like. The present disclosure may also be a computer system having a microprocessor and a memory, in which the memory stores the computer program, and the microprocessor operates according to the computer program. The computer program or the digital signal may also be recorded on the recording medium and transferred, or the computer program or the previous The digital signals may be transferred via the network or the like to be implemented by another independent computer system. [Industrial Applicability]
[0121] The monitoring system according to the present disclosure is applicable to, for example, an integrated ECU having a function of monitoring an in-vehicle system mounted in a vehicle. [Explanation of symbols]
[0122] 2. In-vehicle systems 4. Vehicles 6 External Network 8 Monitoring Server 10 Integrated ECU 12 Gateway ECU 14 Steering ECU 16 Brake ECU 18 Zone ECU 20 Front camera ECU 22 Rear camera ECU 24,26 CAN 28,30 Ethernet (registered trademark) 32 Hardware 34 Virtualization Platform 36,38 Guest Virtual Machines 40 host virtual machines 42, 48, 54 Abnormality detection section 44,50,56 Abnormality Response Section 46,52,58 Abnormality notification section 60 Detection result collection unit 62 Vehicle status acquisition unit 64 Abnormality response count unit 66 Service list storage unit 68 Abnormality response table storage unit 70 Judgment section 72 Instruction section
Claims
1. A monitoring system for monitoring an in-vehicle system installed in a vehicle, comprising: An operating system; an anomaly detection unit for detecting a security anomaly in the operating system; a first storage unit that stores a service list indicating a list of a plurality of services executed by the in-vehicle system; a determination unit that, when the security anomaly is detected by the anomaly detection unit, determines a specific service that should be stopped or have a setting changed from among the plurality of services indicated by the service list in order to resolve the security anomaly; an anomaly handling unit that executes an anomaly handling process to stop or change the setting of the specific service based on the determination result of the determination unit. Surveillance system.
2. The monitoring system further includes a counting unit that counts an anomaly response count, which is the number of times the anomaly response process is executed by the anomaly response unit over a predetermined period of time, The determination unit determines the specific service that should be stopped or have its settings changed to resolve the security anomaly from among the plurality of services indicated by the service list based on the number of anomaly responses. The monitoring system of claim 1 .
3. The monitoring system further includes a second storage unit configured to store an anomaly response table indicating a correspondence relationship between the anomaly response count and the anomaly response process, The determination unit, by referring to the anomaly response table, determines, based on the anomaly response process corresponding to the number of anomaly responses counted by the counting unit, from among the plurality of services indicated by the service list, the specific service that should be stopped or have its settings changed in order to resolve the security anomaly. The monitoring system of claim 2.
4. The monitoring system further includes an acquisition unit that acquires vehicle state information that is information indicating a state of the vehicle, The determination unit determines the specific service that should be stopped or have its settings changed to resolve the security abnormality from among the plurality of services indicated by the service list, based on the abnormality response count and the vehicle state information.
4. A monitoring system according to claim 2 or 3.
5. The vehicle state information is information indicating that the vehicle is in motion or stopped as a state of the vehicle, In the service list, each of the plurality of services is associated with whether or not the service can be stopped while the vehicle is running or stopped; The determination unit does not adopt, as the specific service, a service that cannot be stopped while the vehicle is running or stopped, among the plurality of services indicated by the service list, based on the abnormality response count and the vehicle state information. The monitoring system according to claim 4.
6. The monitoring system further includes a notification unit that notifies a user that the specific service has been stopped or its settings changed when the specific service has been stopped or its settings changed by the abnormality response unit. The monitoring system of claim 1 .
7. The notification unit further notifies the content of the anomaly handling process executed by the anomaly handling unit when the security anomaly is resolved. The monitoring system according to claim 6.
8. The anomaly response unit generates a duplicate operating system by duplicating the operating system in which the security anomaly is detected when the security anomaly detection unit detects the security anomaly. The monitoring system of claim 1 .
9. In the service list, a priority is associated with each of the plurality of services; The determination unit determines, based on the priority, from among the plurality of services indicated by the service list, the specific service that should be stopped or have its settings changed in order to resolve the security anomaly. The monitoring system of claim 1 .
10. In the service list, the plurality of services are classified into categories including at least one of a network, a device, a vehicle function, a vehicle safety function, and a security. The monitoring system of claim 1 .
11. A control method for a monitoring system for monitoring an in-vehicle system mounted on a vehicle, comprising: (a) detecting a security anomaly in the operating system; (b) when the security anomaly is detected in (a), determining a specific service that should be stopped or have its settings changed from among a plurality of services indicated by a service list indicating a list of a plurality of services executed by the in-vehicle system in order to resolve the security anomaly; and (c) executing an anomaly response process for stopping or changing the setting of the specific service based on the determination result of (b). Control methods.
Citation Information
Patent Citations
Information processing apparatus and information processing system
JP2013143093A
Computer with isolated user computing section
JP2020520037A
Control device and control method
JP7224536B2
Vehicle control device, invalidating device, computer program and invalidating method
WO2019175940A1
Service-mediating device and service-mediating method
WO2022153442A1
