Book Image

iOS Forensics Cookbook

By : Bhanu Birani, Mayank Birani
Book Image

iOS Forensics Cookbook

By: Bhanu Birani, Mayank Birani

Overview of this book

Mobile device forensics is a branch of digital forensics that involves the recovery of evidence or data in a digital format from a device without affecting its integrity. With the growing popularity of iOS-based Apple devices, iOS forensics has developed immense importance. To cater to the need, this book deals with tasks such as the encryption and decryption of files, various ways to integrate techniques withsocial media, and ways to grab the user events and actions on the iOS app. Using practical examples, we’ll start with the analysis keychain and raw disk decryption, social media integration, and getting accustomed to analytics tools. You’ll also learn how to distribute the iOS apps without releasing them to Apple’s App Store. Moving on, the book covers test flights and hockey app integration, the crash reporting system, recovery tools, and their features. By the end of the book, using the aforementioned techniques, you will be able to successfully analyze iOS-based devices forensically.
Table of Contents (13 chapters)

Analyzing crash reports


In the previous topics, we have seen various ways to generate and gather crash reports. In this section, our primary focus will be on the ways to analyze the crash reports. This will help us better understand the reasons for crashes and their possible fixes. By default, crashes are not generated in a human-readable format; to read crashes, we need to symbolicate them using the .dysm file.

Getting ready

Open Xcode and navigate to the Organizer window. The Organizer window should list all the crashes for all the apps developed by your team. The following steps will help you in analyzing them.

How to do it...

  1. Go to Window | Organizer. Choose Crashes.

  2. Select an app from the left column. The list of applications is fetched from iTunes Connect and it will obtain all the information about every version.

  3. In the second column, you can see the versions and the build of your app that encountered a crash.

  4. To see where exactly in the code there was a crash, navigate to the right panel...