Difference between pages "Oxygen Forensic Suite 2" and "Disk Imaging"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Added a box to the right.)
 
(Selective imaging)
 
Line 1: Line 1:
<table style="padding:0.3em; float:right; margin-left:15px; margin-bottom:8px; border:1px solid #A3B1BF; background:#f5faff; text-align:center; font-size:95%; line-height:1.5em;width:220px;">
+
{{expand}}
<tr>
+
<th colspan="2" style="padding:0.1em; font-size:1em; background-color:#cee0f2;">Current version</th>
+
</tr>
+
<tr style="font-size:1em;">
+
  <td align="right"><b>Version Number:</b></td>
+
  <td align="left">1.3</td>
+
</tr>
+
<tr style="font-size:1em;">
+
  <td align="right" ><b>Date Released:</b></td>
+
  <td align="left">12 September 2008</td>
+
</tr>
+
<tr>
+
<th colspan="2" style="padding:0.1em; font-size:1em; background-color:#cee0f2;">Recent changes</th>
+
</tr>
+
<tr style="font-size:1em;">
+
  <td colspan="2" align="left">
+
    <ul>
+
    <li>Added contacts extraction from SIM-Card
+
    <li>Implemented file view in Hex, Text, Unicode, UTF-8 including ability to set more than 50 character sets
+
    </ul>
+
  </td>
+
</tr>
+
<tr>
+
<th colspan="2" style="padding:0.1em; font-size:1em; background-color:#cee0f2;">Screenshots</th>
+
</tr>
+
<tr style="font-size:1em;">
+
  <td colspan="2" align="left">
