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

Acquisition and integration of supplier components

You’ve started planning project and cybersecurity activities and in the process of doing so, you’ve identified several components that you must source for your project. You have two choices: use an off-the-shelf component that has been developed for a wide range of use cases without consideration of your exact product or work with a third party on developing or adapting an existing component to fit your product needs. In both cases, you want to demonstrate that your integrated product is still compliant with ISO/SAE 21434, regardless of the security maturity level of such components. By integrating a new component, you are essentially exposed to the inherited cybersecurity risks of that component. To address those risks, you have to achieve the following objectives:

  • Identify ISO/SAE 21434 compliance gaps in the component
  • Assess whether the component is capable of fulfilling your allocated cybersecurity requirements...