Difference between pages "SIMCon" and "AFF Development Task List"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Started wikifying the page.)
 
(High Priority)
 
Line 1: Line 1:
{{Wikify}}
+
== High Priority ==
  
'''SIMCon''' is a program that securely images all files on a [[GSM]] [[SIM Card]] with a standard PC-SC [[smart card]] reader, either [[serial]] or [[USB]]. After imaging, the forensic investigator can then analyze the contents of the card. Specific information regarding stored numbers, call history, and text messages are available.  
+
* Create man pages and/or documentation for AFF toolkit. To wit:
  
== Features ==
+
* [[aimage]]
 +
* [[ident]]
 +
* [[afcat]]
 +
* [[afcompare]]
 +
* [[afconvert]]
 +
* [[affix]]
 +
* [[affuse]]
 +
* [[afinfo]]
 +
* [[afstats]]
 +
* [[afxml]]
 +
* [[afsegment]]
  
* Acquire all available files on a [[SIM Card]] and store in an archive file
+
* Add a usage description to [[afcat]]. When run with no arguments the output should say what the program does.
* Analyze and interpret content of files
+
* Recover deleted text messages stored on the card
+
* Manage PIN and PUK codes
+
* Compatible with [[SIM Cards]] and [[USIM Cards]]
+
* Print reports of evidence
+
* Secure file archive using hashing
+
* Export items to popular spreadsheet programs
+
* Supports international charsets
+
* Contains a "content" view for plain text viewing of data, as well as a hexadecimal view for more specific analysis.
+
  
== Data Acquisition ==
+
* Create man pages and/or documentation for AFF library functions (e.g. ,<tt>af_open</tt>, <tt>af_get_imagesize</tt>)
  
Simcon is also capable of aquiring the following data from a SIM:
+
* Build library as a shared library using libtool. This will allow developers using the library to just link to the AFF. Without it, developers must link to the static library and the individual libraries necessary <em>on that machine</em>. There is no good way to determine those extra libraries.
  
* Abbreviated Dialing Numbers (ADN),
+
* Document that <tt>af_write</tt> may not be called without first setting the <tt>image_pagesize</tt> value inside of the <tt>AFFILE</tt> structure. Not doing so causes a divide by zero error. Perhaps we should 1. Check that <tt>image_pagesize</tt> is not zero and 2. Set <tt>image_pagesize</tt> to a known good default value when opening a new AFF file for writing.
* Last Dialed Numbers (LDN)
+
* Short Message Service (SMS)
+
* Public Land Mobile Network (PLMN) selector
+
* Forbidden PLMNs, Location Information (LOCI)
+
* General Packet Radio Service (GPRS) location
+
* International Mobile Subscriber Identity (IMSI)
+
* Integrated Circuit Card Identifier (ICCID)
+
* Mobile Subscriber ISDN (MSISDN)
+
* Service Provider Name (SPN)
+
* Phase Identification
+
* SIM Service Table (SST)
+
* Language Preference (LP)
+
* Card Holder Verification (CHV1) and (CHV2)
+
* Broadcast Control Channels (BCCH)
+
* Ciphering Key (Kc)
+
* Ciphering Key Sequence Number
+
* Emergency Call Code
+
* Fixed Dialing Numbers (FDN)
+
* Forbidden PLMNs
+
* Local Area Identitity (LAI)
+
* Own Dialing Number
+
* Temporary Mobile Subscriber Identity (TMSI)
+
* Routing Area Identifier (RIA) netowrk code
+
* Service Dialing Numbers (SDNs)
+
* Service Provider Name
+
* Depersonalizatoin Keys
+
  
