2014 IEEE 6th International Symposium on Wireless Vehicular Communications (WiVeC 2014) 2014
DOI: 10.1109/wivec.2014.6953258
|View full text |Cite
|
Sign up to set email alerts
|

Revisiting attacker model for smart vehicles

Abstract: Because of the potential impact on user's life in cooperative automated safety applications, the security of Vehicleto-X communication (V2X) is mandatory. However, the current attacker model used in literature is often too network-oriented, and it is unclear what realistic attacks could be. In this paper, we use the V2X data lifecycle to derive the attack surfaces. From this, we lay the foundations of a revisited attacker model, which details realistic attacks and identify appropriate countermeasures. We demon… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
37
0

Year Published

2018
2018
2024
2024

Publication Types

Select...
7
2

Relationship

1
8

Authors

Journals

citations
Cited by 36 publications
(37 citation statements)
references
References 12 publications
0
37
0
Order By: Relevance
“…By eavesdropping on the communication channel, the adversary tries to collect personal data of EV users in order to build detailed movement profiles of the users (e.g., to rob a user's home in their absence [15,24]). Local Adversary: As a purely remote adversary is often considered to be too weak for comparable settings [1,11,33,41,45], we also consider a Local Adversary with physical access to any unattended EV and CP in public areas. The adversary can physically tamper with the system and extract or modify any data stored on the system, e.g., steal private keys, read out charging logs, or install a malicious firmware image (cf.…”
Section: Security Privacy and Functional Requirementsmentioning
confidence: 99%
“…By eavesdropping on the communication channel, the adversary tries to collect personal data of EV users in order to build detailed movement profiles of the users (e.g., to rob a user's home in their absence [15,24]). Local Adversary: As a purely remote adversary is often considered to be too weak for comparable settings [1,11,33,41,45], we also consider a Local Adversary with physical access to any unattended EV and CP in public areas. The adversary can physically tamper with the system and extract or modify any data stored on the system, e.g., steal private keys, read out charging logs, or install a malicious firmware image (cf.…”
Section: Security Privacy and Functional Requirementsmentioning
confidence: 99%
“…To avoid threats, countermeasures such as detect jamming attacks on cameras via spectral analysis, increase redundancy by adding cameras, etc. may be taken [17].…”
Section: Related Workmentioning
confidence: 99%
“…To date, most studies have focussed on finding network issues. Less attention, however, has been given to security issues that are brought about by data [14]. Vehicles nowadays consume a vast amount of data from a variety of sources (e.g.…”
Section: Motivation and Backgroundmentioning
confidence: 99%
“…data collected by internal and external sensors, and from online databases). Further, within the vehicle, data needs to be captured, processed and stored [14]. All of these Figure 1: Automotive bus systems in a generic architecture steps must happen securely to provide the vehicle with higher assurance levels.…”
Section: Motivation and Backgroundmentioning
confidence: 99%