Information processing device

The information processing device autonomously selects and transmits relevant vehicle logs during security incidents, addressing storage and bandwidth issues by minimizing unnecessary data transmission.

JP2024166652APending Publication Date: 2024-11-29ASTEMO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2023082877
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-19
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

Existing vehicle data collection systems require continuous communication with a monitoring device, leading to storage constraints and potential log loss during communication interruptions, such as in tunnels or out-of-range scenarios.

Method used

An information processing device that autonomously determines which logs to send using in-vehicle resources, including a log acquisition unit, determination unit, search unit, and transmission unit, to selectively collect and transmit logs related to security incidents.

Benefits of technology

Enables efficient log collection and transmission to a vehicle monitoring center, reducing bandwidth consumption and storage demands by narrowing down relevant logs during security incidents.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024166652000001_ABST
    Figure 2024166652000001_ABST
Patent Text Reader

Abstract

To narrow down logs to be transmitted to a center which monitors vehicles by identifying a log of an on-vehicle device associated with a security incident, when the security incident occurs.SOLUTION: An information processing device comprises: a log acquisition unit which acquires a log of an on-vehicle device; a determination unit which determines the presence / absence of occurrence of a predetermined object event among events generated in the on-vehicle device based on the acquired log; a search unit which executes search processing for the log, when determining that the object event has occurred; and a transmission unit which transmits the log acquired by the search processing to a center. The search processing includes: identification processing which identifies a related event associated with the object event; acquisition processing which acquires the log for determining the presence / absence of the occurrence of the related event identified by the identification processing; and determination processing which determines the presence / absence of the occurrence of the related event based on the log acquired by the acquisition processing.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing device, and more particularly to an information processing device that enables, when a security incident occurs, narrowing down the logs to be transmitted to a center that monitors the vehicle by identifying logs of in-vehicle devices related to the security incident. [Background technology]

[0002] Connected cars, which provide a variety of functions by connecting the car to the Internet, are becoming more and more common. If a connected car is subject to a security attack, it could lead to serious incidents that threaten human lives, so such attacks must be dealt with quickly.

[0003] For this reason, in recent years, there has been progress in the study of Vehicle Security Operation Centers (VSOCs) that continuously monitor the status of vehicles in use, analyze the causes of security incidents when they occur, and respond by remotely controlling the vehicle, etc. The security operation center collects data such as logs from the vehicles, identifies the causes of incidents through manual analysis by analysts or automatic analysis by the system, and plans the necessary responses.

[0004] However, as in-vehicle systems become more complex, the amount of data that can be acquired by the vehicle is increasing, and transmitting all of that data to the center consumes a large amount of communication bandwidth. Therefore, by narrowing down the data related to the incident that has occurred and transmitting it to the center, it is possible to reduce the consumption of communication bandwidth.

[0005] As a prior art related to vehicle data collection, Patent Document 1 discloses a monitoring device that classifies logs from monitored targets into passively collected logs and actively collected logs, and transmits a collection request for actively collected logs to other monitored targets based on an alert generated from a passively collected log. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent Publication No. 2021-027505 Summary of the Invention [Problem to be solved by the invention]

[0007] However, the technology disclosed in Patent Document 1 requires communication with a monitoring device to determine the logs to be collected. Therefore, when communication is interrupted, such as when the vehicle is traveling in a tunnel or outside of communication range, the vehicle cannot collect the logs. Therefore, in order to transmit the logs to the monitoring device when communication is restored, a process is required to store logs that the monitoring device may collect in the vehicle, which may result in problems such as consuming storage space in the in-vehicle system or being unable to transmit logs that were not stored.

[0008] The present invention has been made in consideration of the above points, and aims to provide an information processing device that makes it possible to determine which logs should be sent using limited resources on the vehicle side when a security incident occurs in the vehicle. [Means for solving the problem]

[0009] One example of an information processing device according to the present invention includes a log acquisition unit that acquires a log of an in-vehicle device, a judgment unit that judges whether or not a specified target event has occurred among events that occur in the in-vehicle device based on the acquired log, a search unit that executes a search process for the logs when it is determined that the target event has occurred, and a transmission unit that transmits the log acquired by the search process to a center, and the search process includes a determination process that identifies associated events related to the target event, an acquisition process that acquires a log for judging whether or not the associated event identified by the identification process has occurred, and a judgment process that judges whether or not the associated event has occurred based on the log acquired by the acquisition process. Effect of the Invention

