Book Image

Automotive Cybersecurity Engineering Handbook

By : Dr. Ahmad MK Nasser
5 (1)
Book Image

Automotive Cybersecurity Engineering Handbook

5 (1)
By: Dr. Ahmad MK Nasser

Overview of this book

Replete with exciting challenges, automotive cybersecurity is an emerging domain, and cybersecurity is a foundational enabler for current and future connected vehicle features. This book addresses the severe talent shortage faced by the industry in meeting the demand for building cyber-resilient systems by consolidating practical topics on securing automotive systems to help automotive engineers gain a competitive edge. The book begins by exploring present and future automotive vehicle architectures, along with relevant threats and the skills essential to addressing them. You’ll then explore cybersecurity engineering methods, focusing on compliance with existing automotive standards while making the process advantageous. The chapters are designed in a way to help you with both the theory and practice of building secure systems while considering the cost, time, and resource limitations of automotive engineering. The concluding chapters take a practical approach to threat modeling automotive systems and teach you how to implement security controls across different vehicle architecture layers. By the end of this book, you'll have learned effective methods of handling cybersecurity risks in any automotive product, from single libraries to entire vehicle architectures.
Table of Contents (15 chapters)
1
Part 1:Understanding the Cybersecurity Relevance of the Vehicle Electrical Architecture
5
Part 2: Understanding the Secure Engineering Development Process
9
Part 3: Executing the Process to Engineer a Secure Automotive Product

Threats against the E/E topology

In Chapter 1, we explored the various E/E architecture types from the highly distributed, to the domain centralized, and finally, the zone architecture. In this section, we will highlight the threats against each type of architectural layout.

Highly distributed E/E architecture

A typical weakness of such architecture is that security-critical ECUs may be reached from multiple attack surfaces, without the possibility of cleanly separating the domains. One of our security principles in Chapter 2 was domain separation, which required the physical and logical separation of the domains of various levels of security needs.

An example of a weak architecture is that of the famous Jeep hack in which the infotainment ECU was on the same network segment as the brake ECU [28].

Figure 3.11 – 2014 Jeep Cherokee architecture (source is [28])

Figure 3.11 – 2014 Jeep Cherokee architecture (source is [28])

This enabled an attacker who managed to compromise the infotainment ECU to start...