Scalable service-Oriented Middleware over IP

SOME/IP (Scalable service-Oriented Middleware over IP) is a service-oriented communication protocol for automotive Ethernet, standardized within the AUTOSAR (Automotive Open System Architecture) framework. It was designed to replace traditional signal-based communication like CAN to meet the high-bandwidth and flexible demands of modern systems such as ADAS and infotainment. Core mechanisms include Service Discovery, Remote Procedure Calls (RPC), and Publish/Subscribe, enabling ECUs to exchange complex data dynamically. However, the base SOME/IP standard lacks built-in robust encryption or authentication. Therefore, in a risk management context, it is considered a primary cybersecurity attack surface. According to ISO/SAE 21434 "Road vehicles — Cybersecurity engineering," organizations must conduct a Threat Analysis and Risk Assessment (TARA) on all SOME/IP communications to mitigate risks like spoofing, man-in-the-middle, and Denial-of-Service (DoS) attacks.

In enterprise risk management, applying SOME/IP security follows the ISO/SAE 21434 cybersecurity lifecycle. Step 1: **Threat Analysis and Risk Assessment (TARA)**. Identify all services using SOME/IP as critical assets and analyze threats like spoofing, tampering, and DoS using methodologies such as STRIDE. Step 2: **Implement Security Controls**. Based on TARA results, deploy mitigations. This includes integrating the SecOC (Secure Onboard Communication) module within the AUTOSAR stack to provide authentication and integrity for SOME/IP messages, or using TLS/DTLS to encrypt the communication channel. Step 3: **Monitoring and Intrusion Detection**. Deploy an in-vehicle Intrusion Detection System (IDPS) to continuously monitor SOME/IP traffic, establish a baseline of normal behavior, and alert on anomalies. A major European Tier-1 supplier successfully passed UNECE R155 audits and reduced potential cybersecurity incidents by approximately 35% using this structured approach.

Taiwanese automotive suppliers face three main challenges with SOME/IP. First, a **lack of integrated security expertise**: many firms excel in ECU functions but struggle to integrate SOME/IP with security protocols like SecOC and TLS to meet ISO/SAE 21434 requirements. The solution is to form a cross-functional team and engage external experts to conduct TARA workshops. Second, **high cost of testing tools**: professional toolchains for validating secure SOME/IP are expensive for SMEs. The solution is to start with open-source libraries like `vsomeip` for initial validation and phase in commercial tools. Third, a **difficult mindset shift from CAN**: engineers used to signal-based CAN development find SOME/IP's dynamic, service-oriented architecture challenging. The solution is to provide hands-on training and develop a proof-of-concept (PoC) project to build practical experience.

Winners Consulting specializes in SOME/IP for Taiwan enterprises, delivering compliant management systems within 90 days. Free consultation: https://winners.com.tw/contact