I was doing some writing last night, specifically documenting the process described in my previous blog post on accessing VSCs. I grabbed an NTUSER.DAT from within a user profile from the mounted image/VHD file, as well as the same file from within the oldest VSC available, and ran my RegRipper userassist plugin against both of the files.
Let me say that I didn't have to use robocopy to extract the files...I could've just run the plugin against the mounted files/file systems. However, I had some other thoughts in mind, and wanted the copies of the hive files to try things out. Besides, robocopy is native to Windows 7.
If the value of VSCs has not been recognized or understood by now, then we have a serious issue on our hands. For example, we know that the UserAssist key values can tell use the last time that a user performed a specific action via the shell (ie, clicked on a desktop shortcut, followed the Start->Programs path, etc.) and how often they've done so. So, the 15th time a user performs a certain action, we only see the information about that instance, and not the previous times.
By mounting the oldest VSC and parsing the user hive file, I was able to get additional historical information, including other times that applications (Quick Cam, Skype, iTunes, etc.) had been launched by the user. This provides some very significant historical data that can be used to fill in gaps in a timeline, particularly when there's considerable time between when an incident
occurred and when it was detected.
Here's an excerpt of the UserAssist values from the NTUSER.DAT in the mounted VHD:
Thu Jan 21 03:10:26 2010 Z
UEME_RUNPATH:C:\Program Files\Skype\Phone\Skype.exe (14)
Tue Jan 19 00:37:46 2010 Z
UEME_RUNPATH:C:\Program Files\iTunes\iTunes.exe (296)
And here's an excerpt of similar values from the NTUSER.DAT within the mounted VSC:
Sat Jan 9 11:40:31 2010 Z
UEME_RUNPATH:C:\Program Files\iTunes\iTunes.exe (293)
Fri Jan 8 04:13:40 2010 Z
UEME_RUNPATH:C:\Program Files\Skype\Phone\Skype.exe (8)
Some pretty valuable information there...imagine how this could be used to fill in a timeline.
And the really interesting thing is that just about everything else you'd do with a regular file system, you can do with the mounted VSC...run AV scans, run RegRipper or the forensic scanner, etc.
3 comments:
There is so much that can be done with Volume Shadow copies: recover wiped files, roll back encryption, illuminate hidden root kits, run-time "trip wire" . . .
Unfortunately, that sound I here is water hitting the floor, which means I just over-flowed the marine tank and shorted out some lights and pumps and flooded the carpet. Got to go.
We have discovered an incompatibility between vssadmin.exe and Microsoft's Application Virtualization software. If App-V is installed on a system, vssadmin will error out when you try to list the shadow copies. The solutions for the moment are to either not have App-V installed on the machine you are using to examine shadow copies, or use something other than vssadmin.exe to identify or list shadow copies. App-V has no impact on imaging shadow copies with G. Garner's dd.exe.
App-V
Post a Comment