Book Overview & Buying
Table Of Contents
Feedback & Rating

Digital Forensics with Kali Linux

4.3 (11)

Buy this Book

Digital Forensics with Kali Linux

4.3 (11)

Buy this Book

Overview of this book

Kali Linux is a Linux-based distribution used mainly for penetration testing and digital forensics. It has a wide range of tools to help in forensics investigations and incident response mechanisms. You will start by understanding the fundamentals of digital forensics and setting up your Kali Linux environment to perform different investigation practices. The book will delve into the realm of operating systems and the various formats for file storage, including secret hiding places unseen by the end user or even the operating system. The book will also teach you to create forensic images of data and maintain integrity using hashing tools. Next, you will also master some advanced topics such as autopsies and acquiring investigation data from the network, operating system memory, and so on. The book introduces you to powerful tools that will take your forensic abilities and investigations to a professional level, catering for all aspects of full digital forensic investigations from hashing to reporting. By the end of this book, you will have had hands-on experience in implementing all the pillars of digital forensics—acquisition, extraction, analysis, and presentation using Kali Linux tools.

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

Introduction to Digital Forensics

What is digital forensics?

Digital forensics methodology

A brief history of digital forensics

The need for digital forensics as technology advances

Commercial tools available in the field of digital forensics

Operating systems and open source tools for digital forensics

The need for multiple forensics tools in digital investigations

Anti-forensics: threats to digital forensics

Summary

Installing Kali Linux

Software version

Downloading Kali Linux

Installing Kali Linux

Installing Kali Linux in VirtualBox

Summary

Understanding Filesystems and Storage Media

Storage media

Filesystems and operating systems

What about the data?

Data volatility

The paging file and its importance in digital forensics

Summary

Incident Response and Data Acquisition

Digital evidence acquisitions and procedures

Incident response and first responders

Documentation and evidence collection

Chain of Custody

Powered-on versus powered-off device acquisition

Write blocking

Data imaging and hashing

Device and data acquisition guidelines and best practices

Summary

Evidence Acquisition and Preservation with DC3DD and Guymager

Drive and partition recognition in Linux

Maintaining evidence integrity

Using DC3DD in Kali Linux

Image acquisition using Guymager

Summary

File Recovery and Data Carving with Foremost, Scalpel, and Bulk Extractor

Forensic test images used in Foremost and Scalpel

Using Foremost for file recovery and data carving

Using Scalpel for data carving

Bulk_extractor

Summary

Memory Forensics with Volatility

About the Volatility Framework

Downloading test images for use with Volatility

Using Volatility in Kali Linux

Summary

Autopsy – The Sleuth Kit

Introduction to Autopsy – The Sleuth Kit

Sample image file used in Autopsy

Digital forensics with Autopsy

Summary

Network and Internet Capture Analysis with Xplico

Software required

Packet capture analysis using Xplico

Summary

Revealing Evidence Using DFF

Installing DFF

Summary

Customer Reviews

4.3 (11)

5 star

72.7%

4 star

3 star

9.1%

2 star

18.2%

1 star

Maintaining evidence integrity

In an effort to provide proof that the evidence was not tampered with, a hash of the evidence should be provided before and during, or after, an acquisition.

In Kali Linux, we can use the md5sum command followed by the path of the device, to create an MD5 hash of the evidence/input file. For example, md5sum /dev/sdx.

You may also try the command with superuser privileges by typing sudo md5sum /dev/sdx.

For this example, the 2 GB flash drive that I'll be using (named test_usb) is recognized as sdb, and so the command I will be using, is shown in the following screenshot:

In the previous example, the output of the md5sum of the 2 GB flash drive is displayed as 9f038....1c7d3 /dev/sdb. When performing the acquisition or forensic imaging of the drive using DC3DD, we should also have that exact result when hashing the created image file...