Key points are not available for this paper at this time.
Significant developments have taken place over the past few years in the area of vehicular communication systems. Now, it is well understood in the community that security and protection of private user information are a prerequisite for the deployment of the technology. This is so precisely because the benefits of VC systems, with the mission to enhance transportation safety and efficiency, are at stake. Without the integration of strong and practical security and privacy enhancing mechanisms, VC systems can be disrupted or disabled, even by relatively unsophisticated attackers. We address this problem within the SeVeCom project, having developed a security architecture that provides a comprehensive and practical solution. We present our results in a set of two articles in this issue. In this first one, we analyze threats and types of adversaries, identify security and privacy requirements, and present a spectrum of mechanisms to secure VC systems. We provide a solution that can be quickly adopted and deployed. In the second article we present our progress toward the implementation of our architecture and results on the performance of the secure VC system, along with a discussion of upcoming research challenges and our related current results.
Building similarity graph...
Analyzing shared references across papers
Loading...
Panos Papadimitratos
KTH Royal Institute of Technology
Levente Buttyán
Budapest University of Technology and Economics
Tamás Holczer
Budapest University of Technology and Economics
IEEE Communications Magazine
École Polytechnique Fédérale de Lausanne
Swiss Epilepsy Center
Andrássy University Budapest
Building similarity graph...
Analyzing shared references across papers
Loading...
Papadimitratos et al. (Sat,) studied this question.
synapsesocial.com/papers/69d7648ef182769aa8b8af7d — DOI: https://doi.org/10.1109/mcom.2008.4689252
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: