Book Image

Hands-On Network Forensics

By : Nipun Jaswal
2 (2)
Book Image

Hands-On Network Forensics

2 (2)
By: Nipun Jaswal

Overview of this book

Network forensics is a subset of digital forensics that deals with network attacks and their investigation. In the era of network attacks and malware threat, it’s now more important than ever to have skills to investigate network attacks and vulnerabilities. Hands-On Network Forensics starts with the core concepts within network forensics, including coding, networking, forensics tools, and methodologies for forensic investigations. You’ll then explore the tools used for network forensics, followed by understanding how to apply those tools to a PCAP file and write the accompanying report. In addition to this, you will understand how statistical flow analysis, network enumeration, tunneling and encryption, and malware detection can be used to investigate your network. Towards the end of this book, you will discover how network correlation works and how to bring all the information from different types of network devices together. By the end of this book, you will have gained hands-on experience of performing forensics analysis tasks.
Table of Contents (16 chapters)
Free Chapter
1
Section 1: Obtaining the Evidence
4
Section 2: The Key Concepts
8
Section 3: Conducting Network Forensics

Decoding keyboard captures

Another day and another interesting PCAP capture. Have you ever thought that USB keyboards could also reveal a lot of activity and user behavior? We will look at such scenarios in the upcoming chapters, but for now, let's prepare for it. I found an interesting packet-capture file from https://github.com/dbaser/CTF-Write-ups/blob/master/picoCTF-2017/for80-just_keyp_trying/data.pcap. However, on downloading the PCAP file and loading it in Wireshark, I got the following:

Well, I have not seen anything like this, but we know that this is USB data. We can also see that the leftover column contains some bytes. This is the data of interest; let's use tshark to harvest this data by running the tshark –r [path to the file] as follows:

Let's only print the leftover data, using the usb.capdata field:

We can see that we have only one or...