Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical Memory Forensics

You're reading from   Practical Memory Forensics Jumpstart effective forensic analysis of volatile memory

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781801070331
Length 304 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Oleg Skulkin Oleg Skulkin
Author Profile Icon Oleg Skulkin
Oleg Skulkin
Svetlana Ostrovskaya Svetlana Ostrovskaya
Author Profile Icon Svetlana Ostrovskaya
Svetlana Ostrovskaya
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Section 1: Basics of Memory Forensics
2. Chapter 1: Why Memory Forensics? FREE CHAPTER 3. Chapter 2: Acquisition Process 4. Section 2: Windows Forensic Analysis
5. Chapter 3: Windows Memory Acquisition 6. Chapter 4: Reconstructing User Activity with Windows Memory Forensics 7. Chapter 5: Malware Detection and Analysis with Windows Memory Forensics 8. Chapter 6: Alternative Sources of Volatile Memory 9. Section 3: Linux Forensic Analysis
10. Chapter 7: Linux Memory Acquisition 11. Chapter 8: User Activity Reconstruction 12. Chapter 9: Malicious Activity Detection 13. Section 4: macOS Forensic Analysis
14. Chapter 10: MacOS Memory Acquisition 15. Chapter 11: Malware Detection and Analysis with macOS Memory Forensics 16. Other Books You May Enjoy

Learning about the investigation goals and methodology

The basis of any forensic investigation is goal setting. Goals determine evidence to look for, methods to use, and tools we need. The right approach to goal setting helps to achieve the desired result quickly and efficiently. Remember the famous "divide et impera" principle? Despite its origins and primary purpose, this principle is great for achieving any goals, the main thing is to understand what to divide and how to use it. As part of the investigation goal setting, this principle can be used to break down the primary goal into smaller and simpler ones. Thus, by dividing our goals into components, we get a set of specific actions, the result of which will be the pieces of the puzzle and all we will have to do is to put them together.

Let's start with the more general goals. If we receive for examination the device involved in the incident, there is a high probability that it is either one of the following:

  • The alleged victim's device
  • The suspect's device

Let's look at what both are in the next sections.

The victim's device

Consider a situation in which the victim's device is under investigation. The main goal in this case is to answer the question, What happened? One way is to break this question down into its components:

  1. How did an attacker gain access to the system?
  2. What tools were launched?
  3. Did the attacker get persistence?
  4. Was there a lateral movement?
  5. What actions on the objective were performed?

Now let's do the same thing with the question, How did the attacker gain access to the system?:

  1. Are there any traces of potentially malicious files/links having been opened?
  2. Are there any remote connection services running?
  3. Are there any traces of suspicious connections?
  4. Are there any traces of removable devices being connected?

Let's ask questions about malicious files too:

  1. Are there any traces of suspicious files saved?
  2. Are there any traces of suspicious links opened?
  3. Are there any traces of suspicious files opened?

Finding answers to these questions requires not only knowledge of the digital artifacts and their sources but also the attacker's tactics, techniques, and procedures, so such assessments must also be cyber threat intelligence-driven.

This is the level to which each upper-level question should be broken down. As a result, we have a final list of questions that will allow us to piece together a picture of the incident and answer the first question of What happened? in detail.

The suspect's device

A similar method can be used to investigate the device from which the attacks are suspected to have originated. In this case, questions would be posed based on what the owner of the device is suspected of. For example, if they are suspected of being a malware developer, our questions would be related to the presence of development tools, traces of source code, sales of malware, and so on.

So, we have discussed how memory forensics can help our investigation and what methodology we can apply to do so. However, we cannot remain silent and overlook the weaknesses and possible risks. Let's discuss the challenges of memory forensics.

You have been reading a chapter from
Practical Memory Forensics
Published in: Mar 2022
Publisher: Packt
ISBN-13: 9781801070331
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image