/
Student implementation topic (CVII, Security)

Get Involved

◎ COVESA Community Calendar
◎ COVESA Getting Started
◎ Understanding and Engaging in COVESA
◎ Project Launch Process

Groups and Projects

Groups and Projects continued...

◎ Vehicle Signal Specification (VSS)
◎ AOSP App Framework
◎ Commercial Vehicle and Fleet Group
◎ Generative AI Group
◎ Central Data Service Playground

◎ Vehicle Data Model
◎ Cyberecurity Group
◎ In-Vehicle Payments Group
◎ Connected Safety
◎ All Groups and Projects

Resources

◎ COVESA Events
◎ Industry Events 2025
◎ Antitrust and Open Statement
◎ Member Visibility

Join/Sign Up

◎ Join COVESA
◎ Sign Up for Member Newsletter
◎ Request Wiki Account
◎ Request Access to Slack

Student implementation topic (CVII, Security)

Jun 11, 2021

  • VISSv2 Access control.  Authentication part is not strictly specified, so some design is required. And implement. (Ulf)

  •  Identification of subjects (vehicle, charging station) in system-to-system interaction (Dirk)

    • Does this need to follow specification from charging standards orgs?

    • Parking, or other use cases also exist.

  • When you broker messages between standards, the security model might not be compatible.  E.g. MQTT to other. (Dirk)

  • Implement "full" MQTT access control mechanism (e.g. limited to a set of VSS signals)

  • Code-scanning with tools for uncovering software issues that could be vulnerabilities.



Slide deck with first proposals (v1, draft ideas)



Privacy Policy | Cookie Policy