[0010] According to the present invention, when a security incident occurs in a vehicle, it becomes possible to identify logs related to the security incident on the vehicle side and narrow down the logs to be transmitted to the center. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram showing a functional configuration of an information processing device according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing an outline of a processing flow performed by an information processing device according to an embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram showing an example of the contents of a constant-monitoring attack event DB in an embodiment of the present invention. [Figure 4] FIG. 13 is a diagram showing an example of the contents of a related attack event DB in one embodiment of the present invention. [Diagram 5] FIG. 2 is a diagram showing an example of the contents of an attack event related log DB in one embodiment of the present invention. [Figure 6] 11 is a flowchart showing a process performed by a log acquisition unit in an embodiment of the present invention. [Figure 7] 10 is a flowchart showing a process performed by a determination unit in an embodiment of the present invention. [Figure 8] 11 is a flowchart showing a process performed by a search unit in an embodiment of the present invention. [Figure 9] 11 is a flowchart showing a process performed by a search unit in response to an additional search request in an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail using examples with reference to the drawings.

[0013] First, a functional configuration of an information processing device 100 according to an embodiment of the present invention will be described. Note that the information processing device 100 may be a computer including a memory and a processor as a hardware configuration, for example.

[0014] 1 is a block diagram showing the functional configuration of an information processing device 100. The information processing device 100 includes a log acquisition unit 101, a judgment unit 102, a search unit 103, a transmission unit 104, a reception unit 105, a related attack event database (DB) 106, an attack event related log DB 107, a constant monitoring attack event DB 108, a transmission target log list 109, and a search target attack event list 110. Details of these functional units and databases will be described later. The information processing device 100 is mounted on a vehicle and is a computer equipped with a CPU (Central Processing Unit) and a memory.

[0015] The information processing device 100 is also connected to a plurality of in-vehicle devices 112 via a communication path 111. The communication path 111 may physically include a plurality of communication buses, and the standards of each communication bus may all be the same or different. The in-vehicle devices 112 are various ECUs (Electronic Control Units) for controlling the vehicle.

[0016] The information processing device 100 is also connected to a center 114 via a network 113. The center 114 is the above-mentioned VSOC.

[0017] The functional block diagram shown in Fig. 1 is an example, and the units and names of the functions are not limited to those shown. For example, the functions realized by the search unit 103 in this embodiment may be realized by other functional units shown in Fig. 1, or may be realized by a functional unit not shown in Fig. 1.

[0018] FIG. 2 is a diagram showing an outline of the entire processing flow performed by the information processing device 100. As shown in FIG. The log acquisition unit 101 is a functional unit that periodically acquires logs from the in-vehicle device 112. The log acquisition unit 101 acquires constant monitoring attack event information in advance from the constant monitoring attack event DB 108 (201). Here, the constant monitoring attack event DB 108 is a database that stores attack events that are targets of monitoring, and will be described in detail later. An attack event is an event that is caused by an attack on the in-vehicle device. The constant monitoring attack event information is information that indicates an attack event that is constantly monitored for occurrence, and a log that is the basis for determining that the attack event has occurred.

[0019] The log acquisition unit 101 periodically requests the log (overall log) described in the constant monitoring attack event information from the in-vehicle device 112 (202). In response to the request, the in-vehicle device 112 transmits the log to the log acquisition unit 101 (203), and the log acquisition unit 101 passes the acquired log to the determination unit 102 (204).

[0020] The determination unit 102 is a functional unit that determines whether or not an attack event has occurred based on the log of the in-vehicle device received from the log acquisition unit 101 .

[0021] The determination unit 102 acquires constant monitoring attack event information in advance from the constant monitoring attack event DB 108 (205). When the determination unit 102 receives a log from the log acquisition unit 101, the determination unit 102 determines whether or not some attack event has occurred based on the log information. If it is determined that an attack event has occurred, the determination unit 102 transmits attack event information regarding the attack event to the search unit 103 (206).

