Information processing device

The information processing device efficiently identifies and transmits relevant vehicle logs during security incidents by using a log acquisition, determination, and search unit, addressing the challenges of data complexity and communication interruptions, ensuring timely and accurate data delivery to the monitoring center.

WO2024241727A1PCT designated stage expired Publication Date: 2024-11-28ASTEMO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/014152
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2024-04-05
Publication Date
2024-11-28

Smart Images

  • Figure JP2024014152_28112024_PF_FP_ABST
    Figure JP2024014152_28112024_PF_FP_ABST
Patent Text Reader

Abstract

An information processing device 100 comprises: a log acquisition unit 101 that acquires a log of an onboard device 112; a determination unit 102 that, on the basis of the acquired log, determines whether a prescribed event of interest has occurred among events occurring in the onboard device 112; a search unit 103 that executes a log search process when it is determined that the event of interest has occurred; and a transmission unit 104 that transmits the log acquired by using the search process to a center. The search process includes an identification process for identifying a related event that is related to the event of interest, an acquisition process for acquiring a log for use in determining whether the related event identified by using the identification process has occurred, and a determination process for determining whether the related event has occurred on the basis of the log acquired by using the acquisition process.
Need to check novelty before this filing date? Find Prior Art

Description

Information processing device

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

[0002] Connected cars, which enable various functions by connecting cars to the Internet, are becoming increasingly popular. 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, studies have been underway on vehicle security operation centers (VSOCs) that continuously monitor the status of vehicles in use, analyze the cause of security incidents when they occur, and respond by remotely controlling the vehicles, etc. The security operation center collects data such as logs from vehicles, identifies the cause of incidents through manual analysis by analysts or automatic analysis by a system, and plans necessary responses.

[0004] However, as in-vehicle systems become more complex, the amount of data that can be acquired in vehicles is increasing, and transmitting all of that data to the center would consume 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 communication bandwidth consumption.

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

[0006] Japanese Patent Application Laid-Open No. 2021-027505

[0007] However, the technology disclosed in Patent Document 1 requires communication with a monitoring device to determine which logs to collect. Therefore, if communication is interrupted, such as when the vehicle is traveling in a tunnel or outside of a communication range, the vehicle cannot collect logs. Therefore, in order to send logs to the monitoring device when communication is restored, it is necessary to store logs that the monitoring device may collect in the vehicle. This can result in problems such as consuming storage space in the in-vehicle system or being unable to send 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 the vehicle's limited resources when a security incident occurs in the vehicle.

[0009] An example of an information processing device according to the present invention includes a log acquisition unit that acquires logs of an in-vehicle device, a judgment unit that determines 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 log 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, wherein the search process includes a specification process that identifies related events related to the target event, an acquisition process that acquires logs to determine whether or not the related events identified by the specification process have occurred, and a judgment process that determines whether or not the related events have occurred based on the logs acquired by the acquisition process.

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

[0011] 1 is a block diagram showing the functional configuration of an information processing device in an embodiment of the present invention. FIG. 2 is a block diagram showing an overview of the processing flow performed by an information processing device in an embodiment of the present invention. FIG. 3 is a diagram showing an example of the contents of a continuous monitoring attack event DB in an embodiment of the present invention. FIG. 4 is a diagram showing an example of the contents of a related attack event DB in an embodiment of the present invention. FIG. 5 is a diagram showing an example of the contents of an attack event related log DB in an embodiment of the present invention. A flowchart showing the processing performed by a log acquisition unit in an embodiment of the present invention. A flowchart showing the processing performed by a judgment unit in an embodiment of the present invention. A flowchart showing the processing performed by a search unit in an embodiment of the present invention. A flowchart showing the processing performed by a search unit in response to an additional search request in an embodiment of the present invention.

[0012] 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 apparatus 100 according to an embodiment of the present invention will be described. The information processing apparatus 100 may be a computer having, for example, a memory and a processor as a hardware configuration.

