{"id":14370,"date":"2020-07-20T00:00:00","date_gmt":"2020-07-20T00:00:00","guid":{"rendered":"https:\/\/adfsolutions.com\/best-mobile-device-investigator-settings\/"},"modified":"2026-03-11T14:18:45","modified_gmt":"2026-03-11T14:18:45","slug":"best-mobile-device-investigator-settings","status":"publish","type":"post","link":"https:\/\/adfsolutions.com\/best-mobile-device-investigator-settings\/","title":{"rendered":"Best Mobile Device Investigator Settings for Evidence Collection"},"content":{"rendered":"\n

In this short digital forensic How To video, Digital Forensic Specialist, Rich Frawley, walks you through the best settings for<\/span> Mobile Device Investigator\u00ae<\/sup><\/a>.  Learn how to choose the best Search Profile Capture selection and how to decipher which captures will get you the information you need for your investigation with our mobile phone forensic software<\/a>. <\/span><\/p>\n\n

When setting up ADF Search Profiles for the first time its sometimes difficult to resist picking everything to see what you’ll get. If that’s your tendency, we’ve already given you the best comprehensive option with the Search Profile named <\/span>Mobile Devices – General Profiling and Mobile Devices – Child Exploitation<\/span><\/em>. <\/span><\/p>\n

However, if you are looking for specific information, you can also create your own Custom Search Profile. In this video you’ll learn what you<\/span> need to do to create a solid profile that will get you the digital evidence you expect.<\/span><\/p>\n

Get Started with ADF Settings in MDI<\/strong><\/span><\/h2>\n

Go to Setup Scans \u2192 New Profile<\/span><\/strong><\/p>\n

ADF Capture Groups are to the left and the captures for each group are on the right hand side.<\/span><\/p>\n

With <\/span>Applications<\/span><\/strong> highlighted you can see the available captures on the right.<\/span><\/p>\n

How to know which captures will work for your investigation?<\/span><\/h3>\n

As a refresher, Artifact Captures recover specific records or information e.g. browsing history records or user account information. Users cannot create or edit Artifact Captures. File Captures recover files matching certain criteria such as file properties, inclusion of keywords or matching hash values. File Captures are supplied with the program and can also be user created. <\/span><\/p>\n

If you look at the <\/span>Installed Applications Capture, <\/span><\/strong>MDI denotes it as an artifact capture by showing the icon of the Operating System it will collect records from, selecting this artifact capture will collect artifacts from Windows, OSx, Android, or iOS.<\/span><\/p>\n

If you look at the <\/span>Messages Capture<\/span><\/strong>, MDI denotes the  icons for the applications it will parse from (Kik, Telegram, Viber, etc.) and know that this will recover artifacts from the specific applications – but what OS will it recover artifacts from? With mobile devices it comes down to what is available in the Advanced Logical Acquisition. Take for example Android, which leaves it to the app vendor, whether or not the app data is stored in the backup, so it is important to know that for certain apps you will not be able to recover data. \"Best<\/span><\/p>\n

Using MDI to Collect Messages: Example Use Case<\/span><\/h3>\n

A popular app right now is Kik, in the video you can take a closer look at this. <\/span><\/p>\n

Communications \u2192 Messages \u2192 Expand<\/span><\/strong><\/p>\n

You’ll see all the messaging apps that are supported – but which OS will be supported? You can refer to the ADF t<\/span>echnical specifications documents to get more<\/span> information on MDI, system requirements and specific supported apps. Each supported application lists all the artifacts that the ADF Captures can collect from as well as Operating Systems, smartphone apps, and computer applications (for ADF computer forensics). The versions listed are the ones that were tested but the Captures probably support older and newer versions as well.<\/span><\/p>\n

In the video example, Kik is broken down into two categories – Messages and Contacts. You’ll see the app versions tested and the OS that information can be parsed from. So even though Android is listed, it was tested and determined that data was available in earlier OS extractions from an Android, and in the example, Rich demonstrates extracting evidence from Android 9.<\/span><\/p>\n

When creating a Search Profile you’ll want to select Communication categories so MDI will look for and parse any supported and available apps, however, you now know that Kik records will most likely not be available in the Advanced Logical Backup.<\/span><\/p>\n

Having this knowledge you can now select the screenshots capture located in the Capture Groups Applications<\/a>.<\/span><\/p>\n

Collecting Digital Evidence with MDI Screenshots for Unsupported Applications <\/strong><\/span><\/h3>\n

In a scenario where an investigator or examiner has an Android device and Kik is the messaging Application you are interested in you’ll have <\/span> checked the Technical specifications and determined that Kik may not get parsed. In this scenario you have several options:<\/span><\/p>\n

    \n
  1. Mobile Devices – Screenshots<\/strong> to obtain the messages via screenshots. This option does not require the phone to be backed up (See How To use MDI Screenshots video<\/a>)<\/span><\/li>\n
  2. Mobile Devices – General Profiling<\/strong> – a comprehensive scan that also includes the screenshot capture – requires back up (See How to video)<\/span><\/li>\n
  3. Mobile Devices – Custom Search Profile<\/strong> (create your own) requires a back up (See How To create Custom Search Profiles video<\/a>)<\/span><\/li>\n<\/ol>\n

    What to Know and Remember About Mobile Evidence Extraction<\/span><\/h3>\n

    For this purpose we supply a warning after a mobile extraction: <\/span>“This application performed an advanced logical acquisition of an Android\/iOS device. Artifacts may exist that are not collected during this acquisition and will not be presented in the scan results.”<\/span><\/em><\/p>\n

    In other words, an app may be on the phone but it may not be possible to capture results. Be knowledgeable and remember to: <\/span><\/p>\n