VeSPA: Vehicular Security and Privacy-preserving architecture N. - - PowerPoint PPT Presentation

▶
vespa vehicular security and privacy preserving
SMART_READER_LITE
LIVE PREVIEW

VeSPA: Vehicular Security and Privacy-preserving architecture N. - - PowerPoint PPT Presentation

Jan 14, 2023 424 likes •644 views

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work VeSPA: Vehicular Security and Privacy-preserving architecture N. Alexiou M. Lagan` a S. Gisdakis M. Khodaei P. Papadimitratos School of Electrical Engineering,

slide-1
SLIDE 1

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

VeSPA: Vehicular Security and Privacy-preserving architecture

  • N. Alexiou
  • M. Lagan`

a

  • S. Gisdakis
  • M. Khodaei
  • P. Papadimitratos

School of Electrical Engineering, KTH, Sweden surname@kth.se HotWiSec13’

April 19, 2013

1 / 20

slide-2
SLIDE 2

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Table of Contents

Introduction Status and current Directions for VC Future Challenges for VC List of Future Challenges VeSPA Architecture & Operation Analysis of VeSPA Efficiency & Privacy Improvements Future Work Ongoing Work and Future Directions

2 / 20

slide-3
SLIDE 3

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Vehicular Communications

  • Vehicular Communications (VC)
  • Vehicles propagate information

for Safe-Driving

  • Location, Velocity, angle
  • Hazardous warnings
  • Emergency break etc.
  • Cooperative awareness through

beaconed status messages and event-triggered warnings

  • ..Security in VC?
  • Assure legitimate vehicles

propagate information

  • Secure integrity of information

Image source: C2C-CC 3 / 20

slide-4
SLIDE 4

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Digital Signatures for VC

  • Vehicles hold Private-Public

Key pair

  • Unique pair to each vehicle
  • Digital Signature of the

messages

  • Authentication
  • Integrity
  • Non-repudiation
  • Vehicular Public Key

Infrastructure (VPKI)

  • To assign credentials
  • Propagate trust

Image Source: Secure Vehicular Communication Systems: Design and Architecture, P. Papadimitratos et al 4 / 20

slide-5
SLIDE 5

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Privacy in VC

  • Packets signed using same

credentials can be trivially linked

  • Solution:
  • Offer multiple short-lived

credentials (Pseudonyms (PS))

  • Pseudonyms valid for

unique time periods

  • Sign packets with valid

pseudonyms

  • Cryptographic operations in

a Hardware Security Module

  • Extend the VPKI to support

Pseudonyms

5 / 20

slide-6
SLIDE 6

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Current Status: Overview

  • Credential management in Vehicular Communications (VC)
  • Long-term Credentials for accountability and Authentication
  • Short-lived Pseudonyms for anonymity and Location Privacy
  • A VPKI to support credential management
  • VPKI Architecture:
  • LTCA: Issuer of Long-term Credentials
  • PCA: Issuer of Pseudonymous Credentials
  • RA: Resolution Authority
  • VPKI Protocols:
  • Pseudonym provision: Refresh pool of pseudonyms
  • Pseudonym Resolution: De-anonymize misbehaving vehicles
  • Car accident, violation of traffic regulation, police request
  • Pseudonym revocation: Revoke the misbehaving pseudonyms
  • Main Suspects: SEVECOM, C2C-CC, PRESERVE, 1609

family of standards WAVE, ETSI

6 / 20

slide-7
SLIDE 7

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Table of Contents

Introduction Status and current Directions for VC Future Challenges for VC List of Future Challenges VeSPA Architecture & Operation Analysis of VeSPA Efficiency & Privacy Improvements Future Work Ongoing Work and Future Directions

7 / 20

slide-8
SLIDE 8

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Future Challenges for VC

  • Implement an efficient VPKI prototype according to the

standard

  • How to enhance privacy towards the infrastructure
  • Envision support for future vehicular services
  • Safety as a service, not the target application
  • Location based services, Pay-as-you-drive systems
  • Enhance current VPKI to support vehicular services
  • AAA solution with current VPKI architecture as the starting

point

  • Authentication: Legitimate part of the system
  • Authorization: Right to access a service
  • Accountability: Track of consumption

8 / 20

slide-9
SLIDE 9

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Table of Contents

