Reader small image

You're reading from  Automotive Cybersecurity Engineering Handbook

Product typeBook
Published inOct 2023
PublisherPackt
ISBN-139781801076531
Edition1st Edition
Right arrow
Author (1)
Dr. Ahmad MK Nasser
Dr. Ahmad MK Nasser
author image
Dr. Ahmad MK Nasser

Dr. Ahmad MK Nasser is an automotive cybersecurity architect with a long experience in securing safety-critical systems. He started his career as a software engineer, building automotive network drivers, diagnostics protocols, and flash programming solutions. This naturally led him into the field of automotive cybersecurity, where he designed secure firmware solutions for various microcontrollers and SoCs, defined secure hardware and software architectures of embedded systems, and performed threat analysis of numerous vehicle architectures, ECUs, and smart sensors. Ahmad holds a B.S. and an M.S. in electrical and computer engineering from Wayne State University, as well as a Ph.D. in computer science from the University of Michigan in Dearborn. He is currently a principal security architect for NVIDIA's autonomous driving software platform.
Read more about Dr. Ahmad MK Nasser

Right arrow

Defining the appropriate TARA scope

ISO/SAE 21434 mandates that the TARA is performed during the concept phase while considering all product life cycles (production, operation, maintenance, and decommissioning). A common pitfall is to focus purely on the operational phase because that is the phase where vehicle safety is directly exposed to cybersecurity threats. The result is an inadequate cybersecurity concept that misses security goals covering how the vehicle is produced, maintained, and taken out of service. That is why it is important to involve all engineering teams across all the product life cycles and assign clear responsibilities when planning out the TARA(s). When there is resistance to expanding the scope of the TARA to cover these life cycle stages, development teams must capture all the assumptions on risks of the other life cycles to ensure that at least the system integrator is aware of those risks. For example, if the manufacturing phase is not adequately analyzed...

lock icon
The rest of the page is locked
Previous PageNext Page
You have been reading a chapter from
Automotive Cybersecurity Engineering Handbook
Published in: Oct 2023Publisher: PacktISBN-13: 9781801076531

Author (1)

author image
Dr. Ahmad MK Nasser

Dr. Ahmad MK Nasser is an automotive cybersecurity architect with a long experience in securing safety-critical systems. He started his career as a software engineer, building automotive network drivers, diagnostics protocols, and flash programming solutions. This naturally led him into the field of automotive cybersecurity, where he designed secure firmware solutions for various microcontrollers and SoCs, defined secure hardware and software architectures of embedded systems, and performed threat analysis of numerous vehicle architectures, ECUs, and smart sensors. Ahmad holds a B.S. and an M.S. in electrical and computer engineering from Wayne State University, as well as a Ph.D. in computer science from the University of Michigan in Dearborn. He is currently a principal security architect for NVIDIA's autonomous driving software platform.
Read more about Dr. Ahmad MK Nasser