Cybersecurity in Automotive Product Development

How can cybersecurity be integrated into the approach along the V-model in automotive product development? Which steps have to be considered in the specification or verification phases? And how do ISO/SAE 21434 and others envision this in practice? This and more is explained in this video. Don’t move forward in development without knowing the basics of cybersecurity development in automotive product development.

As you have already learned in the previous Automotive Standards and more video courses: With time-bound requirements such as those of UN Regulation No 155, integrating cybersecurity into product development for automotive projects is mandatory. And this doesn’t just apply to OEMs. Regardless of whether you are responsible for product development at the vehicle, system or component level. This video shows how and where cybersecurity needs to be considered.

As a starting point (along the structure of ISO/SAE 21434, based on the Functional Safety approach), the development phase begins at the same time as the concept phase ends. This means that the previously defined cybersecurity concept is the first input for product development.

Watch this video to learn how cybersecurity product development is integrated into the industry-standard V-model. From the breakdown of stakeholder requirements to a statement of work, to implementation and verification at all levels of abstraction.

A deep understanding of all stakeholders helps discover, report, and analyze potential vulnerabilities to ensure a cyber-secure product – in a cost-effective manner, of course.