Difference between pages "Research Topics" and "Talk:Write Blockers"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(SleuthKit Enhancements)
 
(How are they more valuable than mount -o ro?)
 
Line 1: Line 1:
Interested in doing research in computer forensics? Looking for a master's topic, or just some ideas for a research paper? Here is our list. Please feel free to add your own ideas.
+
== How are they more valuable than mount -o ro? ==
  
==Short-Term Engineering Projects==
+
To add value, wouldn't a write-blocker need to be infallible, then *proven* to be infallible? (That is, proven to be as such, within the margin demonstrated by proving compliance with RTCA/DO-178B using Criticality Level 1). [[User:John Crout|johnc]] 17:49, 28 December 2011 (PST)
These projects would make a nice master's thesis or the start of a PhD.
+
 
+
; Physical layer access to flash storage.
+
: Gain access to the physical layer of SD or USB flash storage device. This will require reverse-engineering the proprietary APIs or gaining access to proprietary information from the manufacturers. Use these APIs to demonstrate the feasibility of recovering residual data that has been overwritten at the logical layer but which is still present at the physical layer.
+
 
+
===SleuthKit Enhancements===
+
[[SleuthKit]] is the popular open-source system for forensics and data recovery.
+
* Add support for a new file system:
+
** The [[YAFFS]] [[flash file system]]. (YAFFS2 is currently used on the Google G1 phone.)
+
** The [[JFFS2]] [[flash file system]]. (JFFS2 is currently used on the One Laptop Per Child laptop.)
+
** [[XFAT]], Microsoft's new FAT file system.
+
** [[EXT4]]
+
* Enhance support for an existing file system:
+
** Report the physical location on disk of compressed files.
+
** Add support for NTFS encrypted files (EFS)
+
** Extend SleuthKit's implementation of NTFS to cover Transaction NTFS (TxF) (see [[NTFS]])
+
* Write a FUSE-based mounter for SleuthKit, so that disk images can be forensically mounted using TSK.
+
 
+
===Timeline Analysis===
+
; Timeline Visualization and Analysis
+
: Write a new timeline viewer that supports Logfile fusion (with offsets) and provides the ability to view the logfile in the frequency domain.
+
; Changed Clocks
+
: Detect a system that has had its clock changed.
+
 
+
==Research Areas==
+
These are research areas that could easily grow into a PhD thesis.
+
; Stream-based Forensics
+
: Process the entire disk with one pass to minimize seek time.  (You may find it necessary to do a quick metadata scan first.)
+
; Stegnography Detection (general purpose)
+
: Detect the use of stegnography by through the analysis of file examplars and specifications.
+
; Sanitization Detection
+
: Detect and diagnose sanitization attempts.
+
; Compressed Data Reconstruction
+
: Reconstruct decompressed data from a GZIP file after the first 1K has been removed.
+
;Evidence Falsification Detection
+
: Automatically detect falsified digital evidence through the use of inconsistency in file system allocations, application data allocation, and log file analysis.
+
; Visualization of data/information in digital forensic context
+
: SWOT of current visualization techniques in forensic tools; improvements; feasibility of 3D representation;
+
 
+
==Correlation==
+
* Logfile correlation
+
* Document identity identification
+
* Correlation between stored data and intercept data
+
* Online Social Network Analysis
+
** Find and download in a forensically secure manner all of the information in a social network (e.g. Facebook, LinkedIn, etc.) associated with a targeted individual.
+
** Determine who is searching for a targeted individual. This might be done with a honeypot, or documents with a tracking device in them, or some kind of covert Facebook App.
+
* Automated grouping/annotation of low-level events, e.g. access-time, log-file entry, to higher-level events, e.g. program start, login
+
 
+
==Programming Projects==
+
===File Visualization===
+
Write a program that visualizes the contents of a file, sort of like hexedit, but with other features:
+
* Automatically pull out the strings
+
* Show histogram
+
* Detect crypto and/or stenography.
+
I would write the program in java with a plug-in architecture.
+
 
+
===Carving===
+
Write [[Carver 2.0 Planning Page | Carver 2.0]]
+
 
+
Write a generic NTFS compressed carver
+
 
+
===fiwalk Enhancements===
+
* Rewrite the metadata extraction system.
+
* Extend [[fiwalk]] to report the NTFS "inodes."
+
 
+
==File Format analysis==
+
Analysis of file format for forensic artefacts; could be combined with programming to build code that parses the format.
+
 
+
* Continue work on the [[Extensible Storage Engine (ESE) Database File (EDB) format]] in regard to
+
** Fill in the missing information about older ESE databases
+
** Exchange EDB (MAPI database), STM
+
** Active Directory (Active Directory working document available on request)
+
* Continue work on the [[Notes Storage Facility (NSF)]] (code available on request)
+
* Microsoft SQL Server databases
+
 
+
__NOTOC__
+

Revision as of 20:49, 28 December 2011

How are they more valuable than mount -o ro?

To add value, wouldn't a write-blocker need to be infallible, then *proven* to be infallible? (That is, proven to be as such, within the margin demonstrated by proving compliance with RTCA/DO-178B using Criticality Level 1). johnc 17:49, 28 December 2011 (PST)