@night 1803 access accessdata active directory admissibility ads aduc aim aix ajax alissa torres amcache analysis anjp anssi answer key antiforensics apfs appcompat appcompatflags applocker april fools argparse arman gungor arsenal artifact extractor attachments attacker tools austin automating automation awards aws azure azuread back to basics backstage base16 best finds beta bias bitcoin bitlocker blackbag blackberry enterprise server blackhat blacklight blade blanche lagny book book review brute force bsides bulk extractor c2 carved carving case ccdc cd burning ceic cfp challenge champlain chat logs Christmas Christmas eve chrome cit client info cloud forensics command line computer forensics computername conference schedule consulting contest cool tools. tips copy and paste coreanalytics cortana court approved credentials cryptocurrency ctf cti summit cut and paste cyberbox Daily Blog dbir deep freeze defcon defender ata deviceclasses dfa dfir dfir automation dfir exposed dfir in 120 seconds dfir indepth dfir review dfir summit dfir wizard dfrws dfvfs dingo stole my baby directories directory dirty file system disablelastaccess discount download dropbox dvd burning e01 elastic search elcomsoft elevated email recovery email searching emdmgmt Encyclopedia Forensica enfuse eric huber es eshandler esxi evalexperience event log event logs evidence execution exfat ext3 ext4 extended mapi external drives f-response factory access mode false positive fat fde firefox for408 for498 for500 for526 for668 forenisc toolkit forensic 4cast forensic lunch forensic soundness forensic tips fraud free fsutil ftk ftk 2 full disk encryption future gcfe gcp github go bag golden ticket google gsuite guardduty gui hackthebox hal pomeranz hashlib hfs honeypot honeypots how does it work how i use it how to howto IE10 imaging incident response indepth information theft infosec pro guide intern internetusername Interview ios ip theft iphone ir itunes encrypted backups jailbreak jeddah jessica hyde joe sylve journals json jump lists kali kape kevin stokes kibana knowledgec korman labs lance mueller last access last logon leanpub libtsk libvshadow linux linux-3g live systems lnk files log analysis log2timeline login logs london love notes lznt1 mac mac_apt macmini magnet magnet user summit mathias fuchs md viewer memorial day memory forensics metaspike mft mftecmd mhn microsoft milestones mimikatz missing features mlocate mobile devices mojave mount mtp multiboot usb mus mus 2019 mus2019 nccdc netanalysis netbios netflow new book new years eve new years resolutions nominations nosql notifications ntfs ntfsdisablelastaccessupdate nuc nw3c objectid offensive forensics office office 2016 office 365 oleg skilkin osx outlook outlook web access owa packetsled paladin path specification pdf perl persistence pfic plists posix powerforensics powerpoint powershell prefetch psexec py2exe pyewf pyinstaller python pytsk rallysecurity raw images rdp re-c re-creation testing reader project recipes recon recursive hashing recycle bin redteam regipy registry registry explorer registry recon regripper remote research reverse engineering rhel rootless runas sample images san diego SANS sans dfir summit saturday Saturday reading sbe sccm scrap files search server 2008 server 2008 r2 server 2012 server 2019 setmace setupapi sha1 shadowkit shadows shell items shellbags shimcache silv3rhorn skull canyon skype slow down smb solution solution saturday sop speed sponsors sqlite srum ssd stage 1 stories storport sunday funday swgde syscache system t2 takeout telemetry temporary files test kitchen thanksgiving threat intel timeline times timestamps timestomp timezone tool tool testing training transaction logs triage triforce truecrypt tsk tun naung tutorial typed paths typedpaths uac unc understanding unicorn unified logs unread usb usb detective usbstor user assist userassist usnjrnl validation vhd video video blog videopost vlive vmug vmware volatility vote vss web2.0 webcast webinar webmail weekend reading what are you missing what did they take what don't we know What I wish I knew whitfield windows windows 10 windows 2008 windows 7 windows forensics windows server winfe winfe lite wmi write head xboot xfs xways yarp yogesh zimmerman zone.identifier

Daily Blog #536: USB 3.0 External Storage Drive Forensics: Changes in registry locations

Hello Reader,
             Everything changes and we can never rest when it comes to testing and validating our forensic artifacts. This time the change has come to large external storage drives, such as the Seagate USB 3.0 drive I have next to me. If you've been doing USB forensics lately you may have noticed a conspicuous lack of large external storage drives lately in your tool reports.  This is because the underlying driver has changed away from USBStor and SAS to Storport.

You read Microsoft's write up on Storport here: https://docs.microsoft.com/en-us/windows-hardware/drivers/storage/storport-driver


First notice that the drive I have attached a Seagate Backup Plus drive with Serial Number NA9G5MN0 does not appear in the USBStor Key:


Storport allows for faster drive access than the previous driver could provide which is why the slower flash drives are still using and creating USBStor artifacts while newer faster drives are loading Storport drivers.

This is important as which registry keys we can rely on to find these devices has changed.

To start with we can look at the DeviceClasses GUID
{2accfe60-c130-11d2-b082-00a0c91efb8b}
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/guid-devinterface-storageport

This GUID is the Storport devices GUID and in the below screenshot we can see my internal nvme drive is located here, a VHD I mounted previously and lastly the external storage drive I plugged in.




Notice that the serial number recorded is listed as "MSFT30NA9G5MN0"

Microsoft for Storport devices appears to be prepending the MSFT30 to the serial numbers and then the actual drive serial number follows, NA9G5MN0 which I can verify is the serial number printed on the drive.

In addition the DeviceClass GUID
{a5dcbf10-6530-11d2-901f-00c04fb951ed}
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/guid-devinterface-usb-device

Which is for all USB devices regardless of driver loaded you can see my attached drive below:

Next comes the key from the Windows Portable Devices Key which will reveal the volume name of the drive:

And the USB key which will show the basic USB info

Which lead me to the question, where there some key I wasn't aware of that would allow me to connect all of these elements to understand that the volume label found in the Windows Portal Devices Key corresponded to the serial number recorded in the others. This is when I found a key I wasn't previously paying attention to called DeviceContainers.


Looking closer

we can see that this key connects the SCSI device description for the Storport driver loaded with the 0'd out serial number to the Volume GUID in the Storage and Windows Portal Devices key to the USB enum key which reveals the VID, PID and actual serial number of the drive.

Now I just need to put this into code which I'll likely do this week in the Test Kitchen as every case that involves USB storage analysis will need this logical added now.


Labels: ,

Post a Comment

[blogger][disqus][facebook][spotim]

Author Name

Contact Form

Name

Email *

Message *

Powered by Blogger.