+
[[Image:OFS2_02_EventLog.png|200px|thumb|center|Event log]]
+
[[Image:OFS2_04_LifeBlog.png|200px|thumb|center|LifeBlog with GPS mapping]]
+
[[Image:OFS2_05_FileBrowser.png|200px|thumb|center|File Browser with Hex viewer]]
+
[[Image:OFS2_08_MessagesExportPDF.png|200px|thumb|center|Sample report]]
+
[http://www.oxygen-forensic.com/en/screenshots/ More screenshots ... ]
+
  </td>
+
</tr>
+
</table>
+
  
===Brief===
+
Disk imaging is the process of making a bit-by-bit copy of a disk. Imaging (in more general terms) can apply to anything that can be considered as a bit-stream, e.g. a physical or logical volumes, network streams, etc.
  
[http://www.oxygen-forensic.com/ Oxygen Forensic Suite 2] by [http://www.oxygen-software.com/ Oxygen Software] is a mobile forensic software for logical analysis of [[cell phones]], [[SmartPhones|smartphones]] and [[PDAs]]. The authors claim that using advanced data access protocols helps to extract much more data than usually.
+
The most straight-forward disk imaging method is reading a disk from start to end and writing the data to a [[:Category:Forensics_File_Formats|Forensics image format]].
 +
This can be a time consuming process especially for disks with a large capacity.
  
===Regular data extraction===
+
== Hardware solutions ==
Oxygen Forensic Suite 2 is able to extract general data like:
+
* device information (IMEI, SW and HW versions, operator, etc),
+
* contacts (names, phones, notes)
+
* calendar events,
+
* messages ([[SMS]]),
+
* log records (incoming/outgoing/missed).
+
* files (images, sounds, videos, documents, etc)
+
  
===Unique data extraction===
+
== Software solutions ==
Besides the general data usually extracted, Oxygen Forensic Suite 2 can extract a lot of unique information:
+
* contacts (last date of contact modification, contacts photos, field labels, contact groups and speed dials)
+
* calendar events (last date of event modification, all event dates, alarm status, recurrences)
+
* messages (e-mails and MMS, messages from custom folders, message SMSC time stamp)
+
* log records ([[GPRS]], [[EDGE]], CSD, HSCSD and Wi-Fi session traffic and time, deleted SMS details)
+
* files (file system from phone memory and flash card)
+
* LifeBlog data (all main phone events like sms, photos, events '''with their geographical coordinates'''),
+
'''Important!''' The list of supported features depends on a certain phone model.
+
  
===Device coverage===
+
== Compressed storage ==
By the October, 2008 Oxygen Forensic Suite 2 supports more than '''1100 devices''': [[Nokia]], Vertu, [[Sony Ericsson]], Samsung, Motorola, [[BlackBerry|Blackberry]], Panasonic, Siemens, HTC, HP, E-Ten, Gigabyte, i-Mate and other mobile phones.
+
Oxygen Forensic Suite 2 has a strong support for [[symbian|Symbian OS]], [[symbian|Nokia S60]], Sony Ericsson UIQ, [[Microsoft Windows Mobile|Windows Mobile 5/6]] and [[BlackBerry|Blackberry]] [[SmartPhones|smartphones]] and communicators.
+
  
===Other===
+
A common technique to reduce the size of an image file is to compress the data.
* The software access devices without using standard protocols like AT, OBEX or SyncML. The Agent installation is required to access smartphones and communicators.
+
On modern computers, with multiple cores, the compression can be done in parallel reducing the output without prolonging the imaging process.
* The software is able to perform data search, to create and print reports.
+
Since the write speed of the target disk can be a bottleneck in imaging process parallel compression can reduce the total time of the imaging process.
* The software has a full support of Unicode standard. So the multilanguage information is read and shown correctly.
+
[[Guymager]] was one of the first imaging tools to implement the concept of multi-process compression for the [[Encase image file format]]. This technique is now used by various imaging tools including [http://www.tableau.com/index.php?pageid=products&model=TSW-TIM Tableau Imager (TIM)]
  
===History===
+
Other techniques like storing the data sparse or '''empty-block compression''' can reduce the total time of the imaging process and the resulting size of new non-encrypted (0-byte filled) disks.
Oxygen Forensic Suite 2 is a third generation of forensic tools by Oxygen Software.
+
* 2004, March. Oxygen Phone Manager II for Nokia phones (Forensic Edition) is released.
+
* 2005, November. Oxygen Phone Manager II for Symbian OS smartphones is released.
+
* 2007, June. Oxygen Phone Manager II (Forensic Edition) becomes a stand alone project with new name "Oxygen Forensic Suite"
+
* 2008, May. Oxygen Forensic Suite 2 is released and presented at Mobile Forensics World 2008.
+
  
===Links===
+
== Error tolerance and recovery ==
* [http://www.oxygen-forensic.com/ Official web site]
+
 
* [http://www.oxygen-software.com/ Oxygen Software web site]
+
== Smart imaging ==
 +
Smart imaging is a combination of techniques to make the imaging process more intelligent.
 +
* Deduplication
 +
* Selective imaging
 +
* Decryption while imaging
 +
 
 +
=== Deduplication ===
 +
Deduplication is the process of determining and storing data that occurs more than once on-disk, only once in the image.
 +
It is even possible to store the data once for a corpus of images using techniques like hash based imaging.
 +
 
 +
=== Selective imaging ===
 +
Selective imaging is a technique to only make a copy of certain information on a disk like the $MFT on an [[NTFS]] volume with the necessary contextual information.
 +
 
 +
[[EnCase]] Logical Evidence Format (LEF) is an example of a selective image; although only file related contextual information is stored in the format by [[EnCase]].
 +
 
 +
=== Decryption while imaging ===
 +
Encrypted data is worst-case scenario for compression. Because the encryption process should be deterministic a solution to reduce the size of an encrypted image is to store it non-encrypted and compressed and encrypt it on-the-fly if required. Although this should be rare since the non-encrypted data is what undergoes analysis.
 +
 
 +
== Also see ==
 +
[[:Category:Forensics_File_Formats|Forensics File Formats]]
 +
 
 +
== External Links ==
 +
* [http://www.tableau.com/pdf/en/Tableau_Forensic_Disk_Perf.pdf Benchmarking Hard Disk Duplication Performance in Forensic Applications], by [[Robert Botchek]]
 +
 
 +
=== Hash based imaging ===
 +
* [http://www.dfrws.org/2010/proceedings/2010-314.pdf Hash based disk imaging using AFF4], by [[Michael Cohen]], [[Bradley Schatz]]

Revision as of 09:23, 21 July 2012

Information icon.png

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

Disk imaging is the process of making a bit-by-bit copy of a disk. Imaging (in more general terms) can apply to anything that can be considered as a bit-stream, e.g. a physical or logical volumes, network streams, etc.

The most straight-forward disk imaging method is reading a disk from start to end and writing the data to a Forensics image format. This can be a time consuming process especially for disks with a large capacity.

Hardware solutions

Software solutions

Compressed storage

A common technique to reduce the size of an image file is to compress the data. On modern computers, with multiple cores, the compression can be done in parallel reducing the output without prolonging the imaging process. Since the write speed of the target disk can be a bottleneck in imaging process parallel compression can reduce the total time of the imaging process. Guymager was one of the first imaging tools to implement the concept of multi-process compression for the Encase image file format. This technique is now used by various imaging tools including Tableau Imager (TIM)

Other techniques like storing the data sparse or empty-block compression can reduce the total time of the imaging process and the resulting size of new non-encrypted (0-byte filled) disks.

Error tolerance and recovery

Smart imaging

Smart imaging is a combination of techniques to make the imaging process more intelligent.

  • Deduplication
  • Selective imaging
  • Decryption while imaging

Deduplication

Deduplication is the process of determining and storing data that occurs more than once on-disk, only once in the image. It is even possible to store the data once for a corpus of images using techniques like hash based imaging.

Selective imaging

Selective imaging is a technique to only make a copy of certain information on a disk like the $MFT on an NTFS volume with the necessary contextual information.

EnCase Logical Evidence Format (LEF) is an example of a selective image; although only file related contextual information is stored in the format by EnCase.

Decryption while imaging

Encrypted data is worst-case scenario for compression. Because the encryption process should be deterministic a solution to reduce the size of an encrypted image is to store it non-encrypted and compressed and encrypt it on-the-fly if required. Although this should be rare since the non-encrypted data is what undergoes analysis.

Also see

Forensics File Formats

External Links

Hash based imaging