[0022] The search unit 103 is a functional unit that executes a log search process based on the attack event information received from the judgment unit 102 when it is determined that an attack event has occurred. When the search unit 103 receives attack event information from the judgment unit 102, it searches the related attack event DB 106 for related attack event information related to the attack event (207). Here, the related attack event information is information indicating the relationship between attack events, and when a certain attack event has occurred and there is a high possibility that another attack event has also occurred, the relationship between those attack events is recorded in the related attack event DB 106 as related attack event information. When the search unit 103 acquires the related attack event information (208), it identifies other attack events related to the attack event information received from the judgment unit 102 using the related attack event information.

[0023] Next, the search unit 103 determines whether the identified related attack event has occurred based on the log of the in-vehicle device 112. To do so, the search unit 103 searches and acquires attack event related log information related to the related attack event from the attack event related log DB 107 (209, 210). Here, the attack event related log information is information indicating logs that will be affected when a certain attack event occurs, and is used to determine whether an attack event has occurred. The search unit 103 uses the acquired attack event related log information to identify a log related to the related attack event, and requests the log from the in-vehicle device 112 (211). When the search unit 103 receives the log (search log) (212), it determines whether the related attack event has occurred based on the log.

[0024] In other words, the search process performed by the search unit 103 includes an identification process for identifying related attack events related to the attack event, an acquisition process for acquiring logs to determine whether or not the related attack events identified by the identification process have occurred, and a judgment process for determining whether or not the related attack events have occurred based on the logs acquired by the acquisition process.

[0025] When the search unit 103 determines that the related attack event has occurred, it further executes processes 207 to 212 for the related attack event, identifies related attack events for the related attack event, searches logs, and determines whether related events have occurred. The search unit 103 sequentially searches logs by repeating this process. In other words, when the search unit 103 determines that a certain related attack event has occurred, it repeatedly executes search processes related to the related attack event.

[0026] The search unit 103 passes the log acquired by the above process as a log search result to the transmission unit 104 (213). The transmission unit 104 transmits the received log search result to the center 114 (214).

[0027] By the above process, when it is determined that some attack event has occurred, it is possible to obtain only the log related to the attack event from the in-vehicle device 112 and transmit it to the center 114. In the case of a data structure in which attack events are organized in a tree shape, such as FT (Fault Tree) as in Patent Document 1, the number of patterns, i.e., the number of trees, tends to be enormous. However, in this embodiment, the amount of data required for searching logs can be reduced by organizing the data prepared in advance as related attack event information indicating the relationship between attack events and attack event related log information indicating the relationship between attack events and logs. In addition, by sequentially collecting logs while determining whether or not a related attack event has occurred, it is possible to selectively collect logs related to attack events that are likely to have occurred, and it is possible to obtain logs more efficiently than a method of obtaining logs all at once.

[0028] The receiving unit 105 is a functional unit that receives (215) an additional search request from the center 114 and passes (216) it to the searching unit 103. The searching unit 103 searches the log in accordance with the additional search request and transmits the results to the center 114 again via the transmitting unit 104.

[0029] FIG. 3 is a diagram showing an example of the contents of the constant monitoring attack event DB 108. As shown in FIG. The continuous monitoring attack event DB 108 is a DB in which a log 302 and a condition 303 that are the basis for determining that an attack event has occurred are linked to an attack event 301 that is a constant monitoring target. That is, if a log 302 that satisfies the condition 303 exists, the determination unit 102 determines that an attack event 301 corresponding to the log 302 has occurred. In this embodiment, for example, an attack against an in-vehicle IDS (Intrusion Detection System) is always monitored, and if a log of the in-vehicle IDS that includes the condition "character string 'Detection Rule changed'" is detected, it is determined that an attack event, that is, a rule change of the in-vehicle IDS by a third party, has occurred. The continuous monitoring attack event DB 108 may include multiple records that share the same attack event 301. In this case, if a log that meets any of the pairs of the log 302 and the condition 303 linked to the same attack event 301 exists, it is determined that the attack event 301 has occurred.

[0030] Note that FIG. 3 is an example of the constant monitoring attack event DB 108, and the data structure may be such that more complicated conditions can be set for determining that an attack event has occurred.

