Examination of GPS ...
 
Notifications
Clear all

Examination of GPS wearables

4 Posts
2 Users
0 Reactions
553 Views
(@chrisormond89)
New Member
Joined: 10 years ago
Posts: 2
Topic starter  

I am currently trying to research the best possible method of acquiring data (hopefully forensically) from wearable GPS tech.

I have noticed that quite a few of these watches, especially Garmin, have no data ports and transfer their data via wireless USB adapters.

I have a device in particular that I will be examining which is a Garmin Forerunner 410, which is not supported by major mobile forensic tools (XRY, Cellebrite, etc.) and I am wondering if anybody else has had experience with these types of devices and what their actions were?

Does anyone have any suggestions that could assist?

Many thanks in advance!


   
Quote
(@trewmte)
Noble Member
Joined: 19 years ago
Posts: 1877
 

I am currently trying to research the best possible method of acquiring data……
…….Garmin Forerunner 410

Did you have a look at these to give you some ideas

Garmin_Forerunner_620_ENG_2013_01_18.pdf

https://www8.garmin.com/support/download_details.jsp?id=3741

http//support.trainerroad.com/hc/en-us/articles/201408970-ANT-USB-Stick-Troubleshooting


   
ReplyQuote
(@chrisormond89)
New Member
Joined: 10 years ago
Posts: 2
Topic starter  

Apologies if I've misread your post but I have no problem in connecting the device via the ANT+ USB transfer stick. I was wondering if there was a forensic way of acquiring the data or whether it has to be done using the native software and the forensically analysed from the data files.


   
ReplyQuote
(@trewmte)
Noble Member
Joined: 19 years ago
Posts: 1877
 

Your original post indicates you have a desire to do something but not how far into that research process you had got.

There is little research in this area as you know and on that basis you may think

1) The developer kit looks to be the best route whereby add your program to communicate via the USB+development board to initially determine boot options following power up and test if you can boot from USB with a program that can acquire a raw image.

2) use a write-blocker with native software to see what read / write activity occurs

3) sniff the native software traffic on the USB connection between PC / DUT


   
ReplyQuote
Share: