Security Control Mechanism for Safety Critical Functions Operating on an Automotive Controller Area Network
Total Page:16
File Type:pdf, Size:1020Kb
Security Control Mechanism for Safety Critical Functions Operating on an Automotive Controller Area Network A Thesis Presented in Partial Fulfillment of the Requirements for the Degree Master of Science in the Graduate School of The Ohio State University By Matt Appel, Graduate Program in Electrical and Computer Engineering The Ohio State University 2020 Master's Examination Committee: Prof. Girogio Rizzoni, Advisor Prof. Ness Shroff Prof. Qadeer Ahmed c Copyright by Matt Appel 2020 Abstract Safety-critical systems in automotive design are facing new challenges associated with advancements in autonomous functionality and connectivity. One of those chal- lenges is security in these systems. There are a multitude of different problems with all of these additional connectivity and sensing units. The focus of this thesis is on the internal communication of Network Control Systems(NCS) of a vehicle. The Controller Area Network (CAN) is the primary network used in safety-critical vehi- cle operation and is lacking inherent security. This thesis presents a security control mechanism for CAN that uses vehicle models to detect and mitigate malicious mes- sages on CAN. The security control mechanism is an Intrusion Detection System (IDS) that uses an unknown input observer implementation to address stealth, re- play, and covert attacks. The goal of this method is to address performance challenges in the authentication of an entire CAN bus. It uses vehicle dynamic behavior to au- thenticate messages rather than using encryption methods to require CAN message authentication when the vehicle is not under attack reducing the burden caused by implementing and continually using secure communication protocols on top of CAN. A case study on a throttle control request of an engine by an Autonomous Vehicle Control Unit (AVCU) test and demonstrate the security control mechanisms. ii Dedicated to my family: mother Teresa Appel, father Andrew Appel, and brother Jason Appel for providing their support, their motivation, and their time to help me achieve my goals. iii Acknowledgments I would like to thank all of my colleagues at The Center for Automotive Research for there great support and all of the opportunities that they have provided. I want to also thank Dr. Qadeer Ahmed and Pradeep Oruganti for all the support over the past couple years. The creation and development CyberSecuirty@CAR Lab has been a challenging and rewarding task and I am thankful o have been apart of that team. I would also like to thank my parents and family for there continued support in getting me to this point. No matter what they have always been there for me and supported my dreams and goals. I will forever be grateful to everyone who has helped me throughout this process, without the proper opportunities, support and guidance none of this would have been possible. iv Vita February 17, 1995 . Born - Mayfield Heights, USA 2018 . .B.S. Electrical and Computer Engineer The Ohio State University 2018-present . .Graduate Research Associate, The Ohio State University: Center for Automotive Research Publications Appel, Matthew Andrew, and Qadeer Ahmed. Intelligent Vehicle Monitoring for Safety and Security. No. 2019-01-0129. SAE Technical Paper, 2019. Oruganti, Pradeep Sharma, Matt Appel, and Qadeer Ahmed. "Hardware-in-loop based Automotive Embedded Systems Cybersecurity Evaluation Testbed." In Pro- ceedings of the ACM Workshop on Automotive Cybersecurity, pp. 41-44. 2019. Fields of Study Major Field: Electrical and Computer Engineering v Table of Contents Page Abstract . ii Dedication . iii Acknowledgments . iv Vita......................................... v List of Tables . ix List of Figures . x 1. Introduction . 1 2. Background . 5 2.1 Introduction to Transportation Security . 5 2.1.1 Cyber Security Domain . 5 2.1.2 Threat Models . 7 2.1.3 Layered Security . 9 2.1.4 Security Assurance . 10 2.2 Automotive Security Review . 12 2.2.1 First Formal Projects out of the EU . 14 2.2.2 Penetration Testing . 15 2.2.3 Automotive Security Standards . 17 2.2.4 Security Recommendations . 19 2.2.5 Automotive Security Layers . 20 2.3 Security Layer Targeted in this Thesis . 22 vi 3. Intra-Vehicle Networks and Controller Area Network . 23 3.1 Vehicle Electrical and Electronic Architecture . 23 3.2 Controller Area Network . 26 3.2.1 CAN Security Challenges . 28 3.3 Related work in CAN Security . 32 3.3.1 CAN secure communication protocols . 33 3.3.2 Intrusion Detection Systems . 33 3.3.3 Cyber Physical System Security, Model-Based Methods . 38 3.4 Thesis Contribution and Gap Analysis . 38 4. Observer based CAN Intrusion Detection and Mitigation Mechanism . 40 4.1 CPS Attack Monitor Preliminaries . 40 4.1.1 CPS Attack Monitor . 41 4.1.2 Observability under Adversarial Attack . 45 4.1.3 Unknown Input Observer . 46 4.2 Attack Model . 48 4.2.1 CAN Attack Scenario Being Addressed . 48 4.2.2 Attacks on Observer-Based Security Mechanisms . 49 4.3 UIO based IDS algorithm for CAN . 51 4.3.1 NCS Graphical Analysis for CAN Tasks, Messages, and Re- sources . 51 4.3.2 Formulation of a Secure CAN Message . 54 4.3.3 Connecting CPS System Model to CAN Network Graph . 56 4.3.4 UIO based Dynamic Monitor for Attacks on CAN Sensor Messages . 58 4.3.5 Security Mechanism for Trust of Message under Sensor Attack 60 4.3.6 Security Mechanism for Control Input Under Attack . 62 4.3.7 Limitations . 62 5. Autonomous Vehicle Engine Throttle Control Case Study . 64 5.1 NCS Graph Analysis for Engine Throttle Control . 64 5.2 Engine . 66 5.2.1 Continuous Time Engine Model . 70 5.2.2 Bilinear Approximation Discretization State Space Model . 72 5.2.3 Zero Order Hold State Space Model . 73 5.2.4 ZOH Engine Model Structure Graph and Attack Set . 74 5.3 UIO Construction for AV Engine Control Security Mechanism . 76 5.4 IDS and Mitigation Security Mechanism . 77 vii 5.4.1 Pressure Sensor Attack Detector and Security Mechanism Design . 78 5.4.2 Throttle Actuator Attack Detector and Security Mechanism Design . 79 6. Implementation, Simulation and Results . 80 6.1 Model in the Loop Testing . 80 6.1.1 UIO test in the Crank Angle Domain . 80 6.1.2 Time Domain and CAN simulation . 85 6.2 HIL Test Bench Design . 89 6.2.1 Real-time Machine Setup . 90 6.2.2 Results on Preliminary HIL setup . 91 7. Conclusion and Future Work . 94 Appendices 96 A. Engine Model . 96 Bibliography . 98 viii List of Tables Table Page 2.1 ASIL table used to determine what the safety level is for an E/E com- ponent [29] . 18 3.1 Table showing the list of challenges associated with the security of CAN [40] . 32 3.2 The different types of In-Vehicle anomaly detectors, referred to by sensor types, with the approach in this thesis potentially classified as both a plausibility, S-7, and/or consistency, S-8, type. [48, Table I] . 36 3.3 The type of anomaly sensor needed can be determined by the design scenario. In our case, a specification approach is not enough; there are multiple messages for which the payload data is available. How- ever, there could be multiple busses and different network types. This approach could be both checking plausibility of the payload data and also checking for consistency on either side of a gateway [48, Table II] 37 4.1 Basic NCS graph notation for tasks, resources, and messages . 52 4.2 Notation for trusted and CAN message sets in NCS . 56 ix List of Figures Figure Page 2.1 Layers and components of the cyber domain [68] . 6 2.2 Model types based on different attributes [69] . 9 2.3 Pyramid that shows the general attack surfaces for ITS technology . 10 2.4 Mobility landscape including various V2X communication surfaces that present security risks to vehicles [11] . 13 2.5 Depiction showing the large number of common attack vectors on a vehicle [20] . 14 2.6 Security mechanisms for a vehicle as a function of the attack progres- sion over time and the type of component being targeted [70] . 20 3.1 A common E/E architecture that would be found on a vehicle today [32] 24 3.2 Communication connections in future AV controllers [32] . 25 3.3 Potential vehicle E/E architecture in future cars showing the high level of attack vectors involved in intra-vehicle communication [32] . 26 3.4 The relationship between CAN and OSI model showing it is only a layer 1/2 protocol which contributes to inherent struggles with security [58] 27 3.5 CAN Packet Description: (a) is a standard packet, (b) is an extended frame packet [28] . 28 3.6 Simplified view of the CAN packet showing the relationship between ArbID, data payload, and messages . 29 x 4.1 Different attack types: (a) is a stealth attack, (b) is a replay attack, (c) is a covert attack [55] . 50 4.2 An example resource graph . 53 4.3 An example process graph . 53 4.4 Example mapping of the process graph in Fig. 4.3 to the resource graph in Fig. 4.2 . 54 5.1 Network setup for the computational units relevant to this case study 65 5.2 Resource graph for AV throttle request . 66 5.3 Process graph for throttle control task . 67 5.4 Mapping of process graph to resource graph focused on targeting the messages used for the observer and vulnerable CAN messages . 68 5.5 Engine Model I/O . 69 5.6 Structural digraph for the zero order hold engine model showing a link size of 1 for a vulnerable state x1, pressure, and its associated output reading y1 ................................