[0031] FIG. 4 is a diagram showing an example of the contents of the related attack event DB 106. As shown in FIG. In the related attack event DB 106 in this embodiment, one of the attack events that is likely to have been executed before an attack event 401 occurs is associated with the attack event 401 as a preceding attack event 402. In addition, a time range to be searched in a log search process by the search unit 103 described later is specified as a search target time 403. The search unit 103 determines whether a preceding attack event 402 has occurred for the attack event 401 based on logs going back by the search target time 403 before the occurrence time of the attack event 401. For example, if the contents of the related attack event DB are as shown in FIG. 4 and it is determined that the attack event "sending an unauthorized command from outside to a control ECU" occurred at 10:00 on 2023 / 2 / 20, the search unit 103 searches for logs for determining whether a preceding attack event "changing the in-vehicle IDS rule" has occurred during the period from 10:00 on 2023 / 2 / 19 to 10:00 on 2023 / 2 / 20, and determines whether the preceding attack event has occurred based on the logs.

[0032] In the related attack event DB 106, for example, for an attack event in which a specific operation is performed on a certain ECU, preparations such as obtaining authority to enable the operation, transmission of a signal to cause the ECU to execute the operation, etc. can be associated as preceding attack events. Also, for an attack event in which a signal is sent to a certain ECU, preparations such as obtaining authority and installing unauthorized software to cause a source device to send the signal, and operations for changing the routing table or filtering rules of a communication control device on a communication path to allow a signal to reach a destination ECU from the source device can be associated as preceding attack events.

[0033] In the related attack event DB 106, in addition to associating an attack event with a preceding attack event as in this embodiment, a subsequent attack event that is likely to be executed after the occurrence of the attack event may be associated with the attack event.

[0034] FIG. 5 is a diagram showing an example of the contents of the attack event related log DB 107. As shown in FIG. The attack event related log DB 107 is a DB in which a log 502, a condition 503, and a log type 504 that are the basis for determining that an attack event has occurred are linked to a certain attack event 501. Here, the log type 504 in this embodiment takes two types of values, "direct" and "reference". "Direct" indicates that it is possible to directly determine that the attack event 501 has occurred when a log 502 that satisfies the condition 503 exists, and "reference" indicates that although the log 502 that satisfies the condition 503 is affected by the attack event 501, it is not possible to directly determine that the attack event 501 has occurred simply by the existence of such a log. When a log 502 that satisfies the condition 503 and whose type 504 is "direct" exists, the search unit 103 determines that the attack event 501 corresponding to that log 502 has occurred.

[0035] As shown in FIG. 5, the attack event related log DB 107 may include multiple records with a common attack event 501. In this case, if any of the logs 502 with the type 504 of "direct" that are linked to the same attack event 501 exists and satisfy the corresponding condition 503, it is determined that the attack event 501 has occurred. For example, for the attack event "transmission of unauthorized command from outside to control ECU", if an in-vehicle IDS log that includes the character string "Invalid control message detected" or a CGW (Central GateWay) log that includes the character string "Invalid external message detected" and has the destination as the control ECU exists, it is determined that the attack event has occurred. Note that FIG. 5 is an example of the attack event related log DB 107, and the data structure may be such that, for example, more complex conditions for determining that an attack event has occurred can be set.

[0036] The contents of the constant monitoring attack event DB 108, the associated attack event DB 106, and the attack event related log DB 107 may be written in a machine-readable format so that they can be mechanically processed by the determination unit 102 and the search unit 103. Also, they may be in a format that allows constant monitoring attack event information, associated event information, and attack event related log information for multiple ECUs to be written together.

[0037] FIG. 6 is a flowchart showing an example of a process performed by the log acquisition unit 101. The log acquisition unit 101 requests (601) a log from the in-vehicle device 112 based on the constant monitoring attack event information acquired in advance from the constant monitoring attack event DB 108. For example, in the case of the constant monitoring attack event DB 108 in Fig. 3, the log 302 includes "in-vehicle IDS log", "CGW log", "alert from control ECU", etc., and the log acquisition unit 101 periodically requests these logs from the in-vehicle device 112.

[0038] Next, the log acquisition unit 101 receives the log sent from the in-vehicle device 112 in response to the log request (602), and further transmits the received log to the determination unit 102 (603). As a method of log acquisition, instead of the log acquisition unit 101 periodically requesting logs from the in-vehicle device 112 as in this embodiment, a method in which the in-vehicle device 112 itself periodically transmits logs to be collected to the log acquisition unit 101 may be used.

