Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Automotive Cybersecurity Engineering Handbook

You're reading from   Automotive Cybersecurity Engineering Handbook The automotive engineer's roadmap to cyber-resilient vehicles

Arrow left icon
Product type Paperback
Published in Oct 2023
Publisher Packt
ISBN-13 9781801076531
Length 392 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Dr. Ahmad MK Nasser Dr. Ahmad MK Nasser
Author Profile Icon Dr. Ahmad MK Nasser
Dr. Ahmad MK Nasser
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1:Understanding the Cybersecurity Relevance of the Vehicle Electrical Architecture
2. Chapter 1: Introducing the Vehicle Electrical/Electronic Architecture FREE CHAPTER 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

Exploring policy controls

Just as with the vehicle-level analysis, policy controls must be applied at the ECU level to prohibit design decisions that unreasonably increase the attack surface and significantly alter the threat model of an ECU. Examples of attack surface reduction policy controls are the requirement that all debug interfaces are either locked or disabled, the removal of code profilers, and the elimination of security log traces from production intent builds. The removal of such tools and abilities lowers the attack feasibility related to reconnaissance and the discovery of ECU weaknesses and has a significant return on investment (ROI) in terms of risk elimination. An organization can also enforce policy controls to prohibit certain design choices that would alter fundamental assumptions made during threat modeling. For example, assume the threat model considers that all external network connectivity is filtered through a central gateway. For improved customer experience...

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 $19.99/month. Cancel anytime
Banner background image