![](https://csdnimg.cn/release/download_crawler_static/9994785/bg11.jpg)
Preface
[ 3 ]
What you need for this book
This book is designed to allow you to use different operating platforms (Windows, Mac,
and Linux) through freeware, open source software, and commercial software. Many of the
examples shown can be replicated using either the software tested by the authors or
equivalent solutions that have been mentioned in Appendix B, Tools for iOS Forensics. Some
specific cases require the use of commercial platforms, and among those, we preferred the
platforms that we use in our daily work as forensic analysts (such as Cellebrite UFED,
Oxygen Forensics, Elcomsoft iOS Forensic Toolkit, and Elcomsoft Phone Breaker). In any
case, we were inspired by the principles of ease of use, completeness of information
extracted, and the correctness of the presentation of the results by the software. This book is
not meant to be a form of advertisement for the aforementioned software in any way, and
we encourage you to repeat the tests that are carried out on one operating platform even on
other platforms and software applications.
Who this book is for
This book is intended mainly for a technical audience, and more specifically for forensic
analysts (or digital investigators) who need to acquire and analyze information from mobile
devices running iOS. This book is also useful for computer security experts and penetration
testers because it addresses some issues that must be definitely taken into consideration
before the deployment of this type of mobile devices in business environments or situations
where data security is a necessary condition. Finally, this book can be also of interest for
developers of mobile applications, and they can learn what data is stored in these devices
where the application is used. Thus, they will be able to improve security.
Conventions
In this book, you will find a number of styles of text that distinguish among different kinds
of information. Here are some examples of these styles, and explanations of their meanings.
Code words in text, database table names, folder names, filenames, file extensions,
pathnames, dummy URLs, user input, and Twitter handles are shown as follows:
"Compile the source file by simply typing the make command."
A URL is written as follows: h t t p : / / t h e i p h o n e w i k i . c o m / w i k i / U D I D
A pathname is written as follows:
/private/var/root/Library/Lockdown/data_ark.plist