Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Automotive Cybersecurity Engineering Handbook

You're reading from  Automotive Cybersecurity Engineering Handbook

Product type Book
Published in Oct 2023
Publisher Packt
ISBN-13 9781801076531
Pages 392 pages
Edition 1st Edition
Languages
Author (1):
Dr. Ahmad MK Nasser Dr. Ahmad MK Nasser
Profile icon Dr. Ahmad MK Nasser

Table of Contents (15) Chapters

Preface 1. Part 1:Understanding the Cybersecurity Relevance of the Vehicle Electrical Architecture
2. Chapter 1: Introducing the Vehicle Electrical/Electronic Architecture 3. Chapter 2: Cybersecurity Basics for Automotive Use Cases 4. Chapter 3: Threat Landscape against Vehicle Components 5. Part 2: Understanding the Secure Engineering Development Process
6. Chapter 4: Exploring the Landscape of Automotive Cybersecurity Standards 7. Chapter 5: Taking a Deep Dive into ISO/SAE21434 8. Chapter 6: Interactions Between Functional Safety and Cybersecurity 9. Part 3: Executing the Process to Engineer a Secure Automotive Product
10. Chapter 7: A Practical Threat Modeling Approach for Automotive Systems 11. Chapter 8: Vehicle-Level Security Controls 12. Chapter 9: ECU-Level Security Controls 13. Index 14. Other Books You May Enjoy

Secondary standards

While the primary standards may provide a holistic framework for engineering secure automotive products, they rely on secondary and supporting standards to address specific technical areas of the engineering life cycle. Awareness of such standards is necessary to judge whether they apply to your organization or product offering.

IATF 16949:2016

Developing automotive products within the framework of a quality management system (QMS) serves as a prerequisite to achieving product security. ISO/SAE 21434 makes adherence to a QMS a requirement, which is reasonable considering the difficulty of arguing that a product is secure while not being able to demonstrate its quality [9]. For example, software developed outside a QMS is expected to contain more bugs due to the lack of formal quality checks, such as code reviews and software tests. A percentage of those software bugs are likely exploitable by an attacker. Without the help of a QMS, we are unable to manage...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime}