In recent years, software has become a mutual focus for many automakers across the industry and around the globe. Legacy OEMs, automotive brands, and newer start-ups alike are increasingly integrating technologies that put software first in many areas of the vehicle lifecycle – from its design and core user experience, through to the ways it can help maintain and extend the lifecycle.

While this focus continues to shift from hardware to software, and from discrete ECUs to advanced computing systems, new cyber security threats and attack points that exploit their vulnerabilities will be introduced. As such, OEMs and suppliers working with, or producing, a software-defined vehicle must be well equipped to manage new risks while adopting new mitigation technologies.

SBD Automotive’s Securing the Software-Defined Vehicle report takes a detailed, chip-to-cloud look at SDVs. In doing so, it provides a high-level threat model of a typical SDV architecture and identifies the best practices for preventing, detecting, and containing malicious cyber security attacks at each layer of the technology stack. For IT and security teams newly supporting the development of a SDV, the report maps out the key differences between traditional and SDV architectures from a cyber security perspective.