Introduction Status and current Directions for VC Future Challenges for VC List of Future Challenges VeSPA Architecture & Operation Analysis of VeSPA Efficiency & Privacy Improvements Future Work Ongoing Work and Future Directions

9 / 20

slide-10
SLIDE 10

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

VeSPA: Vehicular Security and Privacy-preserving Architecture

  • “Kerberized” version of a VPKI
  • Efficient VPKI Credential Management Architecture
  • Enhanced VPKI design with respect to privacy
  • Cryptographic tickets to support AAA
  • Tickets:
  • tkt = SigLTCA([te], {S1}, . . . , {Sn})
  • Carrier of service subscription information
  • Anonymous proof of access to obtain pseudonyms
  • Authorization and Authentication to the PCA
  • Limited lifetime dependent on vehicle subscription to the

service

  • Revocable upon misbehavior

10 / 20

slide-11
SLIDE 11

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

VeSPA: Operation

  • AAA check at LTCA
  • LTCA issues ticket
  • 73, 5msec/ticket
  • Ticket per service/access
  • Increased anonymity set
  • Low overhead introduced
  • Ticket received
  • Request for new

pseudonyms

  • Communication over TLS

(one-way authentication)

11 / 20

slide-12
SLIDE 12

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

VeSPA: Protocols

Pseudonym Provision:

  • V −

→LTCA: Sigkv (t1,Request) LTv

  • LTCA−

→V : tkt

  • V −

→PCA:t3,tkt,{K 1

v ,...,K n v }

  • PCA−

→V :t4,{Ps1

v ,...,Psn v }

Resolution Protocol:

  • RA−

→PCA: SigRA(Pi

v,t1)

  • PCA−

→RA: SigPCA(tkt,t2)

  • RA−

→LTCA: SigRA(tkt,t3)

  • LTCA−

→RA: SigLTCA(LTv,t4)

12 / 20

slide-13
SLIDE 13

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Table of Contents

Introduction Status and current Directions for VC Future Challenges for VC List of Future Challenges VeSPA Architecture & Operation Analysis of VeSPA Efficiency & Privacy Improvements Future Work Ongoing Work and Future Directions

13 / 20

slide-14
SLIDE 14

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Implementation Details

  • OpenCA for cryptographic operations
  • ECC-256 keys for digital certificates
  • 1609.2 standard compatible
  • Separate machines for each entity:
  • Intel Xeon 3.4 GHz, 8 GB RAM
  • System scales up with more machines or..
  • stronger equipment
  • Communications over encrypted TLS channel (one-way

authentication)

  • Authentication of server
  • Confidentiality

14 / 20

slide-15
SLIDE 15

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Increased Privacy against the VPKI

15 / 20

slide-16
SLIDE 16

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Privacy against the Infrastructure

16 / 20

slide-17
SLIDE 17

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Pseudonym Provision Efficiency

1 10 20 50 100 200 500 1000 2 4 6 8 10 12 14 16 18 Number of Pseudonyms Latency [seconds] Preparing the Request Entire Operations on the Server Entire Communication Verification and Storage

Infrastructure, Vehicle, Communications Efficiency vs number of requested pseudonyms

17 / 20

slide-18
SLIDE 18

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Pseudonym Revocation Efficiency

1 10 100 1000 10,000 100,000 400 800 1200 1600 2000 2400 2800 3200 3600 Number of Revoked Pseudonyms in CRL Latency [milliseconds] Preparing the Request Entire Operations on the Server Entire Communication Verification and Storage

Infrastructure, Vehicle, Communications Efficiency vs number of revoked pseudonyms

18 / 20

slide-19
SLIDE 19

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Table of Contents

Introduction Status and current Directions for VC Future Challenges for VC List of Future Challenges VeSPA Architecture & Operation Analysis of VeSPA Efficiency & Privacy Improvements Future Work Ongoing Work and Future Directions

19 / 20

slide-20
SLIDE 20

Introduction Future Challenges for VC VeSPA Analysis of VeSPA Future Work

Overview & Future Work

VeSPA:

  • Efficient VPKI Prototype according to the standards
  • Increased Privacy to towards the infrastructure
  • Enhanced VPKI with AAA capabilities
  • A VPKI able to support vehicular services

Ongoing Work:

  • Integration of Anonymous Authentication Mechanisms
  • Extensions to support multi-Domain VPKI architectures

20 / 20