challenges faced wi...
 
Notifications
Clear all

challenges faced with unallocated space

6 Posts
4 Users
0 Reactions
676 Views
(@tootypegs)
Trusted Member
Joined: 18 years ago
Posts: 80
Topic starter  

Just thinking today about unallocated space. When carving out files a lot of the time you don’t get any information regarding them and where they have come from when live on the system. In your experiences have you found this to be detrimental to your cases and what ways? Is this something that we just have to put up with and accept this is how it is? I’m just trying to get a few opinions on this topic as I have recently encountered a couple of situations where I would have loved to have known where a certain file once existed before deletion!

Cheers guys


   
Quote
(@mscotgrove)
Prominent Member
Joined: 17 years ago
Posts: 940
 

A lot of files in unallocated space will also be known as deleted files. Therefore you want to determine where allocated files are stored, where deleted files were stored, before you try and carve just the remaining unallocated files.

This is not a complete answer to your question, but it may help with maybe 50% of the files you find in unallocated space.


   
ReplyQuote
(@joethomas)
Trusted Member
Joined: 16 years ago
Posts: 65
 

Could you hex keyword search for the logical size of the carved file in little endian to try and find it in MFT fragments or maybe $I30's?


   
ReplyQuote
(@tootypegs)
Trusted Member
Joined: 18 years ago
Posts: 80
Topic starter  

i wondered if it was worth using a clean install and monitoring test files as they enter unallocated. As they are deleted areas on the disk could be logged. There may be some sort of pattern or structure to the way that the they enter unallocated and reside on the disk which will allow a "guess" as to where it was before hand. May even allow you to get an idea by seeing what files surround them that are currently live. Obviously wouldn't stand up in court. Maybe an unallocated parse haha…i wish (


   
ReplyQuote
(@mscotgrove)
Prominent Member
Joined: 17 years ago
Posts: 940
 

When a file is deleted no data is moved. There is no area of the disk specifically 'unallocated'. Any sector/cluster can be used, or not used.
A file is deleted by either removing it's pointer, or (in NTFS) setting a flag in the pointer (MFT). The area used by the that file can then be used again.

You may beable to find information from the logfile, but logs normally recyle their space, so only recent changes could be tracked


   
ReplyQuote
(@joachimm)
Estimable Member
Joined: 17 years ago
Posts: 181
 

I’m just trying to get a few opinions on this topic as I have recently encountered a couple of situations where I would have loved to have known where a certain file once existed before deletion!

On WIndows check various system resources the book Windows Forensic Analysis will help you on your way. Other operating systems other resources.

Or a resource I recently wrote an article about the Windows Search database
http//www.forensicfocus.com/windows-search-forensics


   
ReplyQuote
Share: