Intrusion response system and method
Through the combination of software-defined network (SDN) technology and intrusion detection system (IDS), the computing power limitation of intrusion detection and response in IVN is solved, and high-performance detection and attack blocking of IVN are realized, and detection accuracy and response are improved. efficiency.
Patent Information
- Application Number
- CN202080055847.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-07-30
- Filing Date
- 2020-07-31
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-07-31
AI Technical Summary
The prior art is difficult to effectively detect and respond to intrusions or attacks in on-board networks (IVNs), especially due to the limitation of computing power, the intrusion detection system (IDS) only supports lightweight algorithms and cannot effectively respond to the risks of IVN vehicles.
Using software-defined network (SDN) technology, the switch and SDN controller are supported through SDN, and the data packet flow is controlled and monitored using the flow table, combined with the intrusion detection system (IDS) for intrusion detection and response, real-time monitoring of IVN and blocking attacks. traffic.
It realizes high-performance intrusion detection and response to IVN, can remotely judge and prevent intrusion packets, reduce the impact of the vehicle's internal environment on detection, and allows real-time update of the detection algorithm, improving the monitoring accuracy of internal traffic of multiple vehicles.
Smart Images

Figure CN114208116B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a technique for detecting and preventing intrusions or attacks on an in-vehicle network (IVN). Background Art
[0002] The contents described in this section are merely to provide background information for the present embodiment and do not constitute prior art.
[0003] Commercial vehicles that apply vehicle-to-everything (V2X) communication and network-based autonomous driving related technologies have been developed. However, commercial vehicles that apply V2X communication and vehicle networks are vulnerable to attacks that intrude into the communication network or network communications. Figure 1 is a diagram showing the classification of security threat types for vehicles. Attacks that threaten vehicle security include privilege theft attacks and non-privilege theft attacks, external attacks based on attack sources, and internal attacks targeting internal components of the vehicle. Internal attacks are usually carried out by attackers with physical access to the target vehicle to cause obvious damage, while external attacks mainly use sensor-based systems such as short-range radio frequency communications, keyless entry systems, or tire pressure monitoring systems, so their impact is limited. However, with the increase in intra-vehicle connectivity in IVN environments and inter-vehicle connectivity in V2X environments, the impact of external vehicle attacks is expected to increase.
[0004] Even when an attack or intrusion is properly detected, how to mitigate the attack or intrusion has always been a problem. Previously proposed mitigation methods are not adequate alternatives to IVN vehicle attacks.
[0005] In other words, there is a lack of development of a technical framework for detecting and appropriately responding to risks in vehicles that support V2X and IVN. Currently, due to the limitations of the computing power of the vehicle system, the intrusion detection system (IDS) installed in the vehicle only supports lightweight algorithms to a limited extent. Therefore, it is necessary to design an intrusion response system (IRS) for detecting and responding to intrusions that overcomes this limitation of computing power. Summary of the invention
[0006] Technical issues
[0007] The present disclosure provides a method for detecting and responding to attacks on an Ethernet-based in-vehicle network (IVN) using software-defined networking (SDN) technology and a system using the method.
[0008] Technical Solution
[0009] According to one aspect of the present disclosure, an intrusion response system for an in-vehicle network (IVN) is provided. The intrusion response system is characterized in that it includes: a software defined network (SDN) support switch, which is installed in the IVN of the vehicle and controls the flow of incoming data packets by referring to the flow entry from the flow table; and an SDN controller, which communicates with the SDN support switch, receives the flow table from the SDN support switch at a certain time interval T to perform monitoring, and transmits the monitoring result to the SDN support switch. The SDN controller transmits the flow table to an intrusion detection system (IDS) so that the IDS performs intrusion detection, and receives the result of performing intrusion detection as the monitoring result from the IDS.
[0010] According to another aspect of the present disclosure, a method for detecting and responding to vehicle intrusion using a software defined network (SDN) support switch mounted in an in-vehicle network (IVN) of a vehicle and an SDN controller disposed outside the vehicle is provided. The method is characterized in that it includes: the SDN support switch transmits a flow table to the SDN controller at a certain time interval T; the SDN controller receives the flow table and transmits the received flow table to an intrusion detection system (IDS); the SDN controller causes the IDS to perform intrusion detection based on all or part of the fields of each flow entry included in the flow table, and the SDN controller receives the result of the intrusion detection from the IDS; the SDN controller transmits a packet output message (packet-outmessage) including the result of the intrusion detection to the SDN support switch; and the SDN support switch updates the flow table based on the packet output message.
[0011] Beneficial Effects
[0012] The SDN-supported switch of the present disclosure can monitor and block the traffic flowing into the IVN at the same time. That is, the SDN-supported switch can selectively block the traffic identified as an attack while monitoring the traffic flowing into the vehicle based on the flow table.
[0013] According to the present disclosure, judging whether a data packet flowing into a vehicle is an intrusion data packet and executing a flow control action is determined remotely rather than in the IVN, so that the intrusion data packet can be detected based on a high-performance detection technology requiring high computing performance such as deep learning or artificial intelligence methods, regardless of the internal environment of the vehicle, and an appropriate response command can be given according to the detection result. In addition, the intrusion detection system set outside the vehicle can change or update the detection algorithm or model in real time regardless of the vehicle environment.
[0014] In addition, according to the present disclosure, internal traffic occurring in multiple vehicles can be monitored simultaneously and comprehensively in one place. This can achieve more accurate attack detection by collecting fuzzy anomalies that are difficult to detect from a single vehicle and comparing the collected anomalies with normal traffic of other vehicles.
[0015] The technology of the present disclosure can also be applied by adding SDN devices to ordinary switches set in existing Ethernet-based vehicles. Therefore, the technology of the present disclosure can be applied while minimizing the change of the topology structure of the Ethernet-based IVN. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 is a diagram illustrating classification of security threat types of a vehicle.
[0017] Figure 2 is a conceptual diagram showing the architecture of a typical software defined network (SDN).
[0018] Figure 3 The diagram shows the SDN controller and SDN devices that constitute the SDN system and the constituent fields of the flow entries that constitute the flow table installed in the SDN device.
[0019] Figure 4 is a conceptual diagram schematically showing a structure of an intrusion response system according to an embodiment of the present disclosure.
[0020] Figure 5A and Figure 5B is a diagram illustrating an exemplary topological structure of an in-vehicle network (IVN) according to an embodiment of the present disclosure.
[0021] Fig. 6A and Figure 6B 1 is a diagram showing a control plane topology structure of a centralized structure and a distributed structure of an intrusion response system according to an embodiment of the present disclosure.
[0022] Fig. 7A and Figure 7B is a diagram illustrating a topological structure of an intrusion detection system (IDS) applicable to an intrusion response system according to an embodiment of the present disclosure.
[0023] Figure 8 is a diagram illustrating a use case scenario supporting the usefulness of an intrusion response system in accordance with the present disclosure.
[0024] Fig.9A and Fig. 9B is a flow chart showing a data-driven intrusion detection and response method according to the present embodiment. DETAILED DESCRIPTION
[0025] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that when adding reference numerals to components in the various drawings, the same reference numerals represent the same components, although these components are shown in different drawings. In addition, in the following description of the present disclosure, detailed descriptions of related known functions and configurations will be omitted so as not to make the gist of the present disclosure unclear.
[0026] In addition, various terms such as first, second, A, B, (a), (b), etc. are only used to distinguish one component from another component, and are not used to imply or indicate the nature, order or sequence of the components. Throughout this specification, when a component "includes" or "includes" a component, unless otherwise explicitly stated, it means that the component further includes other components, and does not exclude the inclusion of other components. In addition, terms such as "unit", "module", etc. recorded in the specification refer to one or more units for processing at least one function or operation, which can be implemented by hardware, software, or a combination of hardware and software.
[0027] The detailed description, given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention rather than merely to show embodiments that can be implemented according to the present invention.
[0028] The present disclosure relates to an intrusion response method and an intrusion response system for detecting and responding to attacks on an Ethernet-based in-vehicle network (IVN) using software defined network (SDN) technology.
[0029] SDN is a technology that separates the control part of network devices such as switches and routers from the data transmission part of the network devices, provides an open interface to the outside that can define the functions of the network devices, and uses programmed software to set up, control and manage various network paths through the open interface.
[0030] Figure 2It is a conceptual diagram showing the architecture of a typical SDN. The SDN architecture is defined as three layers, including an application layer, a control layer, and an infrastructure layer. The application layer, the control layer, and the infrastructure layer are also referred to as the application plane, the control plane, and the infrastructure plane (or data plane), respectively. The layers communicate with each other through open interfaces. The open interface between the application layer and the control layer, referred to as the "northbound API", is an API that enables the development of applications with various functions and communication with other running tools. The RESTful API is generally used in the northbound API. The open interface between the control layer and the infrastructure layer, referred to as the "southbound API", is an interface for forwarding control, information collection, etc., and may include, for example, OpenFlow, OF-config, Netconf, etc.
[0031] Figure 3 An SDN system including an SDN controller and an SDN device, and fields of flow entries included in a flow table mounted in the SDN device are shown. The SDN controller is a logical entity, which is set on the control plane of the SDN system, and the SDN device is a hardware device, which is set on the data plane. The flow table mounted in the SDN device includes the following three main fields to process data packets received by the SDN device. The main fields include packet header information (RULE field) defining the flow, an action (ACTION) field indicating how to process the data packet, and a STATS field representing statistics for each flow. The controller can create a flow table in the switch using a southbound API that includes the function of registering a new flow or deleting a flow.
[0032] Figure 4 is a conceptual diagram schematically showing a structure of an intrusion response system (IRS) according to an embodiment of the present disclosure.
[0033] As described above, the intrusion response system 400 of the present disclosure utilizes SDN technology. Since SDN is a virtualized architecture, its components do not need to be physically arranged in the same location. According to the intrusion response system 400 of the present disclosure, an in-vehicle network (IVN) having an SDN-supporting switch (referred to as an SDN switch (SDN Switch)) 410 is arranged on the data plane of the SDN system, an SDN controller 420 is arranged on the control plane of the SDN system, and an intrusion detection system (IDS) 430 is arranged on the application plane of the SDN system.
[0034] The intrusion response system 400 separates a logical or physical entity from the IVN, which determines whether there is an intrusion by analyzing the statistical data of vehicles and traffic, and determines the response according to the judgment result. The operating subject of the IDS 430 may be different from the operating subject of the SDN controller 420 .
[0035] The SDN support switch 410 provided in the IVN controls the traffic occurring in the IVN or the traffic flowing into the IVN based on the flow table. The SDN controller 420 provided outside the vehicle and connected to the vehicle through V2I communication periodically receives the flow table from the SDN support switch 410 at a certain time interval, and receives the result of performing intrusion detection as a monitoring result of the received flow table from the IDS so that the SDN support switch 410 updates the flow table.
[0036] Hereinafter, functions and operations of the SDN supporting switch 410 , the SDN controller 420 , and the IDS 430 in the proposed intrusion response system 400 will be described in detail.
[0037] The SDN support switch 410 is mounted in the vehicle and controls the flow of all traffic or data packets (hereinafter collectively referred to as "data packets") flowing into the IVN or V2X communication of the vehicle. The SDN support switch 410 can be an SDN switch or a common switch combined with an SDN device to operate in an SDN environment, but it is not limited thereto. For example, the SDN support switch 410 according to the present embodiment can be any switch as long as the switch can control the flow of data packets generated in the IVN of the vehicle or in the V2X environment and can communicate with the SDN controller 420 of the control plane.
[0038] The SDN support switch 410 uses a flow table to control data packets flowing into the SDN support switch 410. According to one aspect of the present embodiment, the SDN support switch 410 matches data packet related data such as port information with the rule field of each flow entry in the flow table, and extracts or references the flow entry that matches the specific data packet. This matching varies according to the specification of the southbound API corresponding to the communication protocol between the SDN support switch 410 and the SDN controller 420. For example, Figure 4 As shown, the rule field of the flow entry may include a switch port, a MAC source, an Ethernet type, a VLAN ID, an IP source, etc. In this case, a match between the data packet data and the flow entry may be established by a full match relative to the specification of the rule field, a match within a preset range, or a match above a preset number. In this case, there may be multiple flow entries that match a specific data packet.
[0039] When there is a flow entry matching the incoming data packet, the SDN supporting switch 410 extracts the flow entry and executes the command of the action field of the flow entry. According to one aspect of this embodiment, when there are multiple flow entries matching the incoming data packet, the SDN supporting switch 410 can extract the flow entry with the highest priority among the multiple flow entries using a priority field included in each flow entry.
[0040] Transmitting all packets flowing into the SDN supporting switch 410 to the SDN controller 420 may result in privacy violation and waste of resources. Therefore, according to one aspect of the present embodiment, when packet control cannot be performed using only the flow table, for example, when there is no flow entry matching the incoming packet and the validity period of the matching flow entry has expired, a packet input message including the incoming packet may be transmitted to the SDN controller 420. The packet input message is generated according to the interface used by the SDN supporting switch 410 and the SDN controller 420. The SDN controller 420 may transmit a packet output message including the packet and the forwarding action included in the packet input message to the SDN supporting switch 410. The SDN supporting switch 410 appropriately controls the incoming packet by updating the flow table based on the received packet output message.
[0041] Optionally, the SDN support switch 410 may adopt a data-driven intrusion detection method using the flow table-based control function of the SDN support switch 410 for all packet data. In the data-driven intrusion detection method, the SDN support switch 410 transmits the flow table to the SDN controller 420 at a certain time interval "T" or in response to a query for requesting the flow table received from the SDN controller 420 at a certain time interval "T" so as to perform intrusion detection, and the SDN support switch 410 receives the result of the intrusion detection from the SDN controller 420 and updates the flow table based on the result of the intrusion detection. In the data-driven intrusion detection method, packet control and intrusion detection are performed separately.
[0042] Here, the time interval "T" at which the SDN controller 420 receives the flow table may be set or reset based on all or part of the internal or external environment of the vehicle, the driving environment, the intrusion detection method adopted by the IDS 430, and the result of performing the intrusion detection. The setting or resetting of the time interval "T" may be determined by the SDN supporting switch 410 based on the packet output message received from the SDN controller 420, may be determined by the SDN controller 420 based on monitoring of the received packet input message or packet flow, or may be determined by the IDS 430.
[0043] The data packet output message may include the result of the intrusion detection. For example, when it is determined that an intrusion exists, the data packet output message may include rules that can filter out intrusion packets or attacks and corresponding responses (e.g., packet drop actions, packet drop and source blocking actions, packet drop and forwarding to controller actions, reduction of time interval "T", etc.). The SDN support switch 410 can respond to intrusion detection based on the data packet output message by adding new flow entries to the flow table, updating the existing flow table, or changing the time interval "T". The subject that determines these rules and corresponding actions may be an external device (e.g., IDS430, etc.) that has received a request from the SDN controller 420 or the SDN controller 420 itself. This will be referred to later. Fig.9A and Fig. 9B Describe the data-driven intrusion detection method in detail.
[0044] The flow entry includes not only the rule field and action field mentioned above, but also may further include a statistics field ( Figure 4 The statistics field is a field that collects or calculates statistics about data packets and stores them, and may include a counter field. The counter field records the number of matches between the rule field of the flow entry and the incoming data packets, and in some cases, the number may be cumulatively increased or initialized at a preset period. The counter field may include a match counter that is set to count the number of matches with the incoming data packets within a predetermined reference value, or the counter field may also include a byte counter that is set to count the number of bytes per second of the matching data packets.
[0045] The SDN support switch 410 may update the flow table only when receiving a message from the SDN controller 420. When the communication (e.g., communication based on the southbound API) with the SDN controller 420 is disconnected or until the connection with the SDN controller 420 is restored at a cold start (e.g., engine start), the SDN support switch 410 operates in a fail-safe mode. The SDN support switch 410 may control the flow of packets based on the flow table set as a default by the vehicle manufacturer in the fail-safe mode. In this case, the SDN support switch 410 operates as a common switch.
[0046] The SDN controller 420 receives a packet input message or a flow table from the SDN supporting switch 410. As described above, when the SDN controller 420 receives the packet input message, the SDN controller 420 generates a packet output message including a corresponding packet and a forwarding action, and transmits the packet output message to the SDN supporting switch 410. When the SDN controller 420 receives the flow table, the SDN controller 420 transmits the flow table to the IDS 430. Then, the IDS 430 performs intrusion detection, and the SDN controller receives the result (e.g., action) of performing the intrusion detection. The SDN controller 420 transmits the packet output message including the result of performing the intrusion detection to the SDN supporting switch 410.
[0047] The SDN controller 420 may be a dedicated controller for SDN or a general controller combined with an SDN device to operate in an SDN environment, but is not limited thereto. For example, the SDN controller 420 according to the present embodiment may include any controller as long as the controller can manage data packets generated in an IVN or V2X environment and can communicate with the SDN supporting switch 410 or a vehicle equipped with the SDN supporting switch 410.
[0048] The SDN controller 420 may generate a new rule (e.g., a change in the time interval "T", a setting of a rule field of a flow entry, etc.) that can filter out the corresponding intrusion according to the result of performing intrusion detection received from the IDS 430, and may include the new rule in the data packet output message. Such a new rule may be generated by receiving from the IDS 430 or an external device.
[0049] According to another aspect of this embodiment, the SDN controller 420 may use one or more SDN-supporting switches 410 mounted in one or more vehicles to perform maintenance of southbound API-based connections such as OpenFlow, flow table management, or packet statistics collection. The SDN controller 420 may also use one or more IDSs (e.g. Figure 4 430) to perform maintenance of northbound API-based connections such as ad-hoc APIs, RESTful APIs, or other programming interfaces.
[0050] The IDS 430 communicates with the SDN controller 420, receives a flow table from the SDN controller 420, performs intrusion detection, determines an action corresponding to the result of performing the intrusion detection, and transmits the determined action to the SDN controller 420. For example, according to one aspect of the present embodiment, the IDS 430 monitors each field of each flow entry in the flow table, and when the counter increment is abnormal or when an unauthorized source node sends a data packet to a processor requiring authorization, the IDS 430 can determine the situation as an attack, specify a rule to filter out the corresponding flow, or specify the action field of a specific flow entry as a packet drop command. According to another aspect of the present embodiment, the IDS 430 can determine the packet drop command and the forwarding to the controller command as an action. The action enables the SDN support switch 410 to discard the packet type in the IVN and forward the packet type to the SDN controller 420, so that the SDN controller 420 can monitor the packet type. For such monitoring, the SDN controller 420 can receive flow statistics from another device or the SDN support switch 410.
[0051] In the following, refer to Figure 5A , Figure 5B , Fig. 6A , Figure 6B , Fig. 7A and Figure 7B , describe the exemplary topological structures of the data plane, control plane and application plane of the proposed intrusion response system.
[0052] Figure 5A and Figure 5B is a diagram illustrating an exemplary topology of an IVN according to an embodiment of the present disclosure.
[0053] Figure 5A An exemplary topology of an IVN with a hybrid structure is shown. The IVN shown includes various Ethernet devices, infotainment devices, one or more electronic control units (ECUs), and an Ethernet-based LAN including an SDN switch connected to these devices. Typically, high-speed data applications such as advanced driver assistance systems (ADAS) and multimedia can be connected to the SDN switch via an Ethernet-based LAN. In addition, the IVN shown includes a legacy CAN bus (legacy CAN bus) for certain applications that are not suitable for using Ethernet, such as powertrain systems that require message priority. The traditional CAN bus can be connected to an SDN support switch via an ETH-CAN gateway that supports communication between Ethernet and the CAN bus. The SDN switch can communicate with other devices, servers, systems, etc. including a remotely located SDN controller 420 via a V2I communication modem.
[0054] Figure 5B An exemplary topology of an Ethernet-based IVN is shown. The IVN shown includes three switches (i.e., switch 1, switch 2, and base switch 3) and nine ECUs. It should be noted that the number of switches or the number of ECU devices can vary depending on the method of configuring the topology. In order to ensure that all data packets generated by the ECU are transmitted to the final destination node through the switch, each ECU must be connected to the switch separately, and multiple ECUs do not occupy a bus route.
[0055] Switch 1 and Switch 2 are SDN-supported switches with activated SDN functions. The two switches are connected to the SDN controller via a wireless modem that is responsible for communication between the vehicle and the external infrastructure (i.e., V2I communication). When a connection is established with the SDN controller, Switch 1 and Switch 2 process data packets from ECU1 to ECU6 according to the actions received from the SDN controller, and cannot determine the actions of each data packet by themselves. However, when the connection with the SDN controller is disconnected due to a wireless modem failure, Switch 1 and Switch 2 operate like the basic switch 3 to be described later. Therefore, a vehicle based on the intrusion response system 400 according to the present embodiment can maintain normal operation (e.g., fail-safe operation) even in an emergency, and allows each function of the intrusion response system 400 to be selectively applied.
[0056] Based on the command or action received from the SDN controller, switch 1 and switch 2 can block the data packet considered as an attack without forwarding the data packet to other ECUs. In addition, switch 1 or switch 2 can transmit the data packet to the SDN controller for post-analysis. The external intrusion detection system is used to determine whether the data packet corresponds to an intrusion by an attacker.
[0057] The basic switch 3 is not an SDN supporting switch according to the present embodiment, but a conventional switch that performs MAC address learning that has been applied to existing vehicles. When the basic switch 3 knows the destination of the data packet transmitted by the ECU 7 to the ECU 9, the basic switch 3 forwards the data packet to a specific port, and when the basic switch 3 does not know the destination, the basic switch 3 broadcasts the data packet to all ports. The basic switch 3 does not support the data packet information collection function for intrusion detection / response, and does not receive an action designated for controlling the flow of data packets from an external device such as an SDN controller.
[0058] Fig. 6A and Figure 6B1 is a diagram showing a control plane topology structure of a centralized structure and a distributed structure of an intrusion response system according to an embodiment of the present disclosure.
[0059] Generally, an SDN controller disposed on a control plane may transmit data to and receive data from SDN switches within a plurality of vehicles. Fig. 6A A centralized structure is shown, in which a single SDN controller manages all vehicle data packets. The IDS of the present disclosure can achieve the intended purpose with only one SDN controller, but considering latency and load balancing, multiple SDN controllers can also be installed and operated. Figure 6B A distributed structure is shown in which each of several base SDN controllers manages one or more vehicles that are physically or logically close to the SDN controller. For example, the SDN controller can be implemented in an edge cloud server or a fog server at each base. The SDN controller at each base can communicate primarily with the vehicles that are physically or logically close to the SDN controller and transmit the results to the centralized SDN controller. In the centralized architecture, a single SDN controller uses a northbound API to perform communication with the IDS430, while in the distributed architecture, the centralized SDN controller uses a northbound API to perform communication with the IDS430.
[0060] Fig. 7A and Figure 7B is a diagram showing a topological structure of an IDS applicable to an intrusion response system according to an embodiment of the present disclosure.
[0061] Recently proposed deep learning based IDS require more resources such as GPU to obtain accurate detection results. The computing system installed in the vehicle has the minimum performance required for driving, so the computing system is not suitable for operating deep learning based IDS. IDS set outside the vehicle no longer needs to consider the vehicle performance problem when calculating the intrusion detection algorithm. Therefore, the proposed intrusion response system can adopt the operation of such as Fig. 7A The deep learning algorithms shown in the IDS require high computing power for accurate intrusion detection algorithms.
[0062] In the proposed intrusion response system, multiple IDSs can be operated simultaneously. Each IDS is responsible for intrusion detection for a specific protocol (e.g., IDS1 for SSH, IDS2 for AVTP, IDS3 for UDP), and optionally, Figure 7B As shown, an ensemble method may be used that utilizes the detection results of several IDSs operating different detection algorithms.
[0063] Placing the IDS outside the vehicle rather than inside the IVN provides a great deal of flexibility in the operation of the intrusion response system. The IDS can be updated in real time regardless of the location or status of the vehicle being analyzed. For example, the IDS can dynamically add, reconfigure, or remove intrusion detection models or algorithms even when the vehicle to be analyzed is in motion. In addition, if new features are introduced in a single vehicle or new attack patterns are discovered against a single vehicle, the operator (or service provider) can update the detection model with the relevant data.
[0064] Figure 8 is a diagram illustrating a use case scenario supporting the usefulness of an intrusion response system in accordance with the present disclosure.
[0065] (1) Whenever an attack is detected, all vehicles transmit the detected attack information to the IDS through the SDN controller on the cloud server or fog server. In this case, the roadside unit (RSU) can relay the communication between adjacent vehicles and each server. The communication method of RSU can be based on near field communication (NFC), low power Bluetooth (BLE), wireless LAN (WIFI), ultra-wideband (UWB), radio frequency, infrared data communication (IrDA), Zigbee, LTE, or 5G.
[0066] (2) When a vehicle that is one of the vehicles to which the intrusion response system or method of the present disclosure is applied is attacked, the IDS installed in the vehicle (a) transmits attack traffic information or data packets suspected of an attack to a cloud server or a fog server.
[0067] (3) The SDN controller on the cloud server or fog server transmits the attack traffic information or data packets to the IDS, and the IDS analyzes the data. If it is determined that there is an attack, the IDS transmits a warning command to bypass the vehicle (a) to each nearby vehicle through the SDN controller.
[0068] (4) When vehicle-to-vehicle (V2V) communication is activated, the vehicle (a) can share its status with neighboring vehicles.
[0069] (5) When remote control by an external device is allowed, the external device can control the vehicle (a) to decelerate and tow according to the request of the cloud server or fog server.
[0070] Fig.9A and Fig. 9B is a flow chart showing a data-driven intrusion detection and response method according to the present embodiment.
[0071] Fig.9A The process of the SDN supporting switch 410 and the SDN controller 420 performing data driven intrusion detection is shown.
[0072] When a vehicle (eg, CAV) to which the intrusion response system 400 according to the present embodiment is applied starts traveling, a data packet flows from the IVN or V2X environment into the SDN supporting switch 410 ( S900 ).
[0073] The SDN supporting switch 410 determines whether a flow entry having a rule field matching the incoming data packet exists in the mounted flow table ( S902 ).
[0074] When there is a matching flow entry, the SDN support switch 410 determines whether a packet discard command is included in the action field command of the matching flow entry (S904). When there is no packet discard command, the SDN support switch 410 executes the command of the action field without discarding the packet (S906).
[0075] When there is a packet drop command, the SDN support switch 410 drops the corresponding packet and blocks traffic from the corresponding source ( S912 ).
[0076] When there is no flow entry matching the incoming data packet or when the matching flow entry expires and finally there is no matching flow entry, the SDN supporting switch 410 transmits a packet input message including event information such as a port number and a corresponding data packet to the SDN controller 420 disposed outside the vehicle (S910), discards the corresponding data packet, and blocks the corresponding traffic (S912).
[0077] The SDN controller 420 receives the data packet input message ( S920 ), specifies a forwarding action ( S922 ), generates a data packet output message including the forwarding action, and transmits the data packet output message to the SDN supporting switch 410 ( S992 ).
[0078] The SDN controller 420 receives a query requesting a flow table from the IDS 430 ( S940 ), and transmits the query to the SDN supporting switch 410 .
[0079] The SDN supporting switch 410 receives a query requesting a flow table from the SDN controller 420 and transmits the flow table to the SDN controller 420 ( S950 and S952 ).
[0080] Upon receiving the flow table from the SDN supporting switch 410 , the SDN controller 420 transmits the flow table to the IDS 430 ( S960 ).
[0081] The SDN controller 420 receives the result of performing intrusion detection based on the flow table from the IDS 430 ( S990 ), generates a data packet output message including the result of performing intrusion detection, and transmits the data packet output message to the SDN supporting switch 410 ( S992 ).
[0082] The SDN supporting switch 410 receives the packet output message (S996) from the SDN controller 420 and updates the flow table (S998). Such an update may include adding a new flow entry, updating the expiration information of an expired flow entry or each field of a flow entry, or if there is no new content to be updated, keeping the flow table unchanged.
[0083] Fig. 9B The process of IDS 430 performing data-driven intrusion detection is shown.
[0084] The IDS 430 waits for a time interval (“T” in S930 ) for requesting a flow table ( S930 ), and queries the SDN controller 420 ( S932 ).
[0085] When receiving the flow table from the SDN controller 420 ( S970 ), the IDS 430 performs intrusion detection based on each field of each flow entry in the flow table and flow statistics data ( S972 ).
[0086] When the IDS 430 determines that there is an intrusion (S974), the IDS 430 determines to discard the data packets associated with the intrusion (S980). This determination can also be performed by including a discard command in the action field of the flow entry that matches the data packets associated with the intrusion. The IDS 430 transmits the detection result including the discard action to the SDN controller 420 (S982).
[0087] However, if it is determined that there is no intrusion, the IDS 430 does not transmit the detection result (S976).
[0088] although Fig.9A and Fig. 9B In the embodiment of the present invention, it is described that each process is performed sequentially, but this is only to illustrate the technical idea of the embodiment of the present invention. In other words, without departing from the essential features of the embodiment of the present invention, technicians in the field of the embodiment of the present invention can make various modifications and changes for application, such as by changing the Fig.9A and Fig. 9B The present disclosure may be performed in the order described in the description or in parallel to perform one or more of the processes of each process, and therefore, the present disclosure is not limited to Fig.9A and Fig. 9B The timing order.
[0089] Various embodiments of the systems and methods described herein can be implemented by digital electronic circuits, integrated circuits, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include embodiments as one or more computer programs that can be run on a programmable system. A programmable system includes at least one programmable processor (which may be a dedicated processor or a general-purpose processor) that is connected to receive data and instructions from a storage system, at least one input device, and at least one output device, and to transmit data and instructions to a storage system, at least one input device, and at least one output device. A computer program (also referred to as a program, software, software application, or code) includes instructions for a programmable processor and is stored in a "computer-readable medium".
[0090] Computer-readable recording media include all types of recording devices that can store data readable by a computer system. Computer-readable recording media may be non-volatile or non-transitory media such as ROM, CD-ROM, magnetic tape, floppy disk, memory card, hard disk, magneto-optical disk, and storage device, and may further include temporary media such as data transmission media. In addition, computer-readable recording media may be distributed in computer systems connected to a network, and computer-readable codes may be stored and executed in a distributed manner.
[0091] Various embodiments of the systems and techniques described herein can be implemented by a programmable computer. Here, a computer includes a programmable processor, a data storage system (including a volatile memory, a non-volatile memory or other type of storage system, or a combination thereof), and at least one communication interface. For example, a programmable computer can be one of a server, a network device, a set-top box, an embedded device, a computer expansion module, a personal computer, a portable computer, a personal data assistant (PDA), a cloud computing system, and a mobile device.
[0092] The above description is only to describe the technical idea of the present embodiment, and those skilled in the art to which the present embodiment belongs can make various modifications and changes without exceeding the basic features of the present embodiment. Therefore, the present embodiment is intended to describe rather than limit the technical idea of the present embodiment, and the scope of the technical idea of the present embodiment is not limited by these embodiments. The protection scope of the present embodiment shall be interpreted by the attached claims, and the technical ideas within their equivalent scope shall be understood to be included in the scope of rights of the present embodiment.
[0093] Description of Reference Numerals
[0094] 400: Intrusion Response System
[0095] 410: SDN Support Switch
[0096] 420: SDN Controller
[0097] 430: Intrusion Detection System (IDS)
[0098] CROSS-REFERENCE TO RELATED APPLICATIONS
[0099] This application claims the benefit of priority to Korean Patent Application No. 10-2019-0093503, filed on Jul. 31, 2019, and Korean Patent Application No. 10-2020-0095519, filed on Jul. 30, 2020, which are hereby incorporated by reference in their entirety.
Claims
1. An intrusion response system, which is an intrusion response system for an in-vehicle network (IVN) of a vehicle, It is characterized in that The intrusion response system includes: A software defined network support switch, ie, an SDN support switch, is installed in the IVN and controls a flow of an incoming data packet by referring to a flow entry from a flow table; and An SDN controller is disposed outside the vehicle and communicates with the SDN supporting switch, wherein the SDN controller receives flow statistics data from the SDN supporting switch, transmits the flow statistics data to an intrusion detection system, i.e., an IDS, so that the IDS performs intrusion detection, and when an intrusion is detected, receives monitoring results of the intrusion detection from the IDS, and transmits the monitoring results to the SDN supporting switch, The flow entry includes a rule field, an action field, and a statistics field, the statistics field includes a match counter field and a byte counter field, and The SDN supporting switch further compares the incoming data packet with the rule field of each flow entry of the flow table, updates the match counter field when the match between the incoming data packet and the rule field of the flow entry of the flow table is within a preset range or above a preset number, and updates the byte counter field by calculating the number of bytes per second of the matching data packet.
2. The intrusion response system according to claim 1, It is characterized in that The time interval T at which the SDN controller receives the flow statistics data from the SDN supporting switch is set or reset based on all or part of the internal or external environment of the vehicle, the driving environment of the vehicle, the intrusion detection method adopted by the IDS, and the result of performing intrusion detection.
3. The intrusion response system according to claim 1, It is characterized in that The SDN controller communicates with a plurality of SDN supporting switches based on respective interfaces and receives respective flow statistics data from the plurality of SDN supporting switches, and a time interval T at which the SDN controller receives the flow statistics data is individually set for each of the plurality of SDN supporting switches.
4. The intrusion response system according to claim 3, It is characterized in that The flow entry includes one or more fields, and the one or more fields are determined according to an interface adopted by each of the plurality of SDN supporting switches.
5. The intrusion response system according to claim 1, It is characterized in that The SDN supports the switch to update the flow table upon receiving the monitoring result.
6. An intrusion response method, which is a method for detecting and responding to vehicle intrusion using a software defined network support switch (SDN support switch) installed in an in-vehicle network (IVN) and an SDN controller installed outside the vehicle, wherein the SDN support switch controls the packet flow of the incoming data packet by referring to the flow entry from the flow table, It is characterized in that The method comprises: The SDN supporting switch transmits the flow statistics data to the SDN controller; The SDN controller receives the flow statistics data and transmits the flow statistics data to an intrusion detection system (IDS); When an intrusion is detected, the SDN controller receives a monitoring result of the intrusion detection from the IDS; The SDN controller transmits the monitoring result to the SDN supporting switch; and The SDN supporting switch updates the flow table based on the monitoring result, The flow entry includes a rule field, an action field, and a statistics field, the statistics field includes a match counter field and a byte counter field, and The method further comprises: The SDN supporting switch compares the incoming data packet with the rule field of each flow entry of the flow table, updates the match counter field when the match between the incoming data packet and the rule field of the flow entry of the flow table is within a preset range or exceeds a preset number, and updates the byte counter field by calculating the number of bytes per second of the matching data packet.
7. The method according to claim 6, It is characterized in that The time interval T at which the SDN controller receives the flow statistics data from the SDN supporting switch is set or reset based on all or part of the internal or external environment of the vehicle, the driving environment of the vehicle, the intrusion detection method adopted by the IDS, and the result of performing intrusion detection.
8. The method according to claim 6, It is characterized in that Further including: The SDN support switch transmits a packet input message including a packet flowing in from the IVN to the SDN controller; as well as The SDN controller transmits a packet output message including the incoming data packet and the forwarding action to the SDN supporting switch.
9. The method according to claim 8, It is characterized in that When there is no flow entry matching the incoming data packet in the flow table or when the matching flow table expires, transmitting a data packet input message to the SDN controller is performed.
10. The method according to claim 6, It is characterized in that The SDN controller communicates with a plurality of SDN supporting switches based on respective interfaces and receives respective flow statistics data from the plurality of SDN supporting switches, and a time interval T at which the SDN controller receives the flow statistics data is set individually for the plurality of SDN supporting switches.
11. The method according to claim 10, It is characterized in that The flow entry includes one or more fields, and the one or more fields are determined according to an interface adopted by each of the plurality of SDN supporting switches.
