WP2/17 (Cybersecurity) Chair of ITU-T SG17 ITU-T SG17 updates Koji Nakao WP2/17 (Cybersecurity) Chair of ITU-T SG17 Liaison Officer of Q13/17

Security Areas covered by SG17 Cybersecurity – Cybex Countering spam Information Security Management Fundamental security: PKI, X.509… Identity Management (IdM) Application security Home network, IoT, ITS, smart grid, smartphone, SDN, IPTV, web services, etc. Cloud computing, big data analytics, and telebiometrics. Covered by Q6/17 Question 13 (Security Aspects for ITS communications) was formally approved at the last SG 17 meeting in September, 2017.

After the last CITS ITU-T SG17 hold an interim meeting of Q13/17 at Seoul in late January 2018. This update is based on the results of discussion at the interim meeting.

Proposal of work plan for security aspects of cloud-based EDR (Event Data Recorder) in Q13/17 Topics for discussion are: 1) EDR-related work in SG17; 2) an overview of EDR for automotive; 3) work plan for EDR issues in Q13/17. Discussion: Q13/17 should continuously take into account issues how to implement WTSA16 resolution 94 in the context of Q13/17. Security consideration (including security aspects for the interface between EDR and CDR tool) of EDR for automotive and CDR (Crash Data Retrieval) could be taken into account in the annex of X.itssec-3 (Security requirements for vehicle accessible external devices) or new work item. EDR for automotive environment only records the crash data, thus EDR-related security requirements can be addressed in the existing X.itssec-3.

X.itssec-2, Security Guidelines for V2X Communication Systems The meeting discussed the contribution Doc02, which is proposal of terminologies for X.itssec-2 During a meeting, several comments are raised: Both definitions of non-repudiation with proof of origin and non-repudiation with proof of delivery are required in X.itssec-2 It would be better use a definition of pseudonymity in ITU-T recommendations. If this is not used in the main text, it should be removed. Based on the discussion the meeting agreed to ask editors to publish revised baseline text of X.itssec-2 in for further consideration.

Proposed terminology in X.itssec-2 (examples) old 3.1.2 certificate [b-IEEE WAVE 1609.2]: A digitally signed document binding a public key to an identity and/or a set of permissions new 3.1.2 public-key certificate [defined in X.509 as 3.5.57]: The public key of an entity, together with some other information, rendered unforgeable by digital signature with the private key of the certification authority (CA) that issued it. notes Replace all occurrences of “certificate” with “public-key certificate” in the baseline text 3.1.3. certificate authority(CA) [b-IEEE WAVE 1609.2]: An entity that issues certificates to entities that are entitled to them 3.1.3. certification authority(CA) [defined in X.509 as 3.5.19]: An authority trusted by one or more entities to create and digital sign public-key certificates. Optionally the certification authority may create the subjects' keys. Replace all occurrences of “certificate authority” with “certification authority” in the baseline text 3.1.5 non-repudiation [b-IEEE WAVE 1609.2]: A cryptographic service whereby the origin of a message can be demonstrated to a third party, preventing the sender from denying that they produced the message 3.1.5 non-repudiation [defined in X.800 as 5.2.5.1 “non-repudiation with proof of origin]: The recipient of data is provided with proof of the origin of data. This will protect against any attempt by the sender to falsely deny sending the data or its contents. X.800 makes a distinction between “non-repudiation with proof of origin” and “non- repudiation with proof of delivery”. Within X.itssec-2, the usage seems to be only for “proof of origin”. The editors might want to check for consistency of text between “origin” and “delivery”.

