Ensuring Automotive Cybersecurity: The Technical Implications of UN R155 – Part 1

Navigating the New Standards for Cybersecurity Management Systems in the Automotive Industry

The UN regulation No. 155 (UN R155) is a uniform provision concerning the approval of vehicles with regards to cybersecurity and a cybersecurity management system (CSMS) takes effect in July 2024. This regulation requires automotive manufacturers and their suppliers to implement Cybersecurity Management Systems (CSMS) throughout the entire vehicle lifecycle, from design to decommissioning.  

UN R155 establishes specific requirements for vehicle cybersecurity measures, type approval processes, and ongoing security management. We examined the key common components of UN R155 and ISO/SAE 21434, and its impact on OEMs suppliers, and software providers in the automotive industry.  

UN R155 Requirements: Technical Overview

UN R155 mandates the implementation of a comprehensive Cybersecurity Management System (CSMS) focused on vehicle-level cybersecurity. The CSMS is central to ensuring a cybersecure organization within the automotive industry and forms the basis for the Certificate of Compliance for CSMS, subject to auditing and official certification. 

 

Key Components of UN R155: 

Cybersecurity Management System (CSMS): 

The CSMS must be implemented throughout the entire vehicle lifecycle, covering development, production, and post-production phases. It requires a systematic approach to identifying, assessing, and mitigating cybersecurity risks. This includes establishing processes for identifying security requirements, implementing secure defaults, threat detection, incident response, and continuous improvement. The CSMS must be integrated with existing quality management systems and demonstrate traceability of cybersecurity measures throughout the vehicle’s lifecycle. 

Type Approval Process: 

UN R155 introduces a cybersecurity type approval requirement for new vehicle types. This process involves a thorough evaluation of the vehicle’s cybersecurity measures, including hardware and software components. OEMs must provide comprehensive documentation demonstrating how cybersecurity risks have been addressed in the vehicle’s design and implementation. This includes threat modeling, risk assessments, and evidence of security assessments. 

Risk Assessment and Mitigation: 

The regulation mandates a comprehensive risk analysis at the vehicle level. This involves identifying potential attack vectors, assessing their impact and likelihood, and implementing appropriate countermeasures. OEMs must use standardized methodologies for risk assessment, such as TARA (Threat Analysis and Risk Assessment) and maintain up-to-date threat intelligence. Mitigation strategies must be demonstrably effective and proportionate to the identified risks. 

Supply Chain Security: 

UN R155 extends cybersecurity requirements to the entire supply chain. OEMs must establish processes to assess and monitor the cybersecurity practices of their suppliers. This includes conducting security audits, defining security requirements in supplier contracts, and implementing secure communication channels for sharing sensitive information. Suppliers must demonstrate compliance with the OEM’s cybersecurity requirements and provide evidence of their own cybersecurity management systems. 

Incident Response and Monitoring: 

The regulation requires the implementation of robust threat monitoring systems and incident response procedures. This involves deploying intrusion detection systems (IDS) across the vehicle network, establishing a Security Operations Center (SOC) for continuous monitoring, and developing detailed incident response plans. OEMs must have the capability to detect, analyze, and respond to cybersecurity incidents in real-time, including the ability to securely push security updates to affected vehicles. 

Secure Software Updates: 

UN R155 mandates secure processes for all software updates, including over-the-air (OTA) updates. This requires implementing cryptographic measures to ensure the authenticity and integrity of software packages, secure transmission protocols, and robust update mechanisms that can recover from interrupted or failed updates. OEMs must also maintain a secure infrastructure for managing and distributing software updates, including version control and rollback capabilities. 

 

L4B Automotive role in achieving UN R155 Compliance 

Secure Development Lifecycle: 

Cybersecurity design principles form the foundation for the secure development of all embedded products at L4B Automotive. We integrate Secure development lifecycle across products and services, aligned with industry practices such as threat modeling (TARA) at concept phase, secure coding practices (MISRA C & CERT C), software supply chain security, integrating security testing throughout the development process, including static and dynamic code analysis, fuzz testing, penetration testing and vulnerability management. 

Secure Boot and Runtime Integrity: 

L4B Automotive provides secure boot and runtime integrity solutions for automotive systems. Our secure boot implementation includes cryptographic verification at each boot stage, leveraging Trusted Platform Module (TPM 2.0), Hardware Security Modules (HSMs) for secure key storage, key rotation ensuring the integrity of the system throughout its operational lifecycle. 

Secure OTA Updates: 

L4B Automotive’ s provides over-the-air (OTA) update system with MOON services platform. We implement cryptographic package signing and verification, secure transport protocols for update delivery, and mechanisms ensuring update and rollback capabilities. Our solution includes enrolment of Android Automotive and automotive grade Linux based In-vehicle infotainment system (IVI), device management, incremental OTA and A/B partitioning for failsafe, providing a comprehensive and secure OTA update framework for automotive systems. 

Supply Chain Transparency: 

L4B Automotive maintains comprehensive documentation of all software components, including a detailed Software Bill of Materials (SBOM) that identifies third-party components and their versions. We implement continuous vulnerability monitoring processes for these components and provide timely security updates. To support OEM supply chain risk management, we offer evidence of our security practices and relevant industry certifications, ensuring transparency and trust throughout the supply chain.  

New call-to-action