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

Verification testing

Cybersecurity tests that cover all hardware and software cybersecurity requirements are necessary to determine if the hardware and software design matches the cybersecurity specifications. Traceability between security requirements and security test cases is an essential step to ensure that the security measures are implemented as intended.

Similarly, formal verification techniques can be employed to verify that a specific hardware module can achieve its security objectives. At the unit level, ISO/SAE 21434 does not make specific process requirements, besides standard unit verification. Following a common quality management system will ensure that software units are tested with the right level of coverage before they’re integrated into larger components. A good practice for unit testing is to apply tests that exercise unit inputs, outputs, data, and control flows. The tests should cover error handling, fault injection, and methods for recovery to ensure...