[0039] 7 is a flowchart showing an example of processing performed by the determination unit 102. When the determination unit 102 receives a log from the log acquisition unit 101, the determination unit 102 refers to the constant monitoring attack event information previously acquired from the constant monitoring attack event DB 108 and judges whether or not a log 302 that satisfies the condition 303 exists (701). If such a log exists, the determination unit 102 judges that the corresponding attack event 301 has occurred, and transfers the attack event 301 and the log that is the basis for its occurrence, that is, the log 302 that satisfies the condition 303, to the search unit 103 (702). Hereinafter, the attack event transmitted to the search unit 103 is called a trigger attack event. At that time, the occurrence time of the trigger attack event is judged based on the log, and the information is also transferred to the search unit 103. If the log 302 that satisfies the condition 303 does not exist, the determination unit 102 ends the processing.

[0040] FIG. 8 is a flowchart showing an example of the process performed by the search unit 103. The main processing of the search unit 103 consists of initial processing of information received from the judgment unit 102 (801-802), a search for logs related to an attack event (803-805), a judgment of whether an attack event has occurred or not (806), processing when an attack event has occurred (807-808), processing when an attack event has not occurred (809-810), a judgment of the search termination conditions (811), and the transfer of collected logs (812).

[0041] First, the search unit 103 adds the log received from the judgment unit 102 to the transmission target log list 109 (801). Here, the transmission target log list is a list that stores logs to be passed to the transmission unit 104 in process 812, which will be described later. At this time, the log may be added to the transmission target log list in association with the trigger attack event information received from the judgment unit 102 as information to be used as a reference for log analysis at the center 114.

[0042] Next, the search unit 103 refers to the related attack event DB 106 for the trigger attack event received from the judgment unit 102 to identify related attack events, and adds them to the search target attack event list 110 (802). Here, the search target attack event list is a list that stores attack events that are the target of the process of searching for related logs (803 to 805). In process 802, the search unit 103 first searches and acquires from the related attack event DB 106 related attack event information in which the "attack event" column 401 in the related attack event DB 106 is the trigger attack event (see FIG. 4). Then, the search unit 103 adds the attack event included in the "preceding attack event" column 402 of the acquired related attack event information to the search target attack event list 110. At this time, the start time and end time of the log search target period are calculated from the occurrence time of the trigger attack event and the "search target time" column 403 of the related event information, and also add them to the search target attack event list 110.

[0043] Next, the search unit 103 extracts (803) one attack event from the search target attack event list 110. At this time, information on the start time and end time of the search target period recorded in the search target attack event list is also acquired.

[0044] The search unit 103 then identifies the relevant logs for the extracted attack event (804). In process 804, the search unit 103 first refers to the attack event related log DB 107 for the extracted attack event, and searches for and acquires attack event related log information in which the "attack event" column 501 is the attack event (see FIG. 5). Then, the log 502 included in the acquired attack event related log information is set as the relevant log.

[0045] Next, the search unit 103 acquires directly related logs, i.e., related logs whose type 504 in the attack event related log DB 107 is "direct", from the in-vehicle device (805). At this time, related logs within the search target period acquired in process 803 are acquired. As a method of acquisition, as described as flows 211 and 212 in Fig. 2, a method in which a log is requested from the in-vehicle device and the in-vehicle device responds to the request, or a method in which the search unit 103 refers to a file in which the log is recorded and acquires it directly may be used. Furthermore, when acquiring directly related logs from the in-vehicle device, the logs may be narrowed down to only directly related logs that may satisfy condition 503 and acquired.

[0046] Next, the search unit 103 judges whether or not there is any directly related log that satisfies the corresponding condition 503 among the acquired directly related logs, and if such a log is present, it judges that an attack event has occurred (806). At this time, the time of occurrence of the attack event is also judged based on the log.

[0047] If it is determined that an attack event has occurred (if "Yes" in 806), the search unit 103 adds the log that is the basis for the determination, i.e., the directly related log that satisfies the corresponding condition 503, to the transmission target log list 109 (807). At this time, the log may be added to the transmission target log list 109 in association with the attack event information as information that serves as a reference for log analysis at the center. Furthermore, the search unit 103 adds related attack events corresponding to the attack event determined to have occurred to the search target attack event list 110 (808). In this process 808, similar to process 802, the search unit 103 searches and acquires related attack event information from the related attack event DB 106 for the attack event determined to have occurred, in which the "attack event" column 401 is the attack event. Then, the attack event included in the "preceding attack event" column 402 of the acquired related attack event information is added to the search target attack event list 110. At this time, the start time and end time of the log search period are calculated from the occurrence time of the attack event that is determined to have occurred and the “search time” column 403 of the related event information, and are also added to the search target attack event list 110.

