Difference between pages "Upcoming events" and "Windows Prefetch File Format"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Calls For Papers)
 
(Section A)
 
Line 1: Line 1:
<b>PLEASE READ BEFORE YOU EDIT THE LISTS BELOW</b><br>
+
{{expand}}
When events begin the same day, events of a longer length should be listed first.  New postings of events with the same date(s) as other events should be added after events already in the list. Please use three-letter month abbreviations (i.e. Sep, NOT Sept. or September), use two digit dates (i.e. Jan 01 NOT Jan 1), and use date ranges rather than listing every date during an event(i.e. Jan 02-05, NOT Jan 02, 03, 04, 05).<br>
+
<i>Some events may be <u>limited</u> to <b>Law Enforcement Only</b> or to a specific audience.  Such restrictions should be noted when known.</i>
+
  
This is a BY DATE listing of upcoming events relevant to [[digital forensics]]. It is not an all inclusive list, but includes most well-known activities.  Some events may duplicate events on the generic [[conferences]] page, but entries in this list have specific dates and locations for the upcoming event.
+
A Windows Prefetch file consists of one file header and multiple file sections with different content. Not all content has an obvious forensic value.
  
This listing is divided into three sections (described as follows):<br>
+
As far as have been possible to ascertain, there is no public description of the format. The description below has been synthesised from examination
<ol><li><b><u>[[Upcoming_events#Calls_For_Papers|Calls For Papers]]</u></b> - Calls for papers for either Journals or for Conferences, relevant to Digital Forensics (Name, Closing Date, URL)</li><br>
+
of multiple prefetch files.
<li><b><u>[[Upcoming_events#Conferences|Conferences]]</u></b> - Conferences relevant for Digital Forensics (Name, Date, Location, URL)</li><br>
+
<li><b><u>[[Training Courses and Providers]]</u></b> - Training </li><br></ol>
+
  
== Calls For Papers ==
+
== Characteristics ==
Please help us keep this up-to-date with deadlines for upcoming conferences that would be appropriate for forensic research.
+
{| class="wikitable"
 +
|-
 +
| <b>Integers</b>
 +
| stored in little-endian
 +
|-
 +
| <b>Strings</b>
 +
| Stored as [http://en.wikipedia.org/wiki/UTF-16/UCS-2 UTF-16 little-endian] without a byte-order-mark (BOM).
 +
|-
 +
| <b>Timestamps</b>
 +
| Stored as [http://msdn2.microsoft.com/en-us/library/ms724284.aspx Windows FILETIME] in UTC.
 +
|-
 +
|}
  
{| border="0" cellpadding="2" cellspacing="2" align="top"
+
== File header ==
|- style="background:#bfbfbf; font-weight: bold"
+
The file header is 84 bytes of size and consists of:
! width="30%|Title
+
{| class="wikitable"
! width="15%"|Due Date
+
! width="15%"|Notification Date
+
! width="40%"|Website
+
 
|-
 
|-
|Eighth International Workshop on Systematic Approaches to Digital Forensics Engineering
+
! Field
|Jun 24, 2013
+
! Offset
|Oct 01, 2013
+
! Length
|http://conf.ncku.edu.tw/sadfe/sadfe13/
+
! Type
 +
! Notes
 
|-
 
|-
|8th International Conference on Malicious and Unwanted Software - Malware in the Era of Cloud Services and Mobile Endpoints
+
| H1
|Jul 12, 2013
+
| 0x0000
|Aug 12, 2013
+
| 4
|http://www.malwareconference.org/index.php?option=com_docman&task=doc_download&gid=8&Itemid=51
+
| DWORD
 +
| Format version (see format version section below)
 
|-
 
|-
|5th International Workshop on Managing Insider Security Threats
+
| H2
|Jul 31, 2013
+
| 0x0004
|Aug 31, 2013
+
| 4
|http://isyou.info/conf/mist13/cfp4mist13.txt
+
| DWORD
 +
| Signature 'SCCA' (or in hexadecimal representation 0x53 0x43 0x43 0x4)
 
|-
 
|-
|AAFS 66th Annual Scientific Meeting
+
| H3
|Aug 01, 2013
+
| 0x0008
|Nov, 2013
+
| 4
|http://www.aafs.org/aafs-66th-annual-scientific-meeting
+
| DWORD?
 +
| Unknown - Values observed: 0x0F - Windows XP, 0x11 - Windows 7, Windows 8.1
 
|-
 
|-
|21st Network & Distributed System Security Symposium
+
| H4
|Aug 05, 2013
+
| 0x000C
|Nov 01, 2013
+
| 4
|http://www.internetsociety.org/events/ndss-symposium-2014/ndss-2014-call-papers
+
| DWORD
 +
| Prefetch file size (or length) (sometimes referred to as End of File (EOF)).
 
|-
 
|-
|9th International Conference on Cyber Warfare and Security (ICCWS-2014)
+
| H5
|Sep 02, 2013 (abstract)
+
|0x0010
|Sep 09, 2013 (abstract)<br>Dec 30, 2013 (final paper)
+
| 60
|http://academic-conferences.org/iciw/iciw2014/iciw14-call-papers.htm
+
| USTR
 +
| The name of the (original) executable as a Unicode (UTF-16 litte-endian string), up to 29 characters and terminated by an end-of-string character (U+0000). This name should correspond with the one in the prefetch file filename.
 
|-
 
|-
|IFIP WG 11.9 International Conference on Digital Forensics
+
| H6
|Sep 15, 2013
+
|0x004C
|Oct 15, 2013
+
|4
|http://www.ifip119.org/Conferences/WG11-9-CFP-2014.pdf
+
|DWORD
 +
|The prefetch hash. This hash value should correspond with the one in the prefetch file filename.
 +
|-
 +
| H7
 +
|0x0050
 +
|4
 +
|?
 +
| Unknown (flags)? Values observed: 0 for almost all prefetch files (XP); 1 for NTOSBOOT-B00DFAAD.pf (XP)
 
|-
 
|-
 
|}
 
|}
  
See also [http://www.wikicfp.com/cfp/servlet/tool.search?q=forensics WikiCFP 'Forensics']
+
It's worth noting that the name of a carved prefetch file can be restored using the information in field H5 and H6, and its size can be determined by field H4.
  
== Conferences ==
+
=== Format version ===
{| border="0" cellpadding="2" cellspacing="2" align="top"
+
 
|- style="background:#bfbfbf; font-weight: bold"
+
{| class="wikitable"
! width="40%"|Title
+
! width="20%"|Date/Location
+
! width="40%"|Website
+
 
|-
 
|-
|FIRST Conference
+
! Value
|Jun 16-21<br>Bangkok, Thailand
+
! Windows version
|http://conference.first.org/2013/
+
 
|-
 
|-
|The 1st ACM Workshop on Information Hiding and Multimedia Security
+
| 17 (0x11)
|Jun 17-19<br>Montpellier, France
+
| Windows XP, Windows 2003
|http://ihmmsec.org/
+
 
|-
 
|-
|28th IFIP TC-11 SEC 2013 International Information Security and Privacy Conference
+
| 23 (0x17)
|Jul 08-10<br>Auckland, New Zealand
+
| Windows Vista, Windows 7
|http://www.sec2013.org/
+
 
|-
 
|-
|The Second International Workshop on Cyber Patterns: Unifying Design Patterns with Security, Attack and Forensic Patterns
+
| 26 (0x1a)
|Jul 08-09<br>Abingdon, Oxfordshire, United Kingdom
+
| Windows 8.1 (note this could be Windows 8 as well but has not been confirmed)
|http://tech.brookes.ac.uk/CyberPatterns2013
+
 
|-
 
|-
|10th Conference on Detection of Intrusions and Malware & Vulnerability Assessment (DIMVA)
+
|}
|Jul 18-19<br>Berlin, Germany
+
 
|http://dimva.sec.t-labs.tu-berlin.de/
+
=== File information ===
 +
The format of the file information is version dependent.
 +
 
 +
Note that some other format specifications consider the file information part of the file header.  
 +
 
 +
==== File information - version 17 ====
 +
The file information – version 17 is 68 bytes of size and consists of:
 +
{| class="wikitable"
 
|-
 
|-
|Symposium On Usable Privacy and Security (SOUPS)
+
! Field
|Jul 24-26<br>Newcastle, United Kingdom
+
! Offset
|http://cups.cs.cmu.edu/soups/2013/
+
! Length
 +
! Type
 +
! Notes
 
|-
 
|-
|BlackHat USA
+
|  
|Jul 27-Aug 01<br>Las Vegas, NV
+
| 0x0054
|https://www.blackhat.com/us-13/
+
| 4
 +
| DWORD
 +
| The offset to section A. The offset is relative from the start of the file.
 
|-
 
|-
|DFRWS 2013
+
|  
|Aug 04-07<br>Monterey, CA
+
| 0x0058
|http://dfrws.org/2013
+
| 4
 +
| DWORD
 +
| The number of entries in section A.
 
|-
 
|-
|Regional Computer Forensics Group GMU 2013
+
|  
|Aug 05-09<br>Fairfax, VA
+
| 0x005C
|http://www.rcfg.org
+
| 4
 +
| DWORD
 +
| The offset to section B. The offset is relative from the start of the file.
 
|-
 
|-
|6th USENIX Workshop on Large-Scale Exploits and Emergent Threats (LEET '13)
+
|  
|Aug 12<br>Washington, DC
+
| 0x0060
|https://www.usenix.org/conferences?page=1
+
| 4
 +
| DWORD
 +
| The number of entries in section B.
 
|-
 
|-
|8th USENIX Workshop on Hot Topics in Security (HotSec '13)
+
|  
|Aug 13<br>Washington, DC
+
| 0x0064
|https://www.usenix.org/conferences?page=1
+
| 4
 +
| DWORD
 +
| The offset to section C. The offset is relative from the start of the file.
 
|-
 
|-
|22nd USENIX Security Symposium - USENIX Security '13
+
|  
|Aug 14-16<br>Washington, DC
+
| 0x0068
|https://www.usenix.org/conference/usenixsecurity13
+
| 4
 +
| DWORD
 +
| Length of section C.
 
|-
 
|-
|6th International Workshop on Digital Forensics (WSDF 2013)
+
|  
|Sep 02-06<br>Regensburg, Germany
+
| 0x006C
|http://www.ares-conference.eu/conf/index.php?option=com_content&view=article&id=49&Itemid=95
+
| 4
 +
| DWORD
 +
| Offset to section D. The offset is relative from the start of the file.
 
|-
 
|-
|2013 HTCIA International Conference & Training Expo
+
|  
|Sep 08-11<br>Summerlin, NV
+
| 0x0070
|http://www.htciaconference.org/
+
| 4
 +
| DWORD
 +
| The number of entries in section D.
 
|-
 
|-
|New Security Paradigms Workshop (NSPW)
+
|  
|Sep 09-12<br>The Banff Center, Canada
+
| 0x0074
|http://www.nspw.org/current/
+
| 4
 +
| DWORD
 +
| Length of section D.
 
|-
 
|-
|Black Hat-Regional Summit
+
|  
|Sep 10-12<br>Istanbul, Turkey
+
| 0x0078
|https://www.blackhat.com/is-13/
+
| 8
 +
| FILETIME
 +
| Latest execution time (or run time) of executable (FILETIME)
 
|-
 
|-
|French-Speaking Days on Digital Investigations-Journées Francophones de l'Investigation Numérique (AFSIN)
+
|  
|Sep 10-12<br>Neuchâtel, Switzerland
+
| 0x0080
|https://www.afsin.org/
+
| 16
 +
| ?
 +
| Unknown ? Possibly structured as 4 DWORD. Observed values: /0x00000000 0x00000000 0x00000000 0x00000000/, /0x47868c00 0x00000000 0x47860c00 0x00000000/ (don't exclude the possibility here that this is remnant data)
 
|-
 
|-
|5th International Conference on Digital Forensics & Cyber Crime
+
|  
|Sep 25-27<br>Moscow, Russia
+
| 0x0090
|http://d-forensics.org/2013/show/home
+
| 4
 +
| DWORD
 +
| Execution counter (or run count)
 
|-
 
|-
|VB2013 - the 23rd Virus Bulletin International Conference
+
|  
|Oct 02-04<br>Berlin, Germany
+
| 0x0094
|http://www.virusbtn.com/conference/vb2013/index
+
| 4
 +
| DWORD?
 +
| Unknown ? Observed values: 1, 2, 3, 4, 5, 6 (XP)
 
|-
 
|-
|16th International Symposium on Research in Attacks, Intrusions and Defenses (RAID)
+
|}
|Oct 23-25<br>St. Lucia
+
 
|http://www.raid2013.org/
+
==== File information - version 23 ====
 +
The file information – version 23 is 156 bytes of size and consists of:
 +
{| class="wikitable"
 
|-
 
|-
|5th International Workshop on Managing Insider Security Threats
+
! Field
|Oct 24-25<br>Busan, South Korea
+
! Offset
|http://isyou.info/conf/mist13/index.htm
+
! Length
 +
! Type
 +
! Notes
 
|-
 
|-
|4th Annual Open Source Digital Forensics Conference (OSDF)
+
|  
|Nov 04-05<br>Chantilly, VA
+
| 0x0054
|http://www.basistech.com/about-us/events/open-source-forensics-conference/
+
| 4
 +
| DWORD
 +
| The offset to section A. The offset is relative from the start of the file.
 
|-
 
|-
|Paraben Forensic Innovations Conference
+
|  
|Nov 13-15<br>Salt Lake City, UT
+
| 0x0058
|http://www.pfic-conference.com/
+
| 4
 +
| DWORD
 +
| The number of entries in section A.
 
|-
 
|-
|8th International Workshop on Systematic Approaches to Digital Forensic Engineering (SADFE)
+
|  
|Nov 21-22<br>Hong Kong, China
+
| 0x005C
|http://conf.ncku.edu.tw/sadfe/sadfe13/
+
| 4
 +
| DWORD
 +
| The offset to section B. The offset is relative from the start of the file.
 
|-
 
|-
|Black Hat-Regional Summit
+
|  
|Nov 26-27<br>Sao Paulo, Brazil
+
| 0x0060
|https://www.blackhat.com/sp-13
+
| 4
 +
| DWORD
 +
| The number of entries in section B.
 
|-
 
|-
|29th Annual Computer Security Applications Conference (ACSAC)
+
|  
|Dec 09-13<br>New Orleans, LA
+
| 0x0064
|http://www.acsac.org
+
| 4
 +
| DWORD
 +
| The offset to section C. The offset is relative from the start of the file.
 
|-
 
|-
|IFIP WG 11.9 International Conference on Digital Forensics
+
|  
|Jan 08-10<br>Vienna, Austria
+
| 0x0068
|http://www.ifip119.org/Conferences/
+
| 4
 +
| DWORD
 +
| Length of section C.
 
|-
 
|-
|AAFS 66th Annual Scientific Meeting
+
|  
|Feb 17-22<br>Seattle, WA
+
| 0x006C
|http://www.aafs.org/aafs-66th-annual-scientific-meeting
+
| 4
 +
| DWORD
 +
| Offset to section D. The offset is relative from the start of the file.
 
|-
 
|-
|21st Network & Distributed System Security Symposium
+
|  
|Feb 23-26<br>San Diego, CA
+
| 0x0070
|http://www.internetsociety.org/events/ndss-symposium-2014/
+
| 4
 +
| DWORD
 +
| The number of entries in section D.
 
|-
 
|-
|9th International Conference on Cyber Warfare and Security (ICCWS-2014)
+
|  
|Mar 24-25<br>West Lafayette, IN
+
| 0x0074
|http://academic-conferences.org/iciw/iciw2014/iciw14-home.htm
+
| 4
 +
| DWORD
 +
| Length of section D.
 
|-
 
|-
|2014 IEEE Symposium on Security and Privacy
+
|  
|May 16-23<br>Berkley, CA
+
| <b>0x0078</b>
|http://www.ieee.org/conferences_events/conferences/conferencedetails/index.html?Conf_ID=16517
+
| <b>8</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
|
 +
| 0x0080
 +
| 8
 +
| FILETIME
 +
| Latest execution time (or run time) of executable (FILETIME)
 +
|-
 +
|
 +
| 0x0088
 +
| 16
 +
| ?
 +
| Unknown
 +
|-
 +
|
 +
| 0x0098
 +
| 4
 +
| DWORD
 +
| Execution counter (or run count)
 +
|-
 +
|
 +
| 0x009C
 +
| 4
 +
| DWORD?
 +
| Unknown
 +
|-
 +
|
 +
| <b>0x00A0</b>
 +
| <b>80</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 
|-
 
|-
 
|}
 
|}
  
==See Also==
+
==== File information - version 26 ====
* [[Training Courses and Providers]]
+
The file information – version 23 is 224 bytes of size and consists of:
==References==
+
{| class="wikitable"
* [http://faculty.cs.tamu.edu/guofei/sec_conf_stat.htm Computer Security Conference Ranking and Statistic]
+
|-
* [http://www.kdnuggets.com/meetings/ Meetings and Conferences in Data Mining and Discovery]
+
! Field
* http://www.conferencealerts.com/data.htm Data Mining Conferences World-Wide]
+
! Offset
 +
! Length
 +
! Type
 +
! Notes
 +
|-
 +
|
 +
| 0x0054
 +
| 4
 +
| DWORD
 +
| The offset to section A. The offset is relative from the start of the file.
 +
|-
 +
|
 +
| 0x0058
 +
| 4
 +
| DWORD
 +
| The number of entries in section A.
 +
|-
 +
|
 +
| 0x005C
 +
| 4
 +
| DWORD
 +
| The offset to section B. The offset is relative from the start of the file.
 +
|-
 +
|
 +
| 0x0060
 +
| 4
 +
| DWORD
 +
| The number of entries in section B.
 +
|-
 +
|
 +
| 0x0064
 +
| 4
 +
| DWORD
 +
| The offset to section C. The offset is relative from the start of the file.
 +
|-
 +
|
 +
| 0x0068
 +
| 4
 +
| DWORD
 +
| Length of section C.
 +
|-
 +
|
 +
| 0x006C
 +
| 4
 +
| DWORD
 +
| Offset to section D. The offset is relative from the start of the file.
 +
|-
 +
|
 +
| 0x0070
 +
| 4
 +
| DWORD
 +
| The number of entries in section D.
 +
|-
 +
|
 +
| 0x0074
 +
| 4
 +
| DWORD
 +
| Length of section D.
 +
|-
 +
|
 +
| 0x0078
 +
| 8
 +
| ?
 +
| Unknown
 +
|-
 +
|
 +
| 0x0080
 +
| 8
 +
| FILETIME
 +
| Latest execution time (or run time) of executable (FILETIME)
 +
|-
 +
|
 +
| <b>0x0088</b>
 +
| <b>7 x 8 = 56</b>
 +
| <b>FILETIME</b>
 +
| <b>Older (most recent) latest execution time (or run time) of executable (FILETIME)</b>
 +
|-
 +
|
 +
| <b>0x00C0</b>
 +
| <b>16</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
|
 +
| 0x00D0
 +
| 4
 +
| DWORD
 +
| Execution counter (or run count)
 +
|-
 +
|
 +
| <b>0x00D4</b>
 +
| <b>4</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
|
 +
| <b>0x00D8</b>
 +
| <b>4</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
|
 +
| <b>0x00DC</b>
 +
| <b>88</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
|}
 +
 
 +
== Section A - Metrics ==
 +
This section contains an array with 20 byte (version 17) or 32 byte (version 23 and 26) metrics entry records.
 +
 
 +
A metrics entry records conists of:
 +
{| class="wikitable"
 +
|-
 +
! Field
 +
! Offset
 +
! Length
 +
! Type
 +
! Notes
 +
|-
 +
|
 +
| 0
 +
| 4
 +
| DWORD
 +
| Start time in ms
 +
|-
 +
|
 +
| 4
 +
| 4
 +
| DWORD
 +
| Duration in ms
 +
|-
 +
|
 +
| 8
 +
| 4
 +
| DWORD
 +
| Average duration in ms
 +
|-
 +
|
 +
| 12
 +
| 4
 +
| DWORD
 +
| Filename string offset <br> The offset is relative to the start of the filename string section (section C)
 +
|-
 +
|
 +
| 16
 +
| 4
 +
| DWORD
 +
| Filename string number of characters without end-of-string character
 +
|-
 +
|
 +
| 20
 +
| 4
 +
| DWORD
 +
| Unknown flags
 +
|-
 +
|
 +
| 24
 +
| 4
 +
| DWORD
 +
| Unknown
 +
|-
 +
|
 +
| 28
 +
| 4
 +
| DWORD
 +
| Unknown
 +
|}
 +
 
 +
== Section B ==
 +
This section contains an array with 12 byte (version 17, 23 and 26) entry records.
 +
 
 +
The actual format and usage of these entry records is currently not known.
 +
 
 +
== Section C - Filename strings ==
 +
This section contains filenames strings, it consists of an array of UTF-16 little-endian formatted strings with end-of-string characters (U+0000).
 +
 
 +
At the end of the section there seems to be alignment padding that can contain remnant values.
 +
 
 +
== Section D - Volumes information (block) ==
 +
 
 +
Section D contains one or more subsections, each subsection refers to directories on a volume.
 +
 
 +
If all the executables and libraries referenced in the C section are from one single disk volume, there will be only one section in the D section. If multiple volumes are referenced by section C, section D will contain multiple sections.  (A simple way to force this situation is to copy, say, NOTEPAD.EXE to a USB drive, and start it from that volume. The corresponding prefetch file will have one D header referring to, e.g. \DEVICE\HARDDISK1\DP(1)0-0+4 (the USB drive), and one to, e.g. \DEVICE\HARDDISKVOLUME1\ (where the .DLLs and other support files were found).
 +
 
 +
In this section, all offsets are assumed to be counted from the start of the D section.
 +
 
 +
=== Volume information ===
 +
The structure of the volume information is version dependent.
 +
 
 +
==== Volume information - version 17 ====
 +
The volume information – version 17 is 40 bytes in size and consists of:
 +
 
 +
{| class="wikitable"
 +
|-
 +
! Field
 +
! Offset
 +
! Length
 +
! Type
 +
! Notes
 +
|-
 +
| VI1
 +
| +0x0000
 +
| 4
 +
| DWORD
 +
| Offset to volume device path (Unicode, terminated by U+0000)
 +
|-
 +
| VI2
 +
| +0x0004
 +
| 4
 +
| DWORD
 +
| Length of volume device path (nr of characters, including terminating U+0000)
 +
|-
 +
| VI3
 +
| +0x0008
 +
| 8
 +
| FILETIME
 +
| Volume creation time.
 +
|-
 +
| VI4
 +
| +0x0010
 +
| 4
 +
| DWORD
 +
| Volume serial number of volume indicated by volume string
 +
|-
 +
| VI5
 +
| +0x0014
 +
| 4
 +
| DWORD
 +
| Offset to sub section E
 +
|-
 +
| VI6
 +
| +0x0018
 +
| 4
 +
| DWORD
 +
| Length of sub section E (in bytes)
 +
|-
 +
| VI7
 +
| +0x001C
 +
| 4
 +
| DWORD
 +
| Offset to sub section F
 +
|-
 +
| VI8
 +
| +0x0020
 +
| 4
 +
| DWORD
 +
| Number of strings in sub section F
 +
|-
 +
| VI9
 +
| +0x0024
 +
| 4
 +
| ?
 +
| Unknown
 +
|-
 +
|}
 +
 
 +
==== Volume information - version 23 ====
 +
The volume information entry – version 23 is 104 bytes in size and consists of:
 +
 
 +
{| class="wikitable"
 +
|-
 +
! Field
 +
! Offset
 +
! Length
 +
! Type
 +
! Notes
 +
|-
 +
| VI1
 +
| +0x0000
 +
| 4
 +
| DWORD
 +
| Offset to volume device path (Unicode, terminated by U+0000)
 +
|-
 +
| VI2
 +
| +0x0004
 +
| 4
 +
| DWORD
 +
| Length of volume device path (nr of characters, including terminating U+0000)
 +
|-
 +
| VI3
 +
| +0x0008
 +
| 8
 +
| FILETIME
 +
| Volume creation time.
 +
|-
 +
| VI4
 +
| +0x0010
 +
| 4
 +
| DWORD
 +
| Volume serial number of volume indicated by volume string
 +
|-
 +
| VI5
 +
| +0x0014
 +
| 4
 +
| DWORD
 +
| Offset to sub section E
 +
|-
 +
| VI6
 +
| +0x0018
 +
| 4
 +
| DWORD
 +
| Length of sub section E (in bytes)
 +
|-
 +
| VI7
 +
| +0x001C
 +
| 4
 +
| DWORD
 +
| Offset to sub section F
 +
|-
 +
| VI8
 +
| +0x0020
 +
| 4
 +
| DWORD
 +
| Number of strings in sub section F
 +
|-
 +
| VI9
 +
| +0x0024
 +
| 4
 +
| ?
 +
| Unknown
 +
|-
 +
| <b>VI10</b>
 +
| <b>+0x0028</b>
 +
| <b>28</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
| <b>VI11</b>
 +
| <b>+0x0044</b>
 +
| <b>4</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
| <b>VI12</b>
 +
| <b>+0x0048</b>
 +
| <b>28</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
| <b>VI13</b>
 +
| <b>+0x0064</b>
 +
| <b>4</b>
 +
| <b>?</b>
 +
| <b>Unknown</b>
 +
|-
 +
|}
 +
 
 +
==== Volume information - version 26 ====
 +
The volume information entry – version 26 appears to be similar to volume information – version 23.
 +
 
 +
=== Sub section E - NTFS file references ===
 +
This sub section can contain NTFS file references.
 +
 
 +
For more information see [https://googledrive.com/host/0B3fBvzttpiiSbl9XZGZzQ05hZkU/Windows%20Prefetch%20File%20(PF)%20format.pdf Windows Prefetch File (PF) format].
 +
 
 +
=== Sub section F - Directory strings ===
 +
This sub sections contains directory strings. The number of strings is stored in the volume information.
 +
 
 +
A directory string is stored in the following structure:
 +
{| class="wikitable"
 +
|-
 +
! Field
 +
! Offset
 +
! Length
 +
! Type
 +
! Notes
 +
|-
 +
|
 +
| 0x0000
 +
| 2
 +
| DWORD
 +
| Number of characters (WORDs) of the directory name. The value does not include the end-of-string character.
 +
|-
 +
|
 +
| 0x0002
 +
|
 +
| USTR
 +
| The directory name as a Unicode (UTF-16 litte-endian string) terminated by an end-of-string character (U+0000).
 +
|-
 +
|}
 +
 
 +
== See Also ==
 +
* [[Prefetch]]
 +
 
 +
== External Links ==
 +
* [https://googledrive.com/host/0B3fBvzttpiiSbl9XZGZzQ05hZkU/Windows%20Prefetch%20File%20(PF)%20format.pdf Windows Prefetch File (PF) format], by the [[libssca|libssca project]]
 +
* [http://bitbucket.cassidiancybersecurity.com/prefetch-parser/wiki/Home Windows Prefetch file format], by the [http://bitbucket.cassidiancybersecurity.com/prefetch-parser prefetch-parser] project.
 +
 
 +
[[Category:File Formats]]

Revision as of 09:57, 22 June 2014

Information icon.png

Please help to improve this article by expanding it.
Further information might be found on the discussion page.

A Windows Prefetch file consists of one file header and multiple file sections with different content. Not all content has an obvious forensic value.

As far as have been possible to ascertain, there is no public description of the format. The description below has been synthesised from examination of multiple prefetch files.

Characteristics

Integers stored in little-endian
Strings Stored as UTF-16 little-endian without a byte-order-mark (BOM).
Timestamps Stored as Windows FILETIME in UTC.

File header

The file header is 84 bytes of size and consists of:

Field Offset Length Type Notes
H1 0x0000 4 DWORD Format version (see format version section below)
H2 0x0004 4 DWORD Signature 'SCCA' (or in hexadecimal representation 0x53 0x43 0x43 0x4)
H3 0x0008 4 DWORD? Unknown - Values observed: 0x0F - Windows XP, 0x11 - Windows 7, Windows 8.1
H4 0x000C 4 DWORD Prefetch file size (or length) (sometimes referred to as End of File (EOF)).
H5 0x0010 60 USTR The name of the (original) executable as a Unicode (UTF-16 litte-endian string), up to 29 characters and terminated by an end-of-string character (U+0000). This name should correspond with the one in the prefetch file filename.
H6 0x004C 4 DWORD The prefetch hash. This hash value should correspond with the one in the prefetch file filename.
H7 0x0050 4 ? Unknown (flags)? Values observed: 0 for almost all prefetch files (XP); 1 for NTOSBOOT-B00DFAAD.pf (XP)

It's worth noting that the name of a carved prefetch file can be restored using the information in field H5 and H6, and its size can be determined by field H4.

Format version

Value Windows version
17 (0x11) Windows XP, Windows 2003
23 (0x17) Windows Vista, Windows 7
26 (0x1a) Windows 8.1 (note this could be Windows 8 as well but has not been confirmed)

File information

The format of the file information is version dependent.

Note that some other format specifications consider the file information part of the file header.

File information - version 17

The file information – version 17 is 68 bytes of size and consists of:

Field Offset Length Type Notes
0x0054 4 DWORD The offset to section A. The offset is relative from the start of the file.
0x0058 4 DWORD The number of entries in section A.
0x005C 4 DWORD The offset to section B. The offset is relative from the start of the file.
0x0060 4 DWORD The number of entries in section B.
0x0064 4 DWORD The offset to section C. The offset is relative from the start of the file.
0x0068 4 DWORD Length of section C.
0x006C 4 DWORD Offset to section D. The offset is relative from the start of the file.
0x0070 4 DWORD The number of entries in section D.
0x0074 4 DWORD Length of section D.
0x0078 8 FILETIME Latest execution time (or run time) of executable (FILETIME)
0x0080 16  ? Unknown ? Possibly structured as 4 DWORD. Observed values: /0x00000000 0x00000000 0x00000000 0x00000000/, /0x47868c00 0x00000000 0x47860c00 0x00000000/ (don't exclude the possibility here that this is remnant data)
0x0090 4 DWORD Execution counter (or run count)
0x0094 4 DWORD? Unknown ? Observed values: 1, 2, 3, 4, 5, 6 (XP)

File information - version 23

The file information – version 23 is 156 bytes of size and consists of:

Field Offset Length Type Notes
0x0054 4 DWORD The offset to section A. The offset is relative from the start of the file.
0x0058 4 DWORD The number of entries in section A.
0x005C 4 DWORD The offset to section B. The offset is relative from the start of the file.
0x0060 4 DWORD The number of entries in section B.
0x0064 4 DWORD The offset to section C. The offset is relative from the start of the file.
0x0068 4 DWORD Length of section C.
0x006C 4 DWORD Offset to section D. The offset is relative from the start of the file.
0x0070 4 DWORD The number of entries in section D.
0x0074 4 DWORD Length of section D.
0x0078 8 ? Unknown
0x0080 8 FILETIME Latest execution time (or run time) of executable (FILETIME)
0x0088 16  ? Unknown
0x0098 4 DWORD Execution counter (or run count)
0x009C 4 DWORD? Unknown
0x00A0 80 ? Unknown

File information - version 26

The file information – version 23 is 224 bytes of size and consists of:

Field Offset Length Type Notes
0x0054 4 DWORD The offset to section A. The offset is relative from the start of the file.
0x0058 4 DWORD The number of entries in section A.
0x005C 4 DWORD The offset to section B. The offset is relative from the start of the file.
0x0060 4 DWORD The number of entries in section B.
0x0064 4 DWORD The offset to section C. The offset is relative from the start of the file.
0x0068 4 DWORD Length of section C.
0x006C 4 DWORD Offset to section D. The offset is relative from the start of the file.
0x0070 4 DWORD The number of entries in section D.
0x0074 4 DWORD Length of section D.
0x0078 8  ? Unknown
0x0080 8 FILETIME Latest execution time (or run time) of executable (FILETIME)
0x0088 7 x 8 = 56 FILETIME Older (most recent) latest execution time (or run time) of executable (FILETIME)
0x00C0 16 ? Unknown
0x00D0 4 DWORD Execution counter (or run count)
0x00D4 4 ? Unknown
0x00D8 4 ? Unknown
0x00DC 88 ? Unknown

Section A - Metrics

This section contains an array with 20 byte (version 17) or 32 byte (version 23 and 26) metrics entry records.

A metrics entry records conists of:

Field Offset Length Type Notes
0 4 DWORD Start time in ms
4 4 DWORD Duration in ms
8 4 DWORD Average duration in ms
12 4 DWORD Filename string offset
The offset is relative to the start of the filename string section (section C)
16 4 DWORD Filename string number of characters without end-of-string character
20 4 DWORD Unknown flags
24 4 DWORD Unknown
28 4 DWORD Unknown

Section B

This section contains an array with 12 byte (version 17, 23 and 26) entry records.

The actual format and usage of these entry records is currently not known.

Section C - Filename strings

This section contains filenames strings, it consists of an array of UTF-16 little-endian formatted strings with end-of-string characters (U+0000).

At the end of the section there seems to be alignment padding that can contain remnant values.

Section D - Volumes information (block)

Section D contains one or more subsections, each subsection refers to directories on a volume.

If all the executables and libraries referenced in the C section are from one single disk volume, there will be only one section in the D section. If multiple volumes are referenced by section C, section D will contain multiple sections. (A simple way to force this situation is to copy, say, NOTEPAD.EXE to a USB drive, and start it from that volume. The corresponding prefetch file will have one D header referring to, e.g. \DEVICE\HARDDISK1\DP(1)0-0+4 (the USB drive), and one to, e.g. \DEVICE\HARDDISKVOLUME1\ (where the .DLLs and other support files were found).

In this section, all offsets are assumed to be counted from the start of the D section.

Volume information

The structure of the volume information is version dependent.

Volume information - version 17

The volume information – version 17 is 40 bytes in size and consists of:

Field Offset Length Type Notes
VI1 +0x0000 4 DWORD Offset to volume device path (Unicode, terminated by U+0000)
VI2 +0x0004 4 DWORD Length of volume device path (nr of characters, including terminating U+0000)
VI3 +0x0008 8 FILETIME Volume creation time.
VI4 +0x0010 4 DWORD Volume serial number of volume indicated by volume string
VI5 +0x0014 4 DWORD Offset to sub section E
VI6 +0x0018 4 DWORD Length of sub section E (in bytes)
VI7 +0x001C 4 DWORD Offset to sub section F
VI8 +0x0020 4 DWORD Number of strings in sub section F
VI9 +0x0024 4  ? Unknown

Volume information - version 23

The volume information entry – version 23 is 104 bytes in size and consists of:

Field Offset Length Type Notes
VI1 +0x0000 4 DWORD Offset to volume device path (Unicode, terminated by U+0000)
VI2 +0x0004 4 DWORD Length of volume device path (nr of characters, including terminating U+0000)
VI3 +0x0008 8 FILETIME Volume creation time.
VI4 +0x0010 4 DWORD Volume serial number of volume indicated by volume string
VI5 +0x0014 4 DWORD Offset to sub section E
VI6 +0x0018 4 DWORD Length of sub section E (in bytes)
VI7 +0x001C 4 DWORD Offset to sub section F
VI8 +0x0020 4 DWORD Number of strings in sub section F
VI9 +0x0024 4  ? Unknown
VI10 +0x0028 28 ? Unknown
VI11 +0x0044 4 ? Unknown
VI12 +0x0048 28 ? Unknown
VI13 +0x0064 4 ? Unknown

Volume information - version 26

The volume information entry – version 26 appears to be similar to volume information – version 23.

Sub section E - NTFS file references

This sub section can contain NTFS file references.

For more information see Windows Prefetch File (PF) format.

Sub section F - Directory strings

This sub sections contains directory strings. The number of strings is stored in the volume information.

A directory string is stored in the following structure:

Field Offset Length Type Notes
0x0000 2 DWORD Number of characters (WORDs) of the directory name. The value does not include the end-of-string character.
0x0002 USTR The directory name as a Unicode (UTF-16 litte-endian string) terminated by an end-of-string character (U+0000).

See Also

External Links