Software defined vehicles (SDVs): Managing opportunities, threats and compliance requirements in the automotive space

Why should I attend?

Cars today are arguably as technological as they are mechanical: they are computers on wheels, also termed software-defined vehicles (SDVs).

In a single car today, there are typically over 100 electronic control units (ECUs), made up of hundreds more individual semiconductors. These units enable core functions like efficient braking or steering, as well as value-adds that manufacturers can upsell to customers, such as temperature control or object detection.

Connectivity offers more opportunities for manufacturers in the coming years: Over-the-Air (OTA) updates, customization and personalization, autonomous driving capabilities, integration with the Internet of Things (IoT) and data analytics and monetization.

But manage it badly, and connectivity brings vulnerability. If connected cars are hacked, the impact can quickly escalate from inconvenience to serious safety risks. Criminal and malicious actors know this, and we’re now at a critical junction in the road to better automative security.

Traditionally, ECUs were designed without needing to validate the entities with which they communicate; they simply accepted commands from – and shared information with – any entity on the same wiring. But now, our cars, like our lives, are heavily dependent on data superhighways.

Internet-based attacks on SDVs are rising, highlighting the need for ECUs to authenticate each other and communicate securely, without unwanted interference.

All of the above is reflected by regulations such as UNECE R155 (Cyber security and Cyber security management system) and R156 (Software Update and Software update management system), which will apply to all vehicles produced after July 2024.

Join us to understand the core principles that help secure vehicles’ internal communications, including:

• Safeguarding cryptographic keys and confidential information.
  • Ensure that cryptographic keys and passwords, which could grant unauthorized and privileged access to vehicle computing systems, are kept secure and undisclosed, even as the volume of keys increases exponentially.
  • Enable unique keys and secrets for each vehicle and its subsystems, so that keys specific to an individual vehicle's computing system cannot grant access to other vehicles.
• Restrict firmware modifications and critical data alterations.
  • Limit the capability to change firmware, significantly reducing the risk of malicious software being installed on vehicles by attackers.