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

Validation testing

ISO/SAE 21434 defines validation as an activity to be performed at the vehicle level. The objective of this clause is to validate that the cybersecurity goals that were identified during the concept phase have truly been fulfilled now that the item has been integrated within the actual vehicle environment. A component supplier may perform cybersecurity goal validation by applying tests to an environment that emulates the vehicle. While it is not mandatory to do so, it is generally a good practice to validate that the cybersecurity goals that you’ve placed on your product are satisfied before the OEM discovers that they aren’t. Validation is usually carried out through penetration testing by attempting to violate cybersecurity goals through the discovery of unknown vulnerabilities. An OEM who is trying to prioritize ECUs for penetration testing may want all externally facing ECUs, such as telematics or infotainment, to be tested by a third party before...