All [[GSM]] cell phones today have a subscriber identity module (SIM) to identify the phone onto the network. [http://www.simcon.no SIMCon] is an application to acquire all of the information from the [[SIM Card]].
+
* Check aimage ability to write a file of 1,073,741,825 bytes ((2**30)+1). Correctly reported reading/writing a file that was a 1,073,741,824 random byte stream, but did not pick up the extra byte when it was added to the file. ls -la correctly shows the size with the extra byte. Also, added 42 additional bytes which were not apparently read or written.
  
The [[SIM Card]] provides secure storing of the key identifying a mobile phone service subscriber, subscription information, preferences and text messages.  Network state information, such as the current location area identity (LAI), is also stored on the card.  When a handset is turned off and then back on, it will search for the LAI that it was in, rather than having to search all frequencies that the phone operates in.  This saves time when trying to log on to the network. (Subscriber, 2006, para. 1)
+
== Medium Priority ==
  
By using [http://www.simcon.no SIMCon] and a smart card reader, all of the above information and more can be pulled off of the card without knowing the PIN or the PUK of the card. The PIN and the PUK are ways to keep the information on the card secure. They also can be used as a security feature on the phone, not allowing anyone to use a phone to access the [[SIM Card]] without knowing the codes.
+
* How about renaming the library to libaff? That would allow developers to link with <tt>-laff</tt> instead of <tt>-lafflib</tt>. To my knowledge, there is no existing library named AFF already.
 +
:: Response: The problem with doing this is that we have AFFLIB.ORG; AFF.ORG is the Arab Film Festival.  
  
[http://www.simcon.no SIMCon] is an application developed by Inside Out Forensics in Norway.  It is designed for use by the law enforcement community, and it can be obtained free of charge by emailing [http://www.simcon.no SIMCon] and identifying the officers and unit.  However, for anyone outside the law enforcement community, it is not free. 
+
* Is there a set of segment names that must be defined to have a ''valid'' AFF file?
  
== Review ==
+
* Document that <tt>af_open</tt> (when writing a file) does more than a standard <tt>fopen</tt> command. The command writes an AFF stub of some kind to the output file. Users should be cautioned not to use this function as a test, lest they overwrite data.
  
* SIMCon makes the acquisition of data very easy, simply inserting the SIM Card to the appropriate Sim card reader, and clicking acquire is all that is needed to start analyzing evidence.  After the acquisition of the data is complete SimCon will show the user a screen with two halves. 
+
* Does <tt>af_open</tt> refuse to open a file for writing if it already exists? If so, what kind of error does it return?
  
* On the left panel is the different data sectors of the [[SIM Card]] that can either be checked on or off depending on what is needed.  After choosing what data sectors are needed, the right panel will be populated with the selected data.  Some of the most useful pieces of information that are shown are: the International Mobile Subscriber Identity number, every contacts name and number, and all SMS messages sent and received both stored and deleted.
+
* Document how to programmatically enumerate all segments and values in a file. That is, explain how to get the output of <tt>$ afinfo -a</tt>.
  
* SIMCon also comes with two more handy features that are key to an investigation and in a court of law.  The first is [http://www.simcon.no SIMCon]s' feature that allows the printing of a report.  [http://www.simcon.no SIMCon] will format and populate a report with the contents of the users’ choosing.  This can list all the key pieces to an investigation and is an excellent piece of evidence to be used in a court of law.  The second feature is the exportation of the acquired data.  [http://www.simcon.no SIMCon] allows the exportation of all SMS messages and also of all contacts.  When these exported files are opened in a program such as Microsoft Excel the data can be read, sorted, and analyzed in a format of the users design. 
+
== Low Priority ==
  
* When SMS messages are exported [http://www.simcon.no SIMCon] automatically adds the following information about every message: file, item, status, service center, message type, number, time stamp, and text.  When the contacts are exported [http://www.simcon.no SIMCon] automatically adds the following information about every contact: file, item, identifier, and number.  For reference a report of an acquired [[SIM card]] is enclosed as well as a document that tells what information is added into an exported file at the end of this document.
+
* Add library function to open standard input. Perhaps:
  
* SIMCon is known to have issues while imaging multiple cards in the same session of the program. These issues include the appearance of random characters in both the contacts list and in the [[SMS]]. These complications are outlined in the paper [[:Image:Huser_Timothy_SIMCon_paper.doc|Running head: SIM CARD FORENSICS WITH SIMCON SOFTWARE]] by [[User:Thuser|Timothy D. Huser]].
+
<pre>AFFILE * af_open_stdin(void);</pre>
 
+
* Currently there is no "data-dump" mode in which one can simply dump data exactly as it is on the card in order to have a more pure investigation of the contents. This has proven to be a major setback up to version 1.1, as the automatic parsing of information from the card sometimes leaves certain details unseen, especially in the content view.
+
 
+
== External Links ==
+
 
+
* [http://www.simcon.no SIMCon]
+
* [http://en.wikipedia.org/wiki/Subscriber_Identity_Module Wikipedia: Subscriber Identity Module]
+
* [http://www.simcon.no/ InsideOut Forensics]
+

Revision as of 11:55, 1 August 2007

High Priority

  • Create man pages and/or documentation for AFF toolkit. To wit:
* aimage
* ident
* afcat
* afcompare
* afconvert
* affix
* affuse
* afinfo
* afstats
* afxml
* afsegment
  • Add a usage description to afcat. When run with no arguments the output should say what the program does.
  • Create man pages and/or documentation for AFF library functions (e.g. ,af_open, af_get_imagesize)
  • Build library as a shared library using libtool. This will allow developers using the library to just link to the AFF. Without it, developers must link to the static library and the individual libraries necessary on that machine. There is no good way to determine those extra libraries.
  • Document that af_write may not be called without first setting the image_pagesize value inside of the AFFILE structure. Not doing so causes a divide by zero error. Perhaps we should 1. Check that image_pagesize is not zero and 2. Set image_pagesize to a known good default value when opening a new AFF file for writing.
  • Check aimage ability to write a file of 1,073,741,825 bytes ((2**30)+1). Correctly reported reading/writing a file that was a 1,073,741,824 random byte stream, but did not pick up the extra byte when it was added to the file. ls -la correctly shows the size with the extra byte. Also, added 42 additional bytes which were not apparently read or written.

Medium Priority

  • How about renaming the library to libaff? That would allow developers to link with -laff instead of -lafflib. To my knowledge, there is no existing library named AFF already.
Response: The problem with doing this is that we have AFFLIB.ORG; AFF.ORG is the Arab Film Festival.
  • Is there a set of segment names that must be defined to have a valid AFF file?
  • Document that af_open (when writing a file) does more than a standard fopen command. The command writes an AFF stub of some kind to the output file. Users should be cautioned not to use this function as a test, lest they overwrite data.
  • Does af_open refuse to open a file for writing if it already exists? If so, what kind of error does it return?
  • Document how to programmatically enumerate all segments and values in a file. That is, explain how to get the output of $ afinfo -a.

Low Priority

  • Add library function to open standard input. Perhaps:
AFFILE * af_open_stdin(void);