[0048] On the other hand, if it is not determined that an attack event has occurred in process 806, the search unit 103 acquires reference related logs, that is, related logs whose type 504 is "reference" in the attack event related log DB 107, from the in-vehicle device (809). At this time, related logs within the search target period acquired in process 803 are acquired. Also, at the time of acquiring the reference related logs from the in-vehicle device, only reference related logs that may satisfy the condition 503 may be acquired. Hereinafter, attack events that have not been determined to have occurred among the attack events described in each DB are called undetermined events. Next, it is determined whether or not there is one that satisfies the corresponding condition 503 among the acquired reference related logs, and if such a log exists, it is added to the transmission target log list 109 (810). At this time, as information that serves as a reference for log analysis at the center 114, the log may be added to the transmission target log list in association with the information of the undetermined event. Also, the log may be added to the transmission target log list 109 including information for distinguishing between the direct related log and the reference related log.

[0049] After completing the process 808 or 810, the search unit 103 determines whether the termination condition is satisfied (811). Here, it is assumed that the termination condition is set in the search unit 103 in advance. For example, by setting the capacity of the logs included in the transmission target log list to reach a certain value as the termination condition, the amount of data to be transmitted to the center 114 can be reduced. In addition, for each attack event included in the search target attack event list, the number of search processes until the attack event is added to the search target attack event list 110 can be counted, and the minimum value can be set to reach a certain value as the termination condition. For example, if attack event A is added to the search target attack event list 110 in process 802, and attack event B is added to the search target attack event list 110 in process 808 for attack event A, the number of search processes until attack event B is added to the search target attack event list 110 is two. In process 803, the attack event with the minimum number of search processes before being added to the search target attack event list 110 is extracted, and the termination condition is set to the minimum number of search processes reaching a certain value, so that only logs related to attack events with a search process count below the certain value, that is, attacks highly related to the trigger attack event, can be obtained.

[0050] If the termination condition is satisfied, the search unit 103 passes the logs and associated information included in the log list 109 to be transmitted as log search results to the transmission unit 104. Thereafter, the transmission unit 104 transmits the log search results received from the search unit 103 to the center 114.

[0051] When there is an additional search request from the center 114, the receiving unit 105 receives it and passes it to the searching unit 103. For example, when log analysis at the center 114 determines that there is a high possibility that an undetermined event has occurred, the center 114 may send a search request for logs related to the undetermined event to the receiving unit 105. Alternatively, when it is determined that there is a high possibility that an attack event that was not the target of the search by the searching unit 103 has occurred, a search request for the attack event may be sent to the receiving unit 105.

[0052] FIG. 9 is a diagram showing an example of the process performed by the search unit 103 when a search request for logs related to a specific attack event is received as an additional search request from the receiving unit 105. In FIG.

[0053] The search unit 103 first adds (901) the attack event that is the subject of the additional search request received from the receiving unit 105 to the search target attack event list 110. Thereafter, the search unit 103 executes processes 803 to 812 in the same manner as when attack event information is received from the determining unit 102 (FIG. 8), and passes the log to the transmitting unit 104. Thereafter, the transmitting unit 104 transmits the log received from the search unit 103 to the center 114.

[0054] The above-described embodiment of the present invention provides the following advantageous effects.

[0055] (1) An information processing device according to the present invention includes a log acquisition unit that acquires a log of an in-vehicle device, a judgment unit that determines whether or not a specified target event has occurred among events occurring in the in-vehicle device based on the acquired log, a search unit that executes a search process for the logs when it is determined that the target event has occurred, and a transmission unit that transmits the log acquired by the search process to a center, and the search process includes a determination process that identifies an associated event related to the target event, an acquisition process that acquires a log for determining whether or not the associated event identified by the determination process has occurred, and a judgment process that determines whether or not the associated event has occurred based on the log acquired by the acquisition process.

