How to help secure automotive software has been saved
Perspectives
How to help secure automotive software
As published in Risk & Compliance Journal for The Wall Street Journal
Vehicles are becoming more connected and reliant on software and data, but the road ahead still may be bumpy. Download the latest article to learn more.
With the continued growth of autonomous, semi-autonomous, electric, and connected vehicle segments, software is even more central to automotive development. The increasing amount of software installed in vehicles can lead to more safety and security considerations during the development process.
The new security standards introduced by SAE, requires OEMs to adopt a shift-left strategy to identify software security and safety vulnerabilities as early as possible. ISO/SAE 21434 standard specifies engineering requirements for cybersecurity risk management regarding concept, product development, production, operation, maintenance and decommissioning of electrical and electronic (E/E) systems in road vehicles, including their components and interfaces.
Deloitte’s Secure Product Development framework can enable OEMs and Tier-1s perform a thorough assessment of their existing product/software development processes and provides them with a framework to further integrate cybersecurity requirements and milestones into their product/software lifecycle.
Authors and contributors
Rob Massey |
Tim Davis |
Wendy Henry |
Amy Park |
Mike Marzelli |
Seth Connors |
Conor O’Brien |
Jun Ryu |
Caitlin Hahn |
Grant Anderson |
Nate Tasso |
Recommendations
Cyber Risk Services | Deloitte US
Deloitte Cyber & Strategic Risk offers a unified approach to help you tackle obstacles, build new capabilities, and move forward fast. Leverage our breadth and depth to transform your organization, wherever you are on your journey.