X.itssec-3: Security requirements for vehicle accessible external devices Scope In the context of using external devices accessible to internal sub-systems of the vehicle, this Recommendation aims to identify possible threats and vulnerabilities tampering with and intruding to internal sub-systems of the vehicle and provide security requirements for preventing and mitigating threats and vulnerabilities. This Recommendation can be practically utilized by car manufacture, suppliers, 3rd party external device manufactures and ITS-related industries as a security requirement standard for manufacturing and maintaining external devices accessible to the vehicle. This draft recommendation: describes and identifies security threats when external devices access to internal sub-systems of the vehicle; defines security requirements for vehicle accessible external devices; Security requirements of V2X system are out of scope of this draft Recommendation.

Figure 1. Interfaces and external device Note: TMU: Telematics Management Unit PKE: Passive Keyless Entry

Figure 2. Secure access sub-function

X.itssec-3: Security requirements for vehicle accessible external devices Discussion in the interim meeting of Q13/17: Security requirements for V2X communication should be out of scope in this Recommendation; Security threats based on UNECE WP29 was added. More detailed information on PKE(Passive Keyless Entry) is required and added to this Recommendation to define its security threat and requirements The meeting suggested to improve this baseline text with the above comments and expects to discuss the improved baseline text at the next SG17 meeting

X.itssec-4: Methodologies for intrusion detection system on in-vehicle systems

Scope of this Recommendation

Fig. 5 : IDS framework Clarification of Fig.5 IDS framework is required.

Liaison relationship

ITU-T SG16 (LS from SG16)(1) ITU-T Q27/16 will start to review the documents referred in your LS (SG17-LS47, our SG16-TD142/Gen), especially the new work items. ITU-T Q27/16 intends to refer UNECE WP29 relevant work on various related ITS areas including taxonomy. Regarding your suggestion to have a joint meeting between Q27/16 and Q13/17 the group would be willing to discuss a specific candidate date. For your information, Q27/16 plans to have a Rapporteur group meeting in February or early March 2018 after the CITS meeting (venue: TBD).  This is too late for us to hold a joint meeting with SG16 in Feb/early March. ITU-T Q27/16 looks forward to continuing collaboration with ITU-T SG17, SG20 and CITS.

ITU-T SG16 (LS from SG16)(2) For your information, at our last ITU-T SG16 meeting, Macao, China, 16 – 27 October 2017, Q27/16 proposed for consent two draft Recommendations: ITU-T H.550 (ex. H.VGP-ARCH) "Architecture and functional entities of Vehicle Gateway Platform" and ITU-T H.560 (ex G.V2A) "Communications interface between external applications and a Vehicle Gateway Platform". ITU-T Q27/16 looks forward to continuing collaboration with ITU-T SG17 and CITS and from now on also with ITU-T SG20 on relevant ITS activities.

Activities of WP29 TF-CS/OTA related to SG17 WP29’s Recommendation on Cybersecurity will be finalized after the WP29 Korea meeting in April 2018. We will be able to refer the WP29 Recommendation from X.itssec2 as for “threats”; After receiving the formal result (the report and a new baseline) of WP29 in London/Washington DC, we can start reviewing the result. If Q13/17 has any comments on the text, please share the comments in Q13 through Email list (Q13) and the comments will be demonstrated in the next WP29. We will start considering the new Recommendation for “Threat guideline” based on the WP 29 result in SG17. The new Recommendation should be speedily developed in Q13 so as to synchronize the timing of DETERMINATION of X.itssec2.

Relation to ISO TC204 During the meeting, the results of discussion in the previous ISO/TC204 meeting was reported. As in the minutes of TC204/WG18, we will also support to hold a F2F meeting with ISO/TC204/WG18 to seek for common topics between TC204/WG18 and Q13/17 for further collaboration. The current proposed date was in April 22 (Sunday) at Seoul, but it was decided not to hold the F2F meeting at this time.

The next SG17 meeting is approaching Q13/17 will discuss on: Improvements of X.itssec-2, X.itssec-3, X.itssec-4 and X.itssec-5 Review of the existing Rec. X.1373 (software update) Liaison Relationship with SG16, WP29/TF and SAE… The next SG17 meeting is March 20 – 29 in Geneva.