<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    >
<channel>
    <title>Comments on: NTFS $I30 Index Attributes: Evidence of Deleted and Overwritten Files</title>
    <atom:link href="http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/feed/" rel="self" type="application/rss+xml" />
    <link>http://computer-forensics.sans.org/blog</link>
    <description>SANS Computer Forensic Investigations and Incident Response Blog</description>
    <lastBuildDate>Thu, 20 Jun 2013 9:29:25 +0000</lastBuildDate>
    <language>en</language><item><title>By: Mangard</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-14847</link><dc:creator>Mangard</dc:creator><pubDate>Sun, 13 Jan 2013 00:09:06 +0000</pubDate><description><![CDATA[Chad has had 5 months to run the test with BCWipe Ver.6.  I think it is safe to say that vers. 6 has rendered the $I30 formatting tools as well as this entire approach to forensics obsolete. I'm surprised Jetico does not have EnCase, FTK and the all latest forensic tools to do its own tests. I'm not going to wait for either of you. I'm going to do a brute force sector by sector search for attribute remnants.]]></description><content:encoded><![CDATA[Chad has had 5 months to run the test with BCWipe Ver.6.  I think it is safe to say that vers. 6 has rendered the $I30 formatting tools as well as this entire approach to forensics obsolete. I'm surprised Jetico does not have EnCase, FTK and the all latest forensic tools to do its own tests. I'm not going to wait for either of you. I'm going to do a brute force sector by sector search for attribute remnants.]]></content:encoded></item><item><title>By: Chad Tilbury</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-14381</link><dc:creator>Chad Tilbury</dc:creator><pubDate>Wed, 15 Aug 2012 20:56:52 +0000</pubDate><description><![CDATA[Chris - The $I30 index is a NTFS attribute stored in the Master File Table ($MFT) entry for a directory.  Assuming that your evidence is a hard drive image, you are seeing information parsed from the $MFT belonging to the volume mounted on the computer the hard drive was imaged from.  NTFS attributes do not have Modified/Accessed/Changed/Created times like files and folders do.  That being said, FTK chooses to display timestamps for $I30 files.  $I30 timestamps in FTK correspond to the timestamps of the directory that owns the $I30 attribute (seen as the parent folder in FTK).  Thus if you are looking at a modified time for the $I30, it could mean that something within the folder was changed.  If you are looking at a creation time, it could mean the folder was created.  --Chad]]></description><content:encoded><![CDATA[Chris - The $I30 index is a NTFS attribute stored in the Master File Table ($MFT) entry for a directory.  Assuming that your evidence is a hard drive image, you are seeing information parsed from the $MFT belonging to the volume mounted on the computer the hard drive was imaged from.  NTFS attributes do not have Modified/Accessed/Changed/Created times like files and folders do.  That being said, FTK chooses to display timestamps for $I30 files.  $I30 timestamps in FTK correspond to the timestamps of the directory that owns the $I30 attribute (seen as the parent folder in FTK).  Thus if you are looking at a modified time for the $I30, it could mean that something within the folder was changed.  If you are looking at a creation time, it could mean the folder was created.  --Chad]]></content:encoded></item><item><title>By: Chris</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-14376</link><dc:creator>Chris</dc:creator><pubDate>Wed, 15 Aug 2012 20:10:36 +0000</pubDate><description><![CDATA[Hey Chad, Found an $I30 in FTK and it was written roughly 30 seconds after a device was plugged into the computer via USB. Is FTK reading the $I30 from the external device or from the host computer? Thanks]]></description><content:encoded><![CDATA[Hey Chad, Found an $I30 in FTK and it was written roughly 30 seconds after a device was plugged into the computer via USB. Is FTK reading the $I30 from the external device or from the host computer? Thanks]]></content:encoded></item><item><title>By: Rob Lee</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-14351</link><dc:creator>Rob Lee</dc:creator><pubDate>Fri, 10 Aug 2012 17:47:23 +0000</pubDate><description><![CDATA[This is great information.  Thank you for posting.  We will try and do the experiment again.]]></description><content:encoded><![CDATA[This is great information.  Thank you for posting.  We will try and do the experiment again.]]></content:encoded></item><item><title>By: Jetico Technical Team</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-14311</link><dc:creator>Jetico Technical Team</dc:creator><pubDate>Fri, 03 Aug 2012 04:53:38 +0000</pubDate><description><![CDATA[Hello Chad,We are developers of BCWipe wiping software that you mentioned in your article.We would like to inform you and anybody interested that we released BCWipe v6 in March,2012  and it  can wipe B-tree structure and  attributes of directories stored in MFT, including $I30 .We would greatly appreciate if you re-do the tests with BCWipe v6 - try to parse$I30 again and post the results here.]]></description><content:encoded><![CDATA[Hello Chad,We are developers of BCWipe wiping software that you mentioned in your article.We would like to inform you and anybody interested that we released BCWipe v6 in March,2012  and it  can wipe B-tree structure and  attributes of directories stored in MFT, including $I30 .We would greatly appreciate if you re-do the tests with BCWipe v6 - try to parse$I30 again and post the results here.]]></content:encoded></item><item><title>By: Chad Tilbury</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-13811</link><dc:creator>Chad Tilbury</dc:creator><pubDate>Sat, 14 Apr 2012 05:17:16 +0000</pubDate><description><![CDATA[Willi did in fact have the timestamps swapped.  Good catch!  Please make sure you are working from the latest version on github. https://github.com/williballenthin/INDXParse]]></description><content:encoded><![CDATA[Willi did in fact have the timestamps swapped.  Good catch!  Please make sure you are working from the latest version on github. https://github.com/williballenthin/INDXParse]]></content:encoded></item><item><title>By: John McCash</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-13571</link><dc:creator>John McCash</dc:creator><pubDate>Tue, 06 Mar 2012 19:26:55 +0000</pubDate><description><![CDATA[Hey Chad! I found this a couple of weeks ago, and was using it on a case. I used bodyfile output, and then converted to more standardized csv with log2timeline. One thing I just noticed is that last access times seem to be coming out as [M] times... Does Willi have two of the timestamp positions reversed, or am I or log2timeline mangling something?ThanksJohn McCash]]></description><content:encoded><![CDATA[Hey Chad! I found this a couple of weeks ago, and was using it on a case. I used bodyfile output, and then converted to more standardized csv with log2timeline. One thing I just noticed is that last access times seem to be coming out as [M] times... Does Willi have two of the timestamp positions reversed, or am I or log2timeline mangling something?ThanksJohn McCash]]></content:encoded></item><item><title>By: Yogesh Khatri</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-13161</link><dc:creator>Yogesh Khatri</dc:creator><pubDate>Wed, 12 Oct 2011 06:35:16 +0000</pubDate><description><![CDATA[Chad, Good write up on $I30 and the timestamp issue, just yesterday someone emailed me about the same issue. It seems people have started to pay attention to this old artifact :-) with lots of scripts available now.I too had written a script to parse $I30 files about a couple of years back as no scripts existed then. In addition to the usual $I30 files, it tries to make sense of the garbage (partial entries). The big additional feature is it also searches in MFT slack for old $I30 entries (where $I30 is now non resident). For those wanting another free script here it is (http://42llc.net/?p=336). Output is available in a GUI, exportable to csv file.]]></description><content:encoded><![CDATA[Chad, Good write up on $I30 and the timestamp issue, just yesterday someone emailed me about the same issue. It seems people have started to pay attention to this old artifact :-) with lots of scripts available now.I too had written a script to parse $I30 files about a couple of years back as no scripts existed then. In addition to the usual $I30 files, it tries to make sense of the garbage (partial entries). The big additional feature is it also searches in MFT slack for old $I30 entries (where $I30 is now non resident). For those wanting another free script here it is (http://42llc.net/?p=336). Output is available in a GUI, exportable to csv file.]]></content:encoded></item><item><title>By: Chad Tilbury</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-13106</link><dc:creator>Chad Tilbury</dc:creator><pubDate>Mon, 03 Oct 2011 01:47:30 +0000</pubDate><description><![CDATA[Chris -Thanks for weighing in.  I look forward to trying out your EnScript!]]></description><content:encoded><![CDATA[Chris -Thanks for weighing in.  I look forward to trying out your EnScript!]]></content:encoded></item><item><title>By: Chris Taylor</title><link>http://computer-forensics.sans.org/blog/2011/09/20/ntfs-i30-index-attributes-evidence-of-deleted-and-overwritten-files/comment-page-1/#comment-13101</link><dc:creator>Chris Taylor</dc:creator><pubDate>Sun, 02 Oct 2011 17:16:04 +0000</pubDate><description><![CDATA[Tim,You are both right!  Within the index are structures that match the $FN attributes, which is what Chad is alluding to. But, the timestamps for every file in the index are updated to whatever that file's current times are anytime the index is rewritten. So, the index should contain relatively current times that match the file's $SI attibute's times. C]]></description><content:encoded><![CDATA[Tim,You are both right!  Within the index are structures that match the $FN attributes, which is what Chad is alluding to. But, the timestamps for every file in the index are updated to whatever that file's current times are anytime the index is rewritten. So, the index should contain relatively current times that match the file's $SI attibute's times. C]]></content:encoded></item></channel></rss>