Order of Volatility and Evidence Acquisition
Understand why volatile data (RAM, running processes) must be captured before disk images, and how to use write blockers and imaging tools correctly.
Order of Volatility and Evidence Acquisition is a free Cloud & IT Cert Prep lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Cloud & IT Cert Prep learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Digital Forensics Fundamentals
Digital forensics is the application of scientific methods to collect, preserve, analyze, and present digital evidence in a legally admissible manner. Forensic investigators reconstruct attack timelines, identify the root cause of incidents, and recover deleted or hidden data. The field operates under strict procedural requirements because evidence that is mishandled — even technically — may be inadmissible in legal proceedings. Forensics bridges the technical and legal worlds.
Order of Volatility
The order of volatility defines the sequence in which digital evidence should be collected, from most volatile (disappears soonest) to least volatile (persists longer). Forensic investigators always collect the most volatile data first because it will be lost when the system is powered off or rebooted. Collecting in the wrong order destroys evidence that could have been captured. The RFC 3227 standard provides a widely adopted volatility ordering for forensic procedures.
# Order of volatility (most -> least volatile)
# 1. CPU registers and cache
# 2. Routing tables, ARP cache, process table, kernel stats
# 3. Memory (RAM) — volatile, lost on power-off
# 4. Temporary filesystem / swap space
# 5. Data on local disk
# 6. Remote logging data / SIEM
# 7. Physical configuration / network topology
# 8. Archival media (backups, tapes)
# ALWAYS capture items at the top before the bottomMemory Acquisition
Memory acquisition (RAM capture) is one of the most valuable and time-sensitive forensic actions. RAM contains: running processes and their arguments, decrypted versions of encrypted files currently in use, network connection tables, user credentials cached by the OS, encryption keys held in memory, and fileless malware that exists only in RAM. Memory must be acquired while the system is powered on — a reboot or shutdown destroys this evidence entirely. Tools include Magnet RAM Capture, WinPmem, and LiME (for Linux).
# Acquire Windows memory dump with WinPmem
winpmem_mini.exe --output memory.raw --format raw
# Verify integrity with hash
Get-FileHash memory.raw -Algorithm SHA256
# Acquire Linux memory with LiME (kernel module)
insmod lime.ko 'path=/tmp/memory.lime format=lime'
sha256sum /tmp/memory.lime
# Analyze with Volatility framework
vol.py -f memory.raw --profile=Win10x64_19041 pslistDisk Imaging with Write Blockers
Disk imaging creates a bit-for-bit forensic copy of a storage device, including all data, deleted files, unallocated space, and filesystem metadata. To prevent accidental modification of the original evidence, a write blocker is connected between the evidence disk and the forensic workstation — it passes read commands but blocks any write commands. This ensures the original evidence is not modified during acquisition, preserving its integrity for legal proceedings.
# Create forensic disk image with dd (Linux)
# --if: input (evidence disk, write-blocked)
# --of: output (forensic image file)
# --bs: block size for efficiency
dd if=/dev/sdb of=/forensics/evidence_disk.img bs=4M status=progress
# Compute hash of BOTH original and image (must match)
md5sum /dev/sdb
md5sum /forensics/evidence_disk.img
# If hashes match, the image is a faithful copy
# FTK Imager is the industry standard GUI tool for disk imagingHashing for Integrity Verification
Cryptographic hashing is fundamental to forensic evidence integrity. Every piece of evidence must be hashed at collection using SHA-256 (or MD5 for legacy compatibility). The hash is recorded in the chain of custody documentation. Any time the evidence is accessed or transferred, the hash is recomputed — if the hash matches the original, the evidence has not been modified. Courts require this integrity proof to accept digital evidence. A hash mismatch means the evidence has been altered and may be inadmissible.
# Hash commands for evidence verification
# Windows PowerShell
Get-FileHash C:\evidence\disk.img -Algorithm SHA256
# Output: SHA256 hash value
# Linux/macOS
sha256sum /forensics/evidence_disk.img
md5sum /forensics/evidence_disk.img
# Document in chain of custody:
# Evidence: disk.img
# SHA-256: a1b2c3d4e5f6...
# Collected by: [Name] at [Time] on [Date]
# Matches original device hash: YESLive Forensics vs Dead Forensics
Live (online) forensics collects evidence from a running system — capturing volatile data before shutdown. This is necessary when volatile memory analysis is required, when the system cannot be taken offline, or when fileless malware would not be visible on disk. Dead (offline) forensics analyzes powered-off systems using disk images, making it safer and more controlled. Modern incidents often require a combination: capture volatile data live, then power off and image the disk for deeper analysis.
Forensic Triage in Incident Response
During an active incident with multiple affected systems, investigators must perform triage — prioritizing which systems to examine first. Triage criteria include: systems with highest access (domain controllers, databases), systems most likely to contain attacker persistence, systems with the most recent malicious activity, and systems with the highest business impact. Triage-level collection uses EDR telemetry and targeted artifact collection rather than full disk imaging, enabling rapid analysis of many systems simultaneously.
Network Packet Capture Acquisition
Packet capture (PCAP)** files record all network traffic at the packet level. During an incident, PCAP evidence can reveal: credentials transmitted in cleartext, commands issued to compromised systems via C2 channels, data being exfiltrated (large outbound transfers), lateral movement (internal connection patterns), and malware download sources. PCAP is acquired using Wireshark, tcpdump, or network taps. PCAP acquisition requires authorization as it captures all traffic on a segment, potentially including privileged communications.
# Capture network traffic with tcpdump
# Capture all traffic on eth0, save to file
tcpdump -i eth0 -w /forensics/capture.pcap
# Capture traffic to/from specific IP (attacker)
tcpdump -i eth0 host 198.51.100.10 -w /forensics/attacker_traffic.pcap
# Capture traffic on port 443 (HTTPS)
tcpdump -i eth0 port 443 -w /forensics/tls_traffic.pcap
# Hash the capture file for integrity
sha256sum /forensics/capture.pcapCloud Forensics Considerations
Cloud environments present unique forensic challenges. Physical access to underlying hardware is unavailable — cloud providers control the hypervisor layer. Virtual machine disk images can be snapshotted through cloud APIs. Log data (CloudTrail, Azure Monitor) is the primary evidence source for cloud incidents. Memory acquisition is limited to techniques supported by the cloud provider or VM introspection. Evidence jurisdiction may be complex if cloud servers are in different countries than the incident occurred. Understanding these constraints is essential for cloud incident investigations.
# AWS EC2 forensics: create a snapshot of a compromised instance
# 1. Note the instance ID and volume ID
aws ec2 describe-volumes --filters Name=attachment.instance-id,Values=i-0abc12345
# 2. Create snapshot (preserves the disk state at this point in time)
aws ec2 create-snapshot \
--volume-id vol-0example \
--description 'Forensic snapshot: incident IR-2026-042'
# 3. Attach the snapshot to a forensic workstation for analysisForensic Tools Overview
Forensic investigators use specialized tools designed to handle evidence correctly. Autopsy (open source) and FTK (Forensic Toolkit) (commercial) analyze disk images and extract artifacts. Volatility analyzes memory dumps to extract processes, network connections, and malware artifacts. Magnet AXIOM handles both digital and mobile forensics. Wireshark analyzes PCAP files. X-Ways Forensics is a lightweight but powerful commercial toolkit. Investigators must use validated tools to ensure evidence integrity.
Forensic Readiness
Forensic readiness means an organization has taken steps before an incident to ensure digital evidence can be collected efficiently and is legally admissible. Components include: comprehensive logging configured on all critical systems, log retention long enough to support investigations (90-365 days), documented evidence handling procedures, trained first responders who know not to disturb evidence, forensic tools pre-positioned or available on short notice, and legal authorization reviewed in advance (e.g., employee consent to monitoring policies).
Quick Check
Test your understanding of CompTIA Security+ (SY0-701) concepts from this lesson.
Lesson Recap
In this lesson you learned: the order of volatility requires capturing RAM and running processes first because they are lost when the system is powered off, write blockers prevent any modification to original evidence during disk imaging, and SHA-256 hashing at collection and verification ensures evidence integrity for legal admissibility. Next up we explore chain of custody and legal admissibility.
Frequently asked questions
Is the “Order of Volatility and Evidence Acquisition” lesson free?
Yes — the full text of “Order of Volatility and Evidence Acquisition” is free to read here on the web, and the Cloud & IT Cert Prep course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Cloud & IT Cert Prep course, upgrade to CoddyKit PRO.
What will I learn in “Order of Volatility and Evidence Acquisition”?
Understand why volatile data (RAM, running processes) must be captured before disk images, and how to use write blockers and imaging tools correctly. You practise Cloud & IT Cert Prep with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Cloud & IT Cert Prep?
No prior experience is required. Cloud & IT Cert Prep on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Order of Volatility and Evidence Acquisition” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Cloud & IT Cert Prep lesson?
Yes. Every Cloud & IT Cert Prep lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Order of Volatility and Evidence Acquisition
- Chain of Custody and Legal Admissibility
- Windows Forensic Artifacts: Registry, Event Logs, and Prefetch
- Network and Memory Forensics