Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

[2017-2020] : [SG17] : [Q13/17]

[Declared patent(s)]  - [Publication]

Work item: X.eivn-sec (ex X.eivnsec)
Subject/title: Security guidelines for the Ethernet-based in-vehicle networks
Status: [Carried to next study period]
Approval process: TAP
Type of work item: Recommendation
Version: New
Equivalent number: -
Timing: -
Liaison: -
Supporting members: -
Summary: This Recommendation provides security guidelines for the Ethernet-based in-vehicle networks. The current trend in electrical and electronic architecture (E/E architecture) is to integrate the Ethernet with the traditional in-vehicle networks such as CAN, LIN, MOST and FlexRay. In the past, Ethernet was considered only as a connection between the vehicles with the external environments. Standard defined protocols that enable IP-based connections over Ethernet (e.g., DoIP or XCP) have been used to enable communications between the external environment and vehicles. These use cases generally do not need to meet stringent real-time constraints. However, in-vehicle applications using Ethernet communication require characteristics that include high time sensitivity and reliability. Current developments in in-vehicle communication technologies require increased bandwidth in the network. Compared to Ethernet, traditional in-vehicle networks are insufficient to meet the bandwidth requirements of current in-vehicle applications. Therefore, now and in the future, Ethernet-based in-vehicle networks will be a major part of E/E architecture. However, countermeasures known from common computer networks may not be suitable for an automotive application because they were not designed with regard to automotive requirements and capabilities. To address this demand, this Recommendation provides security guidelines for automotive Ethernet technology. This Recommendation includes a reference model of automotive Ethernet and analysis of threat and vulnerability for the Ethernet-based in-vehicle networks. In addition, this Recommendation provides the security requirements and use cases of the Ethernet-based in-vehicle networks too. This Recommendation provides security guidelines for the Ethernet-based in-vehicle networks. Up to now, the usage and specification of automotive Ethernet communication mainly focus on external communication. Standards define protocols as, e.g., DoIP or XCP, that enable an IP-based connection between an external device and the vehicle via Ethernet. Other use cases for external automotive Ethernet communication adapt commonly known and well-established protocols and mechanisms, e.g., HTTP. These use cases usually do not require meeting hard real-time constraints and it is suitable to adapt existing protocols and standards within the corresponding scenarios. In contrary, an in-vehicle application of Ethernet communication may require a high time-sensitive and assured transmission of messages. The current development of in-vehicle communication technologies requires enhanced bandwidth at the network. Legacy automotive network systems such as CAN cannot provide the required bandwidth and efforts compared with the Ethernet network for in-vehicle usage. Thus, it is expected that future electrical and electronic architecture (E/E architectures) will intensively rely on the Ethernet-based in-vehicle networks. However, countermeasures known from common computer networks may not be suitable for an automotive application because they were not designed with regard to automotive requirements and capabilities. To address this demand, this Recommendation provides security guidelines for automotive Ethernet technology. This Recommendation includes a reference model of automotive Ethernet and analysis of threat and vulnerability for the Ethernet-based in-vehicle networks. In addition, this Recommendation provides the security requirements and use cases of the Ethernet-based in-vehicle networks too.
Comment: -
Reference(s):
  Historic references:
Contact(s):
Sang-Woo Lee, Editor
Yousik Lee, Editor
ITU-T A.5 justification(s):
Generate A.5 drat TD
-
[Submit new A.5 justification ]
See guidelines for creating & submitting ITU-T A.5 justifications
First registration in the WP: 2018-09-13 17:46:46
Last update: 2021-09-23 14:18:46