LEss Injuries by making cars SecURE Stefan N├╝rnberger

News

Topic references

Written: 08.11.2019 11:06 Written By: Daniel Frassinelli

Dear students,

we post the list of topic and references. Take a look at all documents to see what you think is fitting for you. The deadline to choose the topic will be Wednesday. Soon, we will also upload:

  • A latex template, with some more details on what you need to write.
  • A doodle to book the exam date.
  • A doodle to vote your preferred topic.

In the meantime, a brief overview of what will be expected from you: For your chosen topic, you should analyse the related works we provide (which are a simple starting point) and find more yourself. The point of this work is to make a presentation and summary where you discuss such things:

 

  • Summarise the topic and related works, and describe what is the current state of the art in the field (both in terms of technology and usage by OEMs).
  • Perform an analysis of how such technologies could evolve in the future (i.e., how will automotive evolve in that aspect).
  • Discuss how this will affect the customers (privacy? security? added costs? etc.), with a particular focus on the persona(s) you define. This can be done by providing a few concrete use-cases.
  • Based on your use-cases, discuss the possible solution(s). Please, consider everything, from the life-time of the vehicle to the fact the OEMs need to recall possibly hundreds of thousands of cars if the solution doesn't work and cannot be remotely fixed! How would it affect your persona(s)? Would your solution allow for new tech to be implemented on top? Is it backwards-compatible? Forward-compatible? Etc.

In short, the idea of this seminar is to put you in the perspective of an OEM. This means you are not allowed to solve somethings by saying 'we encrypt everything', 'we do not sell data', and so on so forth. You must consider the implication of your solution, the complexity of maintaining it over time, how it will adapt for future models, will customers care about it, etc. We hope this will give you insights into how complex is to innovate and propose solutions for the automotive industry. Also, you will probably notice how such industry is anything but agile and that is decades behind the current state-of-the-art technologies.

 

Shared references

These are reads that everyone should look at. Also, feel free to read documents and articles from the other subtopics, as they might still be correlated to yours.

 

Topic 1. Data collection and analysis in vehicles

In this topic, you will analyse technologies that actively log and possibly identify a driver (e.g., log when and how you drive), identification (e.g., can the car know when you are driving and feeling unwell? can this be applied to court?), advertisements (how long before we see custom advertisements on the head unit?), etc.

 

Topic 2. Self-driving & sensor fusion

This topic is concerned more with the future of mobility. Will cars be self-driving, if yes how? How do we judge who is at fault if it is a probabilistic algorithm making a decision? How do you prove it to a judge? What could go wrong? Can we attack sensors? Can we prevent attacks? If yes, how? At which cost?

 

Topic 3. Automotive Security

In this topic, you will analyse the current state of the art in automotive security, especially in-vehicle networks. As of currently, there is no security, but in the future? Components can be replaced, updated, and possibly connected to the Internet. How do we assure that an attacker doesn't gain remote control of your vehicle? How do we protect the communication between ECUs (remember, a 50ms delay on packets telling the car to brake is unacceptable). Similarly, ECUs are cost-driven embedded controllers, with limited RAM and CPU. How will this evolve? Is the current architecture and design sufficient?

 

 

Topic 4. Telematic Control Unit, eCall, and connected dongles

In this topic, you will analyse TCUs and dongles (which are becoming increasingly used). They can be used for several things: from safety to data collection, remote control and debugging, update over the air etc. These devices will possibly revolutionise the automotive industry, as they will allow OEMs to (right now is not) securely push updates to 1) fix bugs, and 2) add features (e.g., TESLA). But many things could go wrong, especially as most of them have little to no security. How can we solve this?

 

Topic 5. Vehicle to infrastructure (V2I) and vehicle to vehicle (V2V) communication

It is definitely true that in the future of mobility, vehicles will be connected to everything. Assuming the two main technologies will be vehicle to vehicle (V2V) and vehicle to infrastructure (V2I), how this communication will happen? Via WLAN or mobile networks? With or without secure communication? What is the state of the art technologies? How all the OEMs manage or (plan) to implement them? Are there any standards? Can this be done security? What could go wrong? How can this affect security & privacy?

 

Topic 6. Vehicle testing, attestation & dynamic homologation

As of currently, cars are black-boxes which cannot be tested if not by the makers. This makes it very difficult for a third-party to verify claims. Also, it is currently impossible to re-configure them, as they would lose their homologation. The question is, how will this process evolve? Can it be made more open and streamlined? Can the community be involved in developing a road-legal vehicle? Can and how you prove to a third party that a vehicle is running the software you signed? How do you test your vehicle?



Privacy Policy | Legal Notice
If you encounter technical problems, please contact the administrators