Project Overview
Vehicle CAN Bus networks for heavy-duty trucks, buses, and off-road
machinery are currently standardized through SAE J1939 which is an
open, non-secured network. As Original Equipment Manufacturers (OEM)
change their business models to be option/subscription based,
raising the value of information on the vehicle network, and as more
aftermarket manufacturers provide systems that require plugging
untrusted devices into vehicle networks (for data gathering, system
monitoring, and other value-add activities) it is in the interest of
all parties (owner/operators, OEMs, and aftermarket manufacturers)
that the data flowing through the vehicle network is authentic and
has not been intentionally or unintentionally modified (i.e.,
messages have integrity), particularly as it relates to
command-and-control messages.
This project will implement protocols used for onboard key
management and secure message exchange defined in SAE J1939-91C (a
draft specification for securing in-vehicle communications using CAN
Flexible Data (FD) network technology). This project simplifies one
important aspect of vehicle network security: it assumes a free-form
approach to CAN FD frames, as opposed to being constrained to
J1939-22. The project team will be responsible for designing and
implementing the vehicle security interfaces and will achieve a full
hardware demonstration.
Expected Deliverables
1. Demonstrate technical ability to work with CAN FD segments.
2. Demonstrate implementation of key management protocols specified
in J1939-91C (which allows for on-vehicle generation and sharing of
session keys without requiring OEMs to inject secrets)
3. Demonstrate use of generated key to secure messages using CAN FD
frames.
Team Members
Aayush Chanda
Advisor Liaison
Cyber Security Engineering
Advisor Liaison, primarily in charge of communicating
with our advisor Dr. Joe Zambreno
Making sure all important information and necessary
updates are relayed back to Dr. Zambreno
Comparing availabilities and setting appropriate dates
and times for team meetings with Dr. Zambreno
Spokesperson for the team's questions and concerns for
Dr. Zambreno
Baganesra Bhaskaran
Gitlab Administrator
Cyber Security Engineering
Gitlab Administrator, in charge of git repositories and
version control.
Prepare and update the repositaries and drives to keep
the documents and code files up-to-date
Compile and organize team documents time-to-time
Chau Wei Lim
Strategist
Cyber Security Engineering
Strategist, in charge of discussing, developing, and
implementing strategies to satisfy client's needs.
Gather team ideas and make sure they meet the project's
requirements.
Find out a common time for each meeting with the advisor
and the client.
Michael Roling
Documentor
Electrical Engineering
Documentor; creates a library of files to faciliate
understanding for the project's material.
J1939 protocols will be the primary means to better
understanding CAN communications.
Compiling a series of research documents on key
management will encourage innovative ways to confirm
handshakes between controllers on CAN.
Alex Freiberg
Client LiasonComputer Engineering
Client Liaison; manages all communication between the team
and the client to establish meeting times and uphold client expectations.
All client expectations, on both the technical and communication fronts, must be clearly
communicated to the rest of the team to ensure project success.
Works to analyze and implement the team's design by ensuring that all client needs
and expectations are met.
Brian Goode
Team Organizer
Cyber Security Engineering
Team Organizer; Manage project documentation and
ensure code, design documents, and other written
material is written consistently.
Reserach security/ cryptography concepts and
standards for CAN communication and key management
and transportation.
Work with team members on design generation, design
decisions, and design documents.
Weekly Reports - F22
Report 1 - 09/30/2022Report 2 - 10/07/2022
Report 3 - 10/14/2022
Report 4 - 10/21/2022
Report 5 - 10/28/2022
Report 6 - 11/04/2022
Report 7 - 11/11/2022
Report 8 - 11/18/2022
Report 9 - 11/28/2022
Bi-Weekly Reports - SP23
Report 1 - 02/18/2023Report 2 - 03/02/2023
Report 3 - 03/24/2023
Report 4 - 04/07/2023
Report 5 - 04/20/2023
Final Report - SP23
Final Report - 04/29/2023Final Presentation Documents - SP23
Final Poster - 04/29/2023Final Slide Deck - 04/29/2023
Final Demo Video - 04/29/2023
Design Documents
Design Doc 1 - 09/30/2022Design Doc 2 - 10/07/2022
Design Doc 3 - 10/14/2022
Design Doc 4 - 10/21/2022
Design Doc 5 - 11/11/2022
Final Design Document - 12/2/2022
Project Repository
Linked Here  -Must connect on campus or through campus VPN