Perl or Java) other methods for translation is be required.
.jpg "prodiscover basic 64")
#PRODISCOVER BASIC 64 SOFTWARE#
Unix), or in software that is intentionally platform-independent ( e.g.
#PRODISCOVER BASIC 64 WINDOWS#
NTFS file timestamps, according to the documentation of the ‘FILETIME’ data structure in the Windows Software Development Toolkit, is a “64-bit value representing the number of 100-nanosecond intervals since Janu(UTC)”.Ĭonversion from this internal format to a format more suitable for human interpretation is performed by the Windows system call FileTimeToSystemTime(), which extracts the year, month, day, hour, minutes, seconds and milliseconds from the timestamp data. Similar tests need to be created and performed for other timestamp formats.Īlso, I am ignoring time zone adjustments and daylight savings time: the translation to be examined will cover Universal Coordinated Time (UTC) only. NTFS is probably the most common source of timestamps that an analyst will have to deal with, so it is important to ensure that timestamp translation is correct. I will also some present some test results from applying the tests to different tools.įor the moment, I am concerned only with NTFS file timestamps. My primary purpose this article is to present a simple design of test data suitable for determining if there are errors or problems in how a particular tool performs these operations. If there are any errors in this step, the result will clearly be less reliable than expected. As these timestamps usually are stored in some internal format, additional software is needed to interpret them and translate them into a format an analyst can easily understand. File and directory timestamps are one of the resources forensic analysts use for determining when something happened, or in what particular order a sequence of events took place.
0 kommentar(er)
