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

Product release

At this point, you’ve performed all the cybersecurity activities defined in your cybersecurity plan. Now, you are ready to make an official product release. But before doing so, you must prove that the work products have been prepared as per the organization’s CSMS and that the objectives of the CSMS have been fully achieved by your product. Gaining release approval requires that you prepare a cybersecurity case and undergo a cybersecurity assessment.

Cybersecurity case

Fast forwarding to the end of the project, the argument for why the product has achieved an adequate level of cybersecurity for its intended use case must be captured within the cybersecurity case. Typically, the case relies on two types of arguments: a process argument and a technical argument. The process argument demonstrates that the product has followed the cybersecurity engineering process and presents any deviations, along with arguments for why those deviation-based risks...

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}