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

Exploring software security controls

Now that we have previewed some of the commonly used security controls in automotive ECUs, we can switch focus to software security controls. As we will see, many of these controls are built on top of hardware security primitives and aim to provide more sophisticated security mechanisms that hardware alone cannot offer.

Software debug and configuration management

Building on hardware debug access protection, it is equally important to eliminate and/or restrict access to software debug tools. It is common for developers to use a wide range of such tools to aid in troubleshooting and testing the ECU prior to production. A common mistake is to leave these tools in the ECU even after the product is shipped. In MCU-based ECUs, these tools range from proprietary diagnostic protocols that are used in factory mode to trace tools that log extensive error codes to pinpoint the file and line of code where an error occurred, to standard calibration protocols...