±Partners and Sponsors
New Today: 0
New Yesterday: 10
· Webmail Forensics – Digging deeper into Browsers and Mobile Applications
· Operation Endeavour: The Tip of the Iceberg?
· Forensic analysis of the ESE database in Internet Explorer 10
· WhatsApp – discovering timestamps of deleted messages
· Man In The Middle Attack: Forensics
· Extracting Evidence from Destroyed Skype Logs and Cleared SQLite Databases
· Windows 8 File History Analysis
· Understanding Rootkits: Using Memory Dump Analysis for Rootkit Detection
· Bitcoin Forensics Part II: The Secret Web Strikes Back
±Follow Forensic Focus
Encase naming confusing for overwritten and overwriting file
Do you know why Encase calls a file overwritten while it actually shows the overwriting one? It actually shows you something different from what it says it does.
If it shows me an overwriting file, it should call it the overwriting file, not the overwritten file.
I know that some forensic examiners and newbies may be deceived by this. Would it not be better, if it called the area -rather than the file- overwritten and show the current file as overwriting?
- Senior Member
- yunusDo you know why Encase calls a file overwritten while it actually shows the overwriting one? It actually shows you something different from what it says it does.
What you are seeing is a MFT record of a deleted file where the MFT record has not be overwritten but the file has. EnCase (in fact, no program of which I am aware), can display the contents of a file that has been overwritten. What EnCase is showing you is that the file pointer still exists though the file does not.
If you look at the very bottom of the EnCase Window (what they call the Navigation data or GPS), what is displayed is the path to actual file that now occupies the blocks occupied by the deleted file.
- Senior Member