Welcome to the COVESA Security Group Meeting!

Weekly Meeting: 1st and 3rd Monday of Month at 9am PT / 12pm ET / 6pm CET Starting Jan 19, 2025 (Zoom Link)(Subscribe to Community Calendar to stay up to date)

Slack: https://covesacommunity.slack.com/archives/C06SRJN0DBN

https://groups.google.com/a/covesa.global/g/cybersecurity

• Join the Group (To join the group you must be logged in/authenticated to Google)

  • Sign in to Google

  • Click the Cybersecurity Group link

  • Click Ask to Join

Shared Google Drive

GitHub: TBD

Chairs:

• @Chuck Brokish, Green Hills

• @Rex Struble , VxLabs

Team Charter

Open

Participants: 

Rex Struble

Chuck Brokish

Paul Boyes

Mike Nunnery

Joby Jester

Tim Yerdon

Topic:

• Presentation

• Meeting

Participants: 

Rex Struble

Chuck Brokish

Paul Boyes

John Heldreth

Richard Fernandes

Jennifer Hillsdale

Mike Nunnery

Johan Veenstra

Topics Discussed:

• Summarized the Team Charter/Deliverables: (see the Team Charter above)

  • 1) Build an Automotive Cybersecurity Ecosystem Map (ACE-Map)

  • 2) Lead the cybersecurity aspects of the COVESA VSS/VDM project

• Prelim alignment on ACE-Map

  • Opened the rough working doc’s in the team folder. 1 excel and 1 power-point.

  • Agreed to merge into the 1 Excel format

  • Agreed to add “Categories” to provide structure

  • Agreed to work on how to visualize the content, as a later step.

  • Agreed to leave individuals names off of the ACE-Map; however, we will have team Liaison's to sync with various Committees, WGs, Taskforces, and so forth

Action Items:

• Chuck to combine and consolidate content of ACE-Map into 1 excel

• Team members are asked to add/contribute content into the ACE-Map Excel sheet (see link above)

Participants: 

Mike Nunnery

Chuck Brokish

Rex Struble

Johan Veenstra

Amadou Kane

Joe Gallo

Richard Fernandez

Amadou Kane

Johan

Topics Discussed:

Reviewed the 2 primary topics of the Cybersecurity Group:

ACE Map: Automotive Cybersecurity Ecosystem Map (in excel format for now)

• The standards list that was placed on the website from ASRG has been updated, and include more information.  Also, since more data was added, and in the interest of keeping it non-company specific, company designation was removed. Updated document is here.

• Need to show “Branching of the Map”: showing the different organizations, and the security documents create by each. Those would include:

Security and Privacy of VSS/VDM:

• Creation of new signal definition details in the form of security metadata within COVESA, but adding details regarding security restrictions/requirements for these signals.

• Beyond the signals and how they propagate across the vehicle and can be subscribed to….adding meta data…. augment with further the security parameters… (public, PII, tagged as such, encrypted, restricted)

• Build upon the work done already by the VSS and VDM teams

Action Items:

ACTION: Rex to Reach-out to COVESA members to join our team that have expertise in security metadata: DDS, SOME/IP, Others such as IEEE-1609.2 (V2X). Send invitation through Paul Boyes. Done. Examples of companies would include (but certainly not limited to) RTA (DDS) and Excelfore (SOME-IP)

ACTION: Rex to send invitation through Mike Nunnery to VSS/VDM Team to provide an overview and to discuss collaboration with Cybersecurity Group. Done.

ACTION: Rex to send invitation through Mike Nunnery to invite Jen Dugalinski to attend a future meeting to address this topic. Done.

 Further Notes:

It was noted on the call that there is a group within COVESA created for safety information on the connected vehicle.  That team may want to leverage the work started within the document above, and either create their own tab within the document, or create their own document.

Chuck and Rex will not be at the AMM in Portugal.

o   Mike has requested that they join virtually for part of the meeting, to given a review of recommended activities within the group

o   Mike will check who will be physically present, and determine if it makes sense to have a technical meeting of the security team during the AMM