Dr. Panos Papadimitratos

Transcription

1 Dr. Panos Papadimitratos Ecole Polytechnique Fédéral de Lausanne (EPFL)

2 2 Security in Vehicle-to-Vehicle (V2V) and Vehicle-to- Infrastructure (V2I) Communications

3 Security and Privacy Why? 3 o Safety (?) Warning: Accident at (x,y,z)! o Efficiency (?) Warning: Congestion at (x,y,z) RSU TOC!! Traffic Update: Congestion at (x,y,z); Use alternate route!! RSU

4 Security and Privacy Why? 4

5 SEVECOM is a Transversal Project 5 Security Industry Standards esafety SecurIST PRIME C2C-CC Security WG COMeSafety SafeSpot CVIS egovernment SEVECOM Coopers Modinis-IDM GST

6 Security Baseline Architecture 6 o Requirements Authentication, Integrity, Non-repudiation, Access control, Confidentiality Availability Privacy Liability identification

7 7 o Objectives Focus on communication Baseline Privacy Enhancing Technology (PET) Future dynamic deployment of stronger PETs o Baseline solution design approach Standardized cryptographic primitives Easy-to-implement Low overhead Adaptable protection

8 8 o Challenges High rate broadcast communication VANET-only (e.g., safety) and TCP/IP communication Safety Applications General Applications C2C-CC Position Based Routing Wave Short Message Protocol (WSMP) TCP / UDP IPv6 C2C-CC MAC IEEE p MAC and PHY IEEE

9 9 o Basic ideas Unique Identity Credentials and Cryptographic Keys Long-term identity Public key crypto EC-DSA, RSA Certificates Central Processing Module Wireless Communication Module Abstract view of a vehicle

10 10 o Basic ideas (cont d) Pseudonym: Remove all identifying information from certificate Equip vehicles with multiple pseudonyms Alternate among pseudonyms over time (and space) Sign message with the private key corresponding to pseudonym Append current pseudonym to signed message

11 11 o Basic Ideas (cont d) Using Pseudonyms PSNYM_2 PSNYM_3 PSNYM_2 PSNYM_1 PSNYM_3 PSNYM_2 PSNYM_1 PSNYM_1

12 12 o System setup Authority X Long-term Identification Authority A Pseudonym Provider PSNYM_1,, PSNYM_k Vehicle V

13 13 o System setup (cont d) Multiple pseudonym providers Organization 1 Organization 2... Organization n V-PNYM-1 V-PNYM-2 V-PNYM-n... Vehicle V

14 14 o Pseudonym format PSNYM-Provider ID PSNYM Lifetime Public Key PSNYM-Provider Signature o Supplying vehicles with pseudonyms Sufficient in number Periodic refills PSNYM_1 PSNYM_2 PSNYM_3 PSNYM_4 PSNYM_k1 PSNYM_1 PSNYM_2 PSNYM_3 PSNYM_4 PSNYM_k2 PSNYM_1 PSNYM_2 PSNYM_3 PSNYM_4 PSNYM_k3 Time

15 15 o Pseudonym Change Mechanism PSNYM_1,, PSNYM_k PSNYM_1,, PSNYM_k Inputs: Vehicle Location Vehicle Clock Recipient(s) / (Verifier(s)) o One pseudonym per day (?) o One per transaction (?) Pseudonym Selection Process Inputs: Local (vehicle) and Authority Privacy Policies Output: Use PSNYM_i for period [t i,t i+1 ] Vehicle V

16 16 o Other vehicle network identifiers: e.g., IP and MAC addresses o Change addresses along with pseudonyms o Maintain addresses only when necessary, but encapsulate Server S AP B AP A AP C PSNYM_k IP c IP S PSNYM_j IP B IP S PSNYM_i IP A

17 17 o Pseudonym resolution Pseudonymous Communication Transcript Authority O Vehicle V generated the transcript

18 18 o Baseline Solution Well-accepted building blocks (e.g., cryptographic primitives) and concepts (e.g., anonymized certificates/pseudonyms) Adaptation to enhance protection o Investigation of alternative techniques Newer cryptography o Flexible Security Architecture Plug-in stronger privacy enhancing technology

19 Thank you! 19 o Questions? o