[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 determination 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 continuous 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 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 the respective communication buses 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 apparatus 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 this. 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 by functional units not shown in Fig. 1.

[0018] FIG. 2 is a diagram showing an overview of the overall processing flow performed by the information processing device 100. 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 continuous monitoring attack event information in advance from the continuous monitoring attack event DB 108 (201). Here, the continuous monitoring attack event DB 108 is a database that stores attack events of monitored targets, and details will be described later. An attack event is an event caused by an attack on an in-vehicle device. The continuous monitoring attack event information is information that indicates an attack event that is constantly monitored for occurrence and a log that serves as 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 continuous 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 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 continuous monitoring attack event information in advance from the continuous monitoring attack event DB 108 (205). When the determination unit 102 receives the log from the log acquisition unit 101, it determines whether or not some attack event has occurred based on the log information. If it is determined that an attack event has occurred, it transmits attack event information regarding the attack event to the search unit 103 (206).

[0022] The search unit 103 is a functional unit that, when it is determined that an attack event has occurred, executes a log search process based on the attack event information received from the determination unit 102. When the search unit 103 receives attack event information from the determination 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 that indicates 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 uses the related attack event information to identify other attack events related to the attack event information received from the determination unit 102.

[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 logs related to the related attack event, and requests the logs 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 a related attack event has occurred, it further executes processes 207 to 212 for the related attack event, identifying related attack events for the related attack event, searching logs, and determining whether related events have occurred. The search unit 103 sequentially searches logs by repeating this process. In other words, when it determines that a certain related attack event has occurred, the search unit 103 repeatedly executes search processes related to the related attack event.

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

[0027] The above process makes it possible, when it is determined that an attack event has occurred, to acquire only logs related to the attack event from the in-vehicle device 112 and transmit them to the center 114. In the case of a data structure in which attack events are organized in a tree-like manner, such as a Fault Tree (FT) as in Patent Document 1, the number of patterns, i.e., the number of trees, tends to become enormous. However, in this embodiment, the amount of data required for log search 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. Furthermore, by sequentially collecting logs while determining whether related attack events have occurred, it is possible to selectively collect logs related to attack events that are likely to have occurred, thereby enabling more efficient log acquisition than a method of acquiring 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 illustrating an example of the contents of the continuous monitoring attack event DB 108. The continuous monitoring attack event DB 108 is a DB that links a log 302 and a condition 303, which are the basis for determining that an attack event has occurred, to an attack event 301 that is a continuous 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, attacks against an in-vehicle IDS (Intrusion Detection System) are constantly monitored, and if a log from the in-vehicle IDS is detected that includes the condition "character string 'Detection Rule changed'," it is determined that an attack event has occurred in the form of a rule change of the in-vehicle IDS by a third party. The continuous monitoring attack event DB 108 may include multiple records that share the same attack event 301. In this case, if there is a log that matches any of the pairs of logs 302 and conditions 303 that are linked to the same attack event 301, it is determined that the attack event 301 has occurred.

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

[0031] 4 is a diagram showing an example of the contents of the related attack event DB 106. In the related attack event DB 106 of this embodiment, when an attack event 401 occurs, one of the attack events that is likely to have been executed before the attack event occurs is associated with the attack event 401 as a preceding attack event 402. In addition, the time range to be searched in the log search process by the search unit 103, which will be 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 Figure 4 and it is determined that the attack event "sending an unauthorized command from outside to the control ECU" occurred at 10:00 on 2023 / 2 / 20, the search unit 103 searches for logs to determine whether the preceding attack event "changing the in-vehicle IDS rules" occurred, covering the period from 10:00 on 2023 / 2 / 19 to 10:00 on 2023 / 2 / 20, and based on the results, determines whether the preceding attack event occurred.

[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 perform 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 malicious software to cause a source device to send the signal, and operations to change the routing table or filtering rule 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 also 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. The attack event-related log DB 107 is a DB that associates a log 502, a condition 503, and a log type 504, which are the basis for determining that an attack event has occurred, with a certain attack event 501. Here, the log type 504 in this embodiment takes two values: "direct" and "reference." "Direct" indicates that it is possible to directly determine that the attack event 501 has occurred if a log 502 that satisfies the condition 503 exists. "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. If 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 sharing a common attack event 501. In this case, if any of the logs 502 associated with the same attack event 501 and having a type 504 of "direct" exists and satisfy the corresponding condition 503, the attack event 501 is determined to have occurred. For example, for the attack event "transmission of an unauthorized command from outside to a control ECU," the attack event is determined to have occurred if an in-vehicle IDS log containing the string "Invalid control message detected" or a CGW (Central Gateway) log containing the string "Invalid external message detected" and having the destination as the control ECU exists. Note that FIG. 5 is an example of the attack event-related log DB 107, and the DB may have a data structure that allows for the setting of more complex conditions for determining that an attack event has occurred.

[0036] The contents of the continuous monitoring attack event DB 108, the related 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. In addition, they may be in a format that allows continuous monitoring attack event information, related event information, and attack event related log information for multiple ECUs to be written together.

[0037] 6 is a flowchart showing an example of processing performed by the log acquisition unit 101. The log acquisition unit 101 requests a log from the in-vehicle device 112 based on constant monitoring attack event information previously acquired from the constant monitoring attack event DB 108 (601). For example, in the case of the constant monitoring attack event DB 108 in FIG. 3, the log 302 contains an "in-vehicle IDS log," a "CGW log," an "alert from the control ECU," and the like, 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 also 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, it references the continuous monitoring attack event information previously acquired from the continuous monitoring attack event DB 108 and determines whether a log 302 that satisfies the condition 303 exists (701). If such a log exists, it determines that a corresponding attack event 301 has occurred, and passes the attack event 301 and the log that was the basis for its occurrence, i.e., the log 302 that satisfies the condition 303, to the search unit 103 (702). Hereinafter, the attack event sent to the search unit 103 is referred to as a trigger attack event. At this time, the time of occurrence of the trigger attack event is determined based on the log, and this information is also passed to the search unit 103. If no log 302 that satisfies the condition 303 exists, the determination unit 102 terminates processing.

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

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

[0042] The search unit 103 then identifies related attack events for the trigger attack event received from the determination unit 102 by referring to the related attack event DB 106, and adds the identified attack events 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 processes (803 to 805) for searching for related logs. In process 802, the search unit 103 first searches for and acquires related attack event information from the related attack event DB 106, for which the "attack event" column 401 in the related attack event DB 106 identifies the trigger attack event (see FIG. 4). The search unit 103 then adds attack events 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 these are also added to the search target attack event list 110.

[0043] Next, the search unit 103 extracts one attack event from the search target attack event list 110 (803). 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 obtained.

[0044] The search unit 103 then identifies the logs associated with 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 indicates the attack event (see FIG. 5). Then, the log 502 included in the acquired attack event-related log information is designated as the associated log.

[0045] The search unit 103 then 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 for acquiring logs, as described in flows 211 and 212 of 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 references a file in which the log is recorded and acquires the logs directly, may be used. Furthermore, when acquiring directly related logs from the in-vehicle device, the logs may be narrowed down to only those that may satisfy condition 503.

[0046] The search unit 103 then determines whether or not any of the acquired directly related logs satisfies the corresponding condition 503, and if such a log is found, determines that an attack event has occurred (806). At this time, the time of occurrence of the attack event is also determined based on the log.

[0047] If it is determined that an attack event has occurred ("Yes" in 806), the search unit 103 adds the log that served as the basis for the determination, i.e., the directly related log that satisfies the corresponding condition 503, to the log list 109 to be sent (807). At this time, the log may be added to the log list 109 in association with the attack event information as reference information 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, as in 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, where the "attack event" column 401 indicates 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 target 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 in process 806 that an attack event has occurred, the search unit 103 acquires reference related logs, i.e., related logs whose type 504 is set to "reference" in the attack event related log DB 107, from the in-vehicle device (809). At this time, the search unit 103 acquires related logs within the search target period acquired in process 803. Furthermore, when acquiring reference related logs from the in-vehicle device, the acquired logs may be narrowed down to only reference related logs that may satisfy condition 503. Hereinafter, attack events recorded in each DB that have not been determined to have occurred are referred to as "undetermined events." Next, it is determined whether any of the acquired reference related logs satisfy the corresponding condition 503, and if any such logs exist, they are added to the log list 109 to be sent (810). At this time, the log may be added to the log list 109 in association with the information on the undetermined event as information useful for log analysis at the center 114. Furthermore, information for distinguishing between directly related logs and reference related logs may also be included in the log list 109 to be sent.

[0049] After completing process 808 or 810, the search unit 103 determines whether the termination condition is met (811). Here, it is assumed that the termination condition is set in the search unit 103 in advance. For example, by setting the volume of logs included in the log list to be sent reaching a certain value as the termination condition, the amount of data transmitted to the center 114 can be reduced. Furthermore, 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 will be 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 by using the minimum number of search processes reaching a certain value as the termination condition, it is possible to obtain only logs related to attack events with a search process count below a certain value, i.e., attack events that are highly related to the trigger attack event.

[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 an additional search request is received from the center 114, the receiving unit 105 receives it and passes it to the searching unit 103. For example, if the 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, if there is a high possibility that an attack event that was not the target of the search by the searching unit 103 has occurred, the receiving unit 105 may send a search request for the attack event.

[0052] FIG. 9 is a diagram showing an example of processing 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.

[0053] The search unit 103 first adds the attack event that is the target of the additional search request received from the receiving unit 105 to the search target attack event list 110 (901). 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) The information processing device of the present invention includes a log acquisition unit that acquires logs of an in-vehicle device, a judgment unit that determines whether 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 log search process 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 specification process that identifies related events related to the target event, an acquisition process that acquires logs to determine whether the related events identified by the specification process have occurred, and a judgment process that determines whether the related events have occurred based on the logs 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 sent to the center that monitors the vehicle by identifying the logs of the in-vehicle device related to the security incident.

[0057] (2) When the search process does not acquire a log for determining that a related event has occurred, the transmission unit transmits the logs acquired 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 is further provided for receiving requests from the center side, and the search unit executes search processing in response to the request from the center, with the related events that were the subject of the search processing as the target events. In this way, search processing can be performed 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 performs a search process on events that were not previously included in the search process, thereby increasing the possibility of discovering new attack events that were not included in the database or list.

[0060] (5) The search unit stops the search process when it has repeated the search process 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 transmitter acquires a log of a predetermined type that indicates a higher relevance to the occurrence of an event than other types, the transmitter excludes the logs of the predetermined type and transmits the logs of the predetermined type to the center. In other words, by transmitting only important logs to the center, it is possible to reduce 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 for the related event as a target event, thereby enabling related attack events to be sequentially discovered.

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

[0064] It should be noted that the present invention is not limited to the above-described embodiments, and various modifications are possible. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to embodiments that include all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment. It is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to delete part of the configuration of each embodiment, or to add or replace other configurations.

[0065] 100 Information processing device, 101 Log acquisition unit, 102 Determination unit, 103 Search unit, 104 Transmission unit, 105 Reception unit, 112 In-vehicle device, 114 Center

Claims

1. An information processing device comprising: a log acquisition unit that acquires logs of an in-vehicle device; a judgment unit that judges whether 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 of the log when it is judged that the target event has occurred; and a transmission unit that transmits the log acquired by the search process to a center, wherein the search process includes: an identification process that identifies associated events related to the target event; an acquisition process that acquires the log to judge whether the associated event identified by the identification process has occurred; and a judgment process that judges whether the associated event has occurred based on the log acquired by the acquisition process.

2. An information processing device as described in claim 1, characterized in that, when the log for determining that the related event has occurred in the search process is not acquired, the transmission unit transmits the log acquired up to the time of the search process to the center.

3. An information processing device as described in claim 2, further comprising a receiving unit for receiving a request from the center, and wherein the search unit, in response to the request from the center, executes the search process by treating the related event that was the subject of the search process as the target event.

4. An information processing device according to claim 3, wherein 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.

5. An information processing device according to claim 1, characterized in that the search unit stops the search process when the search process has been repeated a predetermined number of times or when the logs to be transmitted to the center have reached a predetermined volume or more.

6. An information processing device as described in claim 1, characterized in that when the transmission unit acquires a log of a specified type that indicates a higher relevance to the occurrence of the event than other types, the transmission unit transmits the log of the specified type to the center, excluding the logs of the other types.

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

8. An information processing device as described in claim 1, characterized in that when the transmission unit does not obtain a log of a specified 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.

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