Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Cloud Forensics Demystified

You're reading from  Cloud Forensics Demystified

Product type Book
Published in Feb 2024
Publisher Packt
ISBN-13 9781800564411
Pages 384 pages
Edition 1st Edition
Languages
Concepts
Authors (2):
Ganesh Ramakrishnan Ganesh Ramakrishnan
Profile icon Ganesh Ramakrishnan
Mansoor Haqanee Mansoor Haqanee
Profile icon Mansoor Haqanee
View More author details

Table of Contents (18) Chapters

Preface 1. Part 1: Cloud Fundamentals
2. Chapter 1: Introduction to the Cloud 3. Chapter 2: Trends in Cyber and Privacy Laws and Their Impact on DFIR 4. Chapter 3: Exploring the Major Cloud Providers 5. Chapter 4: DFIR Investigations – Logs in AWS 6. Part 2: Forensic Readiness: Tools, Techniques, and Preparation for Cloud Forensics
7. Chapter 5: DFIR Investigations – Logs in Azure 8. Chapter 6: DFIR Investigations – Logs in GCP 9. Chapter 7: Cloud Productivity Suites 10. Part 3: Cloud Forensic Analysis – Responding to an Incident in the Cloud
11. Chapter 8: The Digital Forensics and Incident Response Process 12. Chapter 9: Common Attack Vectors and TTPs 13. Chapter 10: Cloud Evidence Acquisition 14. Chapter 11: Analyzing Compromised Containers 15. Chapter 12: Analyzing Compromised Cloud Productivity Suites 16. Index 17. Other Books You May Enjoy

Forensic acquisition of AWS instance

Let us jump right into the details of collecting forensic artifacts in a secure and forensically sound manner. We will assume that an organization received alerts for ransomware deployment on an Elastic Compute Cloud (EC2) instance. As a result, this instance was stopped. Forensic investigators would need to pull forensic artifacts out of the EC2 instance safely.

Any disks associated with an EC2 instance are referred to as volumes by AWS. To collect artifacts, investigators have to follow a specific sequence of steps. Firstly, investigators must record the infected instance’s instance ID (unique identifier).

In this case, the infected instance name is CF2 and it has the instance ID i-00229ce2dd123a2e6.

Step 1 – creating EC2 volume snapshots

We will refer to these EC2 instances by their instance ID for the following steps:

  1. Investigators must note storage volumes associated with i-00229ce2dd123a2e6 (CF2) and the volume...
lock icon The rest of the chapter is locked
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 $15.99/month. Cancel anytime}