The more autonomous vehicles get, the more safety becomes relevant. And the less control you have in the car, the more cybersecurity that you're going to need. This two-part presentation and subsequent dialogue are designed to give insight into:
o Intelligence to ensure your autonomous product is secure and meets cybersecurity demands.
o What needs to be considered from a supply chain point of view with increasingly complex vehicle architecture.
o Also, find out what OEMs are looking for from supplier to secure their products, and how much they value certain properties.
The current trend for AV and ADAS application to go for a single compute unit instead of many computers or embedded chips presents unique challenges for the industry.
o Understand what the biggest security threats will be.
o Understand how the single compute platform will look for hardware companies.
o Measures to ensure security of a single compute platform.
o How to respond to a security event in an autonomous vehicle.
Software defined vehicles will fundamentally change the role and the work of security engineers in the automotive space. Not only this, but it will also alter the way companies look at their security approaches and the roles and responsibilities between OEMs and suppliers.
This is a significant change that will require huge shifts and changes in the software base and require security teams to prepare for both the opportunities and challenges that SDVs present.
Learn how security approaches will change with and for software-defined vehicles and how you prepare for this industry-transforming shift.
Software Defined Vehicle emergence in the automotive industry is a great opportunity in terms of user experience but also in terms of product value allowing the deployment of new features while reducing and communalizing SW development costs. SDV platforms are built around HPC with HW/SW sharing and a generalized SOA backbone.
The median age of a passenger vehicle today in the US is 12.8 years. And half of the vehicles on the road were designed nearly 20 years ago. To make relevant safety changes to something that was designed 20 years ago or something that stays on the road for >10 years is really a challenge.
If you want to find out what cybersecurity experts are doing or planning to do to address this challenge, take a seat in the audience, and learn:
o The role of long-term maintenance for passenger & commercial vehicles
o How automakers can enable themselves and their supply chains to preserve knowledge, devices, and testing for longer timescales.
o Recommendation on how to manage security vulnerabilities for a timeline of 15 to 30+ years.
o The type of support OEMs will require from Tier-1 and Tier-2 suppliers to safeguard vehicles for full lifetime.
There’s a huge need for talent in the automotive space, and continued skill and availability of skilled people is hugely important. This session is focused entirely on finding out what car companies are looking for from their employees, and what type of training vendors can offer.
What will be discussed:
o What is the profile of individual we need today, and what type of profile will be need in 10 years – do we have a flexible academic program to ensure that?
o Redefining the role of who we need to solve the security challenge of SDVs.
o From an education standpoint, what is the most important certification.
o What resources and support is available for someone who is already in the industry and wants to learn more about transitioning into cybersecurity.
o What type of vendor support and training is available.
The industry is not as mature in the manufacturing space, especially with upticks of ransomware and a lot of people thinking their manufacturing is a closed network, when it might not be. This small group workshop focuses on addressing vulnerabilities associated with our manufacturing environment without halting or impacting manufacture of vehicles/products.
Share ideas and best practices on:
o How to implement security in older machines that are still required to manufacture products in an efficient and acceptable manner.
o How to ensure that the other lines are not infected if there’s a breach of security on the manufacturing side.
o How to secure/streamline signing for cycles from common hacks.
o Where does the responsibility of the supplier end, and the OEM start.
o How to store the right keys and how many keys do you need.