Block4Forensic An Integrated Lightweight Blockchain Framework For Forensics Applications of Connected Vehicles
Block4Forensic An Integrated Lightweight Blockchain Framework For Forensics Applications of Connected Vehicles
Wi-Fi
Bluetooth
Bluetooth
DSRC
LTE RSU integrity.
Manufacturer Maintenance
service
provider
User
devices
Steering wheel
OBU
Lidar
Forensic
Daemon
Brakes
ECUs
Diagnosis reports
tenance (e.g., steering ability, braking distance) or Bus. The forensic daemon periodically shares the
a previously reported malfunctioning component EDR and BSM data with the insurance company
of a vehicle can provide important clues to deter- through an encrypted channel. Note that only
mine the faulty party. related BSMs are shared when an EDR triggering
Lightweight: The system should have minimum event occurs. On the other hand, the car man-
overhead on endpoints since it includes multiple ufacturers collect regular car diagnostic reports.
parties that may have different capabilities and A cryptographic hash of these data is submitted
resources. to Blockchain for removing the single trust issue.
Privacy: The system should preserve the pri- Both insurance companies and manufacturers
vacy of the participants while also providing the collect those data for analysis. Moreover, main-
flexibility for the participants to selectively reveal tenance records are kept at the maintenance
their data as they wish. service providers, and a hash of each record is
submitted to Blockchain in the same manner. As
B4F Framework an optional extension to the framework, all of the
To enable the vehicular forensics vision, we intro- mentioned data can also be stored in personal
duce a novel blockchain forensic framework as cloud storage.
shown in Fig. 3. The framework connects the Stored data will be used in post-accident sce-
following stakeholders: vehicles, maintenance narios by allowing the parties to disclose their
service providers (e.g., mechanics), vehicle man- data selectively to determine the faulty party. Law
ufacturers, law enforcement, and insurance enforcement authorities play an investigative role
companies. The key features of the envisioned for post-accident scenarios while parties disclose
vehicular forensics system mentioned in the pre- their data with proof of integrity.
vious subsection guided us while building the
blockchain-based vehicular forensics system. Potential Accident Scene
At the heart of design, there is a special foren- An investigator working on an accident scene
sic daemon, which is stationed within the OBU needs to collect all pieces of clues to reconstruct
and constantly retrieves data from EDR, BSMs the accident scene. Once the accident scene is
(i.e., messages received from other vehicles), and reconstructed, the faulty party can be determined
onboard sensors/IoT devices through a CAN accordingly.
Here, we discuss how digital data provided by Reconstructed Scene (f): In this scenario,
B4F assist an investigation. Assume that an acci- B4F data shows that V1 was on autopilot at the
dent scene where Vehicle 1 (V1) collided with accident time. Moreover, the diagnostic records
Vehicle 2 (V2) at an intersection with traffic lights report a failed sensor. Thus, V1 autopilot software
as illustrated in Fig. 4a. The data provided by with faulty input caused the accident, which sug-
B4F may enable various forensically sound scene gests the car manufacturer as the faulty party.
reconstructions as listed below. Various parties might be involved in an acci-
Reconstructed Scene (b): BSM messages dent as exemplified above. Forensic data provid-
include the traffic light status and cars’ last posi- ed by B4F provides a fast and efficient accident
tions. In this scenario, BSM messages reveal that scene reconstruction, which helps any investiga-
V1 started to turn left when the red light was on, tion significantly.
as shown in Fig. 4b. Lights’ statuses are being dis-
seminated by smart traffic lights; thus, when the B4F Components
accident happens, B4F would have stored the last In this section, we first describe the forensics ele-
BSM messages from the traffic lights. Here, data ments and data types, and then we move on to
clearly point out that V1 is the faulty party. elaborate on the specific elements of B4F that
Reconstructed Scene (c): Timestamped data relate to the blockchain structure, its membership
in B4F reveals the existence of another vehicle at management, and storage issues.
the accident scene. Drivers of V1 and V2 started
crossing the road when the light turned green. Forensic Daemon
At that time V3 did not stop at the red light and Here, we explain how the proposed forensic
caused V2 to lose control and hit V1. B4F data daemon interacts with different components of a
uncovers the existence of V3 and resolves such a vehicle. Note that our forensic daemon runs as an
hit case where the faulty party is a third car that application in an OBU thanks to existing software
runs out of the incident area. development kits (SDKs) for custom application
Reconstructed Scene (d): Similar to scene (c), development.
data reveals the existence of V3. However, this The OBU has read access to the vehicle network
time none of the cars violate the rules as the traf- infrastructure. The backbone of the vehicle network
fic light for V3 is also green. BSM data supplied is the CAN bus. In a modern vehicle, many import-
by smart traffic lights would reveal faulty signaling ant substructures like steering wheel motor, braking
as the cause of the accident. system, throttle, tire pressure monitoring system,
Reconstructed Scene (e): In this scenario, B4F seat belt buckle status, and even windshield wip-
data indicates that none of the drivers has violat- ers are controlled and monitored via the CAN bus.
ed the traffic rules. However, by investigating the Thus, the CAN bus may deliver invaluable data in
car diagnostic report history on B4F, the investiga- terms of vehicular forensics to the OBU that can be
tor finds out that after maintenance, the vehicle retrieved by the forensic daemon.
has a pulling problem while braking. Due to this Additionally, through WiFi or Bluetooth inter-
faulty operation in V1, the driver lost control of faces, the forensic daemon can receive data from
the car and hit V2. The history of previous vehicle the driver about his/her health status via wear-
maintenance records helps to resolve this com- ables. Similarly, road conditions and weather data
plicated scenario and suggests the maintenance can be retrieved from RSUs or a driver’s smart-
provider as the faulty party. phone that has applications related to such data.
Figure 6. An overview of the proposed ledger structure. SL: shared ledger; FL: fragmented ledger, which
can hold different data.
user privacy as defined in the attack model of not carry any information related to the forensic
IEEE 1609.2. However, regulations and policies content of EDR&BSM data, car diagnostic reports,
should be assessed for proper disclosure of the provided maintenance, and so on.
user data. In addition, exploiting the VPKI scheme Additionally, note that the user may want to
also addresses the above mentioned membership refuse to submit maintenance or manufacturer
management challenge. Any vehicle that has a data content. Instead, s/he keeps it in personal
valid pseudonym identity can make transactions cloud storage. However, based on regulations
on the proposed Blockchain since participants and policies, in the case of an incident, the
of B4F recognize valid certificates produced by authorities will require the user to disclose this
VPKI. Validator nodes check the validity of the data as needed, the integrity of which is satisfied
certificate and timestamp of the submitted data by the Blockchain.
(i.e., hash of the forensic data). If the timestamp
belongs to the certificate validity period (i.e., Future Research Issues
every five minutes), the transaction is confirmed. As there is growing research on various aspects
The consensus on valid transactions is achieved of connected vehicles, their applications will pro-
by a computationally inexpensive voting-based liferate in coming years, such as driverless cars
Byzantine agreement scheme among validators. and automated fleets. This may result in increased
disputes as a result of incidents. Therefore, we
Lightweight Fragmented Ledger for believe that there is a vast opportunity to pur-
Forensic Participants sue additional research with respect to vehicular
Blockchain is a shared ledger that maintains a grow- forensics in general and our framework in particu-
ing list of blocks which are chained to each other. lar. We list them below:
Each participant stores a copy of the entire histo- • There will be a need to analyze the storage and
ry. In our case, the data are immense, and thus the communication overhead of the B4F frame-
shared ledger can grow dramatically and may cause work by implementing it using an OBU SDK.
both communication and storage overhead. • A punishment/incentive/avoidance mech-
To address this issue, we utilize a fragment- anism should be investigated to prevent
ed ledger instead of storing all forensic data in a members becoming malicious actors. In this
shared ledger. The motivation comes from the regard, a detection mechanism should be
observation that each party has already stored a developed to discover malicious participants.
different fragment of required data. For instance, • The B4F provides a lightweight solution by
a maintenance provider may not be interested just keeping hash values. While this ensures
in the content of periodic EDR data, and thus integrity and immutability of forensic data,
there is no need to keep that content in a shared the availability of this data depends on the
ledger. On the contrary, as insurance compa- individual storage and shared counterparts.
nies keep EDR data in their fragmented ledger, There is no mechanism for ensuring avail-
keeping proof of that data in the shared ledger ability of critical forensic data on blockchain.
is sufficient. Therefore, in B4F, all participants of Therefore, this warrants further research.
the network will have a consensus on the shared • Due to increased availability of data and
ledger. However, each participant maintains blockchain technologies in various domains
just related information that differs from others, for forensic purposes, researchers would
as shown in Fig. 6. Specifically, the difference need to consider a forensic-by-design princi-
between the shared and fragmented ledgers will ple when proposing new systems and mech-
be in forensic data details. The shared ledger does anisms.