[0056] With the above configuration, when a security incident occurs, it is possible to narrow down the logs to be transmitted to a center that monitors the vehicle by identifying the logs of the in-vehicle device related to the security incident.

[0057] (2) When no logs are obtained in the search process to determine that a related event has occurred, the transmission unit transmits the logs obtained up to the time of the search process to the center. By analyzing these logs, it becomes possible to perform a more detailed analysis of the related event.

[0058] (3) A receiving unit that receives a request from the center side is further provided, and the search unit executes a search process for the related events that were the subject of the search process as target events in response to the request from the center. In this way, it is possible to perform the search process not only from the device side but also from the center side.

[0059] (4) In response to a request from the center, the search unit executes a search process on other events that were not included in the search process as target events. This increases the possibility of discovering new attack events that were not listed in the database or list.

[0060] (5) The search unit stops the search process when the search process has been repeated a predetermined number of times or when the amount of logs to be transmitted to the center reaches a predetermined amount. This makes it possible to reduce the amount of data to be transmitted.

[0061] (6) When the transmitting unit acquires a log of a predetermined type that indicates a higher relevance to the occurrence of an event than other types, the transmitting unit transmits the log of the predetermined type to the center, excluding the logs of the other types. In other words, by transmitting only important logs to the center, it is possible to suppress the amount of data to be transmitted, as in (5).

[0062] (7) When it is determined that a related event has occurred, the search unit repeatedly executes a search process on the related event as a target event, thereby making it possible to sequentially discover related attack events.

[0063] (8) When the transmission unit does not receive a log of a specific type that indicates a higher relevance to the occurrence of an event than other types, the transmission unit transmits logs of the other types to the center. By analyzing such logs, the possibility of discovering a new attack event is increased.

[0064] 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]

[0065] 100 Information processing device, 101 Log acquisition unit, 102 Judgment unit, 103 Search unit, 104 Transmission unit, 105 Reception unit, 112 Vehicle-mounted device, 114 Center

Claims

1. a log acquisition unit that acquires a log of the in-vehicle device; a determination unit that determines whether or not a predetermined target event has occurred among events that occur in the in-vehicle device based on the acquired log; a search unit that executes a search process of the log when it is determined that the target event has occurred; a transmission unit that transmits the log acquired by the search process to a center, The search process includes: A process of identifying a related event related to the target event; an acquisition process for acquiring a log for determining whether or not the related event identified by the identification process has occurred; A determination process for determining whether or not the related event has occurred based on the log acquired by the acquisition process.

23. An information processing apparatus comprising:

2. 2. The information processing device according to claim 1, when the log for determining that the related event has occurred is not acquired in the search process, the transmission unit transmits the log acquired up to the search process to the center.

23. An information processing apparatus comprising:

3. 3. The information processing device according to claim 2, A receiving unit for receiving a request from the center side is further provided, the search unit executes the search process in response to a request from the center, with the related event that was the target of the search process as the target event.

23. An information processing apparatus comprising:

4. 4. The information processing device according to claim 3, the search unit executes the search process by treating other events that were not the target of the search process as the target events in response to a request from the center.

23. An information processing apparatus comprising:

5. 2. The information processing device according to claim 1, the search unit stops the search process when the search process has been repeated a predetermined number of times or when the log to be transmitted to the center has been acquired to a predetermined capacity or more.

23. An information processing apparatus comprising:

6. 2. The information processing device according to claim 1, when acquiring the log of a predetermined type that indicates a higher relevance to the occurrence of the event than other types, the transmission unit transmits the log of the predetermined type to the center, excluding the logs of the other types.

23. An information processing apparatus comprising:

7. 2. The information processing device according to claim 1, when it is determined that the related event has occurred, the search unit repeatedly executes a search process with the related event as the target event.

23. An information processing apparatus comprising:

8. 2. The information processing device according to claim 1, when the transmission unit has not acquired the log of a predetermined type that indicates a higher relevance to the occurrence of the event than other types, the transmission unit transmits the log of the other type to the center.

23. An information processing apparatus comprising:

Citation Information

Patent Citations

  • On-vehicle device and log collection system

    JP2018032254A

  • Program, method, and device for assisting cyberattack analysis

    JP2018032355A

  • Cyber attack analysis support device

    JP2021117568A

  • Information processing device, information processing method and program

    JP2022007238A

  • Log analyzer

    JP2022024266A