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

End of life

The product has reached its end of life. Now, you can rest assured that no one can attack your system, right? No – even when you are ready to bury that product in its final resting place, you must take care of active assets that may be “exhumed” by a determined attacker who wishes to launch attacks against the other still alive and functioning products. For example, intellectual property, or user private data, may still be accessible in a vehicle that is slated for the junkyard. It is common for hobbyists to buy such parts on eBay, so products must have procedures for transitioning such systems into a secure state in which the assets cannot be exposed. This can be achieved by invoking routines that randomize secret keys or wipe user secrets. End-of-life preparation must also include change of ownership events. An OEM must provide procedures for the removal of personally identifiable information (PII) when a change of ownership occurs:

...