Cybersecurity in automotive joint ventures: securely driving the SDV future together
Collaborations in the automotive industry are accelerating the development of the software-defined vehicle (SDV), but they also create new cybersecurity risks. When partners' differing technologies and processes converge, it may result in complex architectures and new attack surfaces. Therefore, an integrated security approach is essential from the outset. In AUTOMOBIL ELEKTRONIK magazine, ETAS experts explain how to ensure cybersecurity in such joint ventures from the ground up.
In their technical article, 'To prevent the joint venture from becoming a cyber risk,' Dr. Christoph Stadtmüller and Lena Steden explain how security must be embedded in collaboratively developed E/E architectures right from the start.
A holistic approach to collaboration
To fully leverage the benefits of a joint venture without compromising vehicle security, cybersecurity must be an integral part of the collaboration. This requires early harmonization at both the organizational and technical levels to create a comprehensive and robust security concept.
- Organizational framework: Cybersecurity must be embedded in the partnership's governance from the outset, for example through a joint committee with clear decision-making authority. It is crucial to define precise responsibilities and interfaces, which can then be formally documented in a 'Cybersecurity Interface Agreement' (CIA) as suggested by ISO/SAE 21434. Furthermore, contractually agreed post-SOP obligations, such as vulnerability monitoring, incident response, and security updates, are essential to ensure cybersecurity over the entire vehicle lifecycle.
- Secure onboard network communication: Secure communication between Electronic Control Units (ECUs) is critical for maintaining a robust cybersecurity framework in the automotive industry. While standards such as SecOC for in-vehicle networks and TLS for Ethernet-based communication provide essential mechanisms, their implementation requires alignment between partners. Key aspects such as parameterization and key management must be harmonized to ensure interoperability.
- Secure software updates: Secure software updates are a key requirement for software-defined vehicles. Authentication is typically based on asymmetric cryptography using certificates and Public-Key Infrastructure (PKI). Depending on the partnership setup, two main scenarios arise: updating joint ECUs via separate backends or merging partner-specific ECUs into a common architecture. To ensure consistent and secure update processes, the technical adaptation must occur either in the backend, which provides compatible signatures, or within the ECUs themselves, which must then support various partner keys or algorithms.
- Key management and intrusion detection systems: A harmonized Key Management System (KMS) is essential for secure key distribution in partner-developed E/E architectures, as no overarching industry standard exists. Since merging two different proprietary KMS solutions is often not feasible, partners must either select one of their existing systems or define a new joint solution. Similarly, intrusion detection systems must be aligned in terms of event definitions and data formats to ensure consistent security event reporting and enable effective backend analysis.
Added value for SDV security
Developing SDVs in partnership requires a new way of thinking: Cybersecurity cannot be an afterthought, but must serve as a strategic foundation for the collaboration. An integrated approach that combines organizational governance with technical harmonization is the key to success. By pooling their experience and expertise, the partners involved can even elevate vehicle security to a higher level. In this way, the joint development creates genuine added value for the comprehensive cybersecurity of tomorrow's software-defined vehicles.
Contact us
Do you have any questions? Feel free to send us a message. We will be more than happy to help. Contact us today!