Repository navigation
Volatility 3 Memory Forensics Guide
Reference index and audit status: Reviewed cheat sheets and references.
Important
Reviewed October 31, 2026 (reference corrections, not a live dump validation). Prefer the upstream Volatility 3 documentation and official source. Exact plugin names/flags and symbol requirements can vary by release and OS build; use vol --help and vol <plugin> --help for your version. Collect memory only with authorization and preserve hash, acquisition time, tool version, custody, and original bytes. Unknown Docker images are not official merely because they contain Volatility.
Volatility 3 memory forensics cheat sheet - covering the full analysis workflow for Windows and Linux memory dumps captured during incident response.
Covers: Volatility 3 plugin taxonomy (windows.pslist, windows.cmdline, windows.netscan, windows.malfind, windows.dlllist), process analysis, network connection extraction, injected code detection, registry hive extraction, and artifact recovery from memory.
Enable IR analysts to extract actionable intelligence from memory dumps: running processes, network connections at time of capture, injected shellcode, credential material, and attacker tooling loaded in memory.
- Analyzing a memory dump captured from a compromised system
- Hunting for in-memory malware (fileless malware, process injection)
- Extracting network connections and process trees for timeline reconstruction
- Recovering attacker tools or credential material from RAM
Volatility is the industry-standard open-source framework for memory forensics. It enables analysts to extract digital artifacts from volatile memory (RAM) dumps, revealing evidence that may not exist on disk-running processes, network connections, injected code, encryption keys, and more.
This guide covers Volatility 3 installation, memory acquisition, and comprehensive analysis techniques for Windows memory forensics.
Memory analysis can reveal artifacts not always recoverable from disk; capture timing, memory acquisition quality, paging, encryption and symbol compatibility limit what can be recovered:
| Artifact | Disk Forensics | Memory Forensics |
|---|---|---|
| Running processes | โ | โ Full details including hidden |
| Network connections | Limited (logs) | โ Active at capture time |
| Encryption keys | Sometimes | Potentially recoverable, not guaranteed or necessarily plaintext |
| Injected code/shellcode | โ | โ Detectable |
| Malware in memory-only | โ | โ Capturable |
| Command history | Limited | โ Console buffers |
| Clipboard contents | โ | โ Recoverable |
| Decrypted data | Sometimes | May be present in RAM depending on process/OS and timing |
| Deleted/hidden processes | โ | โ Via pool scanning |
| Component | Minimum | Recommended |
|---|---|---|
| OS | Windows/Linux/macOS | Linux (Ubuntu 22.04) |
| Python | Check installed Volatility release requirements | Use a currently supported Python and isolated environment |
| RAM | 8 GB | 16 GB+ |
| Storage | 2x size of memory dump | SSD recommended |
- A Python version supported by the installed Volatility 3 release; current versions may reject old Python runtimes
- pip (Python package manager)
- Git (for installation from source)
# Install Volatility 3
# Isolated installation; avoid modifying system-managed Python
python3 -m venv .venv-volatility
. .venv-volatility/bin/activate
python -m pip install volatility3
# Verify installation (pip installs the binary as 'vol', not 'vol3')
vol --help# Clone the repository
git clone https://github.com/volatilityfoundation/volatility3.git
cd volatility3
# Install dependencies
python3 -m venv .venv && . .venv/bin/activate
python -m pip install -r requirements.txt
# Run directly
python3 vol.py --helpWarning
Older examples referred to sk4la/volatility3 as an official image. That claim was not established and has been removed. Build a reviewed image from upstream source or choose a provenance-verified package; do not mount confidential memory dumps into unknown or outdated third-party containers. Prefer an isolated, offline forensic VM when practicable.
Volatility 3 may require matching symbols for specific layers/plugins and can acquire some symbols automatically when network access is permitted. Offline analysis needs a previously verified, compatible symbol cache:
# Create symbols directory
mkdir -p ~/.local/lib/volatility3/symbols
# Download Windows symbols (automatic on first run)
# Or manually from: https://downloads.volatilityfoundation.org/volatility3/symbols/
# For offline environments, download and extract:
cd ~/.local/lib/volatility3/symbols
wget https://downloads.volatilityfoundation.org/volatility3/symbols/windows.zip
unzip windows.zip# List available plugins
vol --help | grep windows
# Or from source
python3 vol.py --help | grep windowsBefore analysis, you need a memory dump. Several tools can capture RAM from live systems.
Important
Preserve integrity as you acquire. Live acquisition itself perturbs RAM, so
capture memory first (order of volatility) and with the smallest footprint
tool available. Immediately hash the resulting image
(sha256sum image.raw > image.raw.sha256) and record it in your notes โ this
establishes integrity for chain of custody. See the section's evidence-handling
guidance in Digital-Forensics/README.md.
Free, portable, and simple:
:: Run as Administrator
DumpIt.exeOutput: Creates a raw memory dump in the current directory.
:: Capture to raw format
winpmem_mini_x64.exe output.raw
:: Capture to AFF4 format (compressed)
winpmem_mini_x64.exe -o output.aff4- Download from AccessData (free)
- File โ Capture Memory
- Select destination path
- Include pagefile (optional)
Free GUI tool from Magnet Forensics:
- Run as Administrator
- Select output location
- Click "Capture Memory"
# Install dependencies
sudo apt install -y build-essential linux-headers-$(uname -r)
# Clone and build LiME
git clone https://github.com/504ensicsLabs/LiME.git
cd LiME/src
make
# Capture memory (as root)
sudo insmod lime-$(uname -r).ko "path=/tmp/memory.lime format=lime"# Download AVML
wget https://github.com/microsoft/avml/releases/latest/download/avml
# Capture memory
sudo ./avml memory.lime| Hypervisor | Method |
|---|---|
| VMware | Suspend VM โ .vmem file in VM directory |
| VirtualBox | VBoxManage debugvm <VM> dumpguestcore --filename dump.elf |
| Hyper-V | Checkpoint โ Export โ .bin file |
| KVM/QEMU | virsh dump <domain> memory.dump --memory-only |
| Format | Extension | Tools | Notes |
|---|---|---|---|
| Raw |
.raw, .mem, .bin
|
Most tools | Uncompressed, largest |
| LiME | .lime |
LiME | Linux format with metadata |
| AFF4 | .aff4 |
WinPMEM | Compressed, with metadata |
| Crash Dump | .dmp |
Windows | Kernel/complete dumps |
| VMware | .vmem |
VMware | Suspended VM state |
| ELF Core |
.elf, .core
|
VirtualBox, QEMU | Standard format |
| Hibernation | hiberfil.sys |
Windows | Compressed RAM snapshot |
# Standard syntax
vol -f <MEMORY_DUMP> <PLUGIN> [OPTIONS] # installed in venv; from source use python3 vol.py
# With output file
python3 vol.py -f memory.dmp windows.pslist > processes.txt
# JSON output for scripting
python3 vol.py -f memory.dmp -r json windows.pslist > processes.json
# Specify symbol path
python3 vol.py -s /path/to/symbols -f memory.dmp windows.pslist| Option | Description |
|---|---|
-f <file> |
Path to memory dump file |
-r <format> |
Output format: pretty, json, csv |
-o <dir> |
Output directory for dumped files |
-s <path> |
Additional symbol path |
-v |
Verbose output |
-p |
Parallelism (number of threads) |
--help |
Show help for plugin |
# General help
python3 vol.py --help
# Plugin-specific help
python3 vol.py windows.pslist --helpProcess analysis is typically the starting point for any memory investigation.
Lists processes from the EPROCESS doubly-linked list (what the OS sees):
python3 vol.py -f memory.dmp windows.pslistOutput columns:
| Column | Description |
|---|---|
| PID | Process ID |
| PPID | Parent Process ID |
| ImageFileName | Process name |
| Offset | Memory offset of EPROCESS |
| Threads | Number of threads |
| Handles | Number of handles |
| SessionId | User session (0 = system) |
| Wow64 | 32-bit process on 64-bit OS |
| CreateTime | Process start time |
| ExitTime | Process end time (if exited) |
What to look for:
- Processes with
ExitTimeset (terminated but still in memory) - Unusual parent/child relationships
- Processes with very few threads or handles
- Misspelled system process names (
scvhost.exevssvchost.exe)
Displays processes in a tree structure showing parent/child relationships:
python3 vol.py -f memory.dmp windows.pstreeSuspicious patterns:
-
WINWORD.EXEโcmd.exeorpowershell.exe(macro execution) -
explorer.exeโ suspicious child processes - System processes with wrong parents
-
services.exeshould be a child ofwininit.exe -
svchost.exeshould be a child ofservices.exe
Normal Windows process tree:
System (4)
โโโ smss.exe
โโโ csrss.exe (Session 0)
โโโ wininit.exe
โ โโโ services.exe
โ โ โโโ svchost.exe (multiple)
โ โโโ lsass.exe
โโโ csrss.exe (Session 1)
โโโ winlogon.exe
โโโ explorer.exe
Scans for EPROCESS structures using pool tag scanning. Finds hidden/unlinked processes:
python3 vol.py -f memory.dmp windows.psscanWhy this matters:
- Rootkits unlink processes from the active process list
-
psscanfinds these by scanning raw memory for process structures - Compare output with
pslist-differences indicate hidden processes
Find hidden processes:
# Compare pslist vs psscan
python3 vol.py -f memory.dmp windows.pslist > pslist.txt
python3 vol.py -f memory.dmp windows.psscan > psscan.txt
diff pslist.txt psscan.txtShows command-line arguments for each process:
python3 vol.py -f memory.dmp windows.cmdlineSuspicious indicators:
- Encoded PowerShell (
-enc,-e,-encodedcommand) - Commands with Base64 strings
- Processes running from
\Temp\,\AppData\,\Downloads\ - Unusual arguments for system processes
Displays environment variables for processes:
# All processes
python3 vol.py -f memory.dmp windows.envars
# Specific process
python3 vol.py -f memory.dmp windows.envars --pid 1234Look for:
- Unusual
PATHmodifications - Suspicious environment variables set by malware
- User context (
USERNAME,USERPROFILE)
Network artifacts reveal active connections, listening ports, and potential C2 communication.
Scans for network connection structures (TCP/UDP endpoints):
python3 vol.py -f memory.dmp windows.netscanOutput columns:
| Column | Description |
|---|---|
| Offset | Memory offset |
| Proto | Protocol (TCPv4, TCPv6, UDPv4, UDPv6) |
| LocalAddr | Local IP and port |
| ForeignAddr | Remote IP and port |
| State | Connection state |
| PID | Associated process ID |
| Owner | Process name |
| Created | Connection creation time |
Connection states:
| State | Meaning |
|---|---|
| LISTENING | Waiting for incoming connections |
| ESTABLISHED | Active connection |
| CLOSE_WAIT | Remote side closed |
| TIME_WAIT | Connection closing |
| SYN_SENT | Initiating connection |
Suspicious patterns:
- Connections from non-browser processes to port 80/443
- Connections to known-bad IPs
- Unusual listening ports
- System processes with external connections
Similar to the netstat command output:
python3 vol.py -f memory.dmp windows.netstat# Find process with suspicious connection
python3 vol.py -f memory.dmp windows.netscan | grep "192.168.1.100"
# Get full details on that process
python3 vol.py -f memory.dmp windows.pslist --pid <PID>
python3 vol.py -f memory.dmp windows.cmdline --pid <PID>These plugins help identify malicious code injection and suspicious memory regions.
Scans process memory for signs of code injection:
python3 vol.py -f memory.dmp windows.malfindDetection criteria:
- Memory regions with
PAGE_EXECUTE_READWRITEprotection - Executable code in regions not backed by files
- Common shellcode patterns (e.g.,
MZheaders)
Output includes:
- Process name and PID
- Memory region address and protection
- Hexdump of suspicious region
- Disassembly of code
Dump injected regions:
python3 vol.py -f memory.dmp -o /output/dir windows.malfind --dumpCommon false positives:
- .NET JIT compiled code
- Some security products
- Legitimate packers
Lists Virtual Address Descriptor (VAD) information for memory regions:
python3 vol.py -f memory.dmp windows.vadinfo --pid 1234Memory protection flags:
| Flag | Description | Suspicious? |
|---|---|---|
| PAGE_EXECUTE_READWRITE | RWX | Yes - common for injection |
| PAGE_EXECUTE_WRITECOPY | Execute + Copy-on-write | Potentially |
| PAGE_EXECUTE_READ | Normal executable | Usually OK |
| PAGE_READWRITE | Data section | Normal |
Compares loaded modules across three different lists:
python3 vol.py -f memory.dmp windows.ldrmodules --pid 1234The three lists:
- InLoadOrderList
- InInitOrderList
- InMemOrderList
Interpretation:
- Legitimate DLLs appear in all three lists
-
Falseentries may indicate:- Unlinked/hidden modules
- Manually loaded DLLs
- Injection artifacts
Detects process hollowing (a technique where legitimate process memory is replaced):
python3 vol.py -f memory.dmp windows.hollowprocessesLists kernel callbacks that malware might use for persistence:
python3 vol.py -f memory.dmp windows.callbacksLists DLLs loaded by a process:
# All processes
python3 vol.py -f memory.dmp windows.dlllist
# Specific process
python3 vol.py -f memory.dmp windows.dlllist --pid 1234Suspicious indicators:
- DLLs loaded from unusual paths (
\Temp\,\Users\) - Misspelled DLL names
- DLLs with no file path (memory-only)
Lists kernel modules (drivers):
python3 vol.py -f memory.dmp windows.modulesLook for:
- Unsigned drivers
- Drivers loaded from unusual locations
- Known malicious driver names
Pool scanner for kernel modules (finds hidden drivers):
python3 vol.py -f memory.dmp windows.modscan# Dump all DLLs for a process
python3 vol.py -f memory.dmp -o /output/dir windows.dlllist --pid 1234 --dumpExtracts password hashes from the SAM database:
python3 vol.py -f memory.dmp windows.hashdumpOutput format:
Administrator:500:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0:::
Hash positions:
- LM hash (first 32 chars, often empty)
- NTLM hash (second 32 chars)
Extracts LSA secrets:
python3 vol.py -f memory.dmp windows.lsadumpContains:
- Service account passwords
- Cached domain credentials
- VPN/dial-up passwords
Extracts cached domain credentials:
python3 vol.py -f memory.dmp windows.cachedumpFor more comprehensive credential extraction, dump LSASS and analyze with Mimikatz:
# Find LSASS PID
python3 vol.py -f memory.dmp windows.pslist | grep lsass
# Dump LSASS memory
python3 vol.py -f memory.dmp -o /output/dir windows.memmap --pid <LSASS_PID> --dumpScans for FILE_OBJECT structures:
python3 vol.py -f memory.dmp windows.filescanFilter for specific files:
python3 vol.py -f memory.dmp windows.filescan | grep -i "malware"
python3 vol.py -f memory.dmp windows.filescan | grep -i "\.exe"Dumps files from memory:
# Dump by physical offset
python3 vol.py -f memory.dmp -o /output/dir windows.dumpfiles --physaddr 0x12345678
# Dump by virtual address
python3 vol.py -f memory.dmp -o /output/dir windows.dumpfiles --virtaddr 0x12345678Lists handles opened by processes:
# All handles for a process
python3 vol.py -f memory.dmp windows.handles --pid 1234
# Filter by handle type
python3 vol.py -f memory.dmp windows.handles --pid 1234 | grep "File"Handle types of interest:
- File handles (accessed files)
- Key handles (registry access)
- Process/Thread handles (injection indicators)
- Mutant handles (malware mutexes)
Lists registry hives loaded in memory:
python3 vol.py -f memory.dmp windows.registry.hivelistPrints registry keys and values:
# Print specific key
python3 vol.py -f memory.dmp windows.registry.printkey --key "Software\Microsoft\Windows\CurrentVersion\Run"
# With specific hive offset
python3 vol.py -f memory.dmp windows.registry.printkey --offset 0x12345678 --key "Software"Important keys for investigation:
| Key | Purpose |
|---|---|
...\CurrentVersion\Run |
Startup programs |
...\CurrentVersion\RunOnce |
One-time startup |
...\Services |
Service configurations |
...\Explorer\RecentDocs |
Recent documents |
...\TypedPaths |
Explorer address bar history |
Extracts UserAssist data (program execution history):
python3 vol.py -f memory.dmp windows.registry.userassistCreates a timeline of system events:
python3 vol.py -f memory.dmp timeliner.TimelinerOutput includes:
- Process creation/exit times
- Network connection times
- File access times
- Registry modification times
# Generate timeline in CSV format
python3 vol.py -f memory.dmp -r csv timeliner.Timeliner > timeline.csv
# Sort by time
sort -t',' -k1 timeline.csv > timeline_sorted.csvDumps the full memory space of a process:
python3 vol.py -f memory.dmp -o /output/dir windows.memmap --pid 1234 --dumpDumps the executable image of a process:
python3 vol.py -f memory.dmp -o /output/dir windows.pslist --pid 1234 --dump# Get VAD information first
python3 vol.py -f memory.dmp windows.vadinfo --pid 1234
# Dump specific VAD region
python3 vol.py -f memory.dmp -o /output/dir windows.vadyarascan --pid 1234 --yara-rules "rule test { strings: $a = \"malware\" condition: $a }"Scans process memory with YARA rules:
# Scan with YARA rule file
python3 vol.py -f memory.dmp windows.vadyarascan --yara-file /path/to/rules.yar
# Scan specific process
python3 vol.py -f memory.dmp windows.vadyarascan --pid 1234 --yara-file /path/to/rules.yarScans all memory (kernel + user space):
python3 vol.py -f memory.dmp yarascan.YaraScan --yara-file /path/to/rules.yarCreate malware_indicators.yar:
rule Suspicious_PowerShell {
meta:
description = "Detects encoded PowerShell commands"
strings:
$enc1 = "-enc" ascii nocase
$enc2 = "-encodedcommand" ascii nocase
$enc3 = "FromBase64String" ascii nocase
$iex = "IEX" ascii nocase
condition:
any of them
}
rule Mimikatz_Strings {
meta:
description = "Detects Mimikatz in memory"
strings:
$s1 = "mimikatz" ascii nocase
$s2 = "gentilkiwi" ascii
$s3 = "sekurlsa::" ascii
$s4 = "kerberos::" ascii
condition:
2 of them
}
rule Cobalt_Strike_Beacon {
meta:
description = "Detects Cobalt Strike beacon"
strings:
$s1 = "%s (admin)" ascii
$s2 = "beacon.dll" ascii
$s3 = "ReflectiveLoader" ascii
$pipe = "\\\\.\\pipe\\msagent_" ascii
condition:
2 of them
}#!/bin/bash
DUMP="memory.dmp"
OUTPUT="investigation_$(date +%Y%m%d)"
mkdir -p $OUTPUT
echo "[*] Step 1: Process listing"
python3 vol.py -f $DUMP windows.pstree > $OUTPUT/pstree.txt
echo "[*] Step 2: Finding hidden processes"
python3 vol.py -f $DUMP windows.pslist > $OUTPUT/pslist.txt
python3 vol.py -f $DUMP windows.psscan > $OUTPUT/psscan.txt
echo "[*] Step 3: Command lines"
python3 vol.py -f $DUMP windows.cmdline > $OUTPUT/cmdline.txt
echo "[*] Step 4: Network connections"
python3 vol.py -f $DUMP windows.netscan > $OUTPUT/netscan.txt
echo "[*] Step 5: Injection detection"
python3 vol.py -f $DUMP windows.malfind > $OUTPUT/malfind.txt
echo "[*] Analysis complete. Review files in $OUTPUT/"# 1. Identify suspicious processes
python3 vol.py -f memory.dmp windows.pstree | grep -E "(cmd|powershell|wscript|cscript|mshta|rundll32)"
# 2. Check for code injection
python3 vol.py -f memory.dmp windows.malfind
# 3. Scan with YARA
python3 vol.py -f memory.dmp windows.vadyarascan --yara-file malware_rules.yar
# 4. Check network for C2
python3 vol.py -f memory.dmp windows.netscan | grep ESTABLISHED
# 5. Dump suspicious process
python3 vol.py -f memory.dmp -o ./dump windows.memmap --pid <SUSPICIOUS_PID> --dump# 1. Check for LSASS access
python3 vol.py -f memory.dmp windows.handles | grep -i lsass
# 2. Look for credential tools
python3 vol.py -f memory.dmp windows.cmdline | grep -iE "(mimikatz|procdump|sekurlsa)"
# 3. Extract cached credentials
python3 vol.py -f memory.dmp windows.hashdump
python3 vol.py -f memory.dmp windows.cachedump
python3 vol.py -f memory.dmp windows.lsadump
# 4. Dump LSASS for offline analysis
LSASS_PID=$(python3 vol.py -f memory.dmp windows.pslist | grep lsass | awk '{print $2}')
python3 vol.py -f memory.dmp -o ./dump windows.memmap --pid $LSASS_PID --dump# 1. Check for remote connections (RDP, SMB, WinRM)
python3 vol.py -f memory.dmp windows.netscan | grep -E ":(3389|445|5985|5986)"
# 2. Look for PsExec or similar tools
python3 vol.py -f memory.dmp windows.pslist | grep -iE "(psexec|paexec|remcom|winexe)"
# 3. Check scheduled tasks
python3 vol.py -f memory.dmp windows.filescan | grep -i "tasks"
# 4. Review services
python3 vol.py -f memory.dmp windows.svcscan | grep -v "Microsoft"When you have baseline and compromised dumps:
# Extract process lists
python3 vol.py -f baseline.dmp windows.pslist > baseline_ps.txt
python3 vol.py -f compromised.dmp windows.pslist > compromised_ps.txt
# Compare
diff baseline_ps.txt compromised_ps.txtCreate Python scripts using Volatility as a library:
#!/usr/bin/env python3
import volatility3
from volatility3 import framework
from volatility3.framework import contexts, automagic
from volatility3.plugins.windows import pslist
# Initialize context
ctx = contexts.Context()
# Configure and run
# (Simplified example - full implementation requires more setup)Process multiple dumps:
#!/bin/bash
for dump in /cases/*.dmp; do
echo "Processing: $dump"
name=$(basename $dump .dmp)
mkdir -p results/$name
python3 vol.py -f $dump windows.pslist > results/$name/pslist.txt
python3 vol.py -f $dump windows.netscan > results/$name/netscan.txt
python3 vol.py -f $dump windows.malfind > results/$name/malfind.txt
doneProblem: Volatility cannot identify the OS profile.
Solutions:
# Check if dump is valid
file memory.dmp
# Try windows.info to identify the OS
python3 vol.py -f memory.dmp windows.info
# Specify symbol path
python3 vol.py -s /path/to/symbols -f memory.dmp windows.pslist
# Download symbols
python3 vol.py -f memory.dmp windows.pslist
# (Symbols download automatically on first run)Problem: Volatility cannot read the memory format.
Solutions:
# Identify dump format
file memory.dmp
# For hibernation files
python3 vol.py -f hiberfil.sys windows.pslist
# For crash dumps
python3 vol.py -f MEMORY.DMP windows.pslist
# Convert formats if needed
volatility3 -f input.vmem layerwriter.LayerWriter --output rawOptimizations:
# Use parallel processing
python3 vol.py -p 4 -f memory.dmp windows.psscan
# Use SSD for output
python3 vol.py -f memory.dmp -o /fast/ssd/output windows.malfind --dump
# Filter before dumping
python3 vol.py -f memory.dmp windows.pslist --pid 1234# List available plugins
python3 vol.py --help
# Check plugin path
python3 vol.py --plugin-dirs /path/to/plugins -f memory.dmp <plugin>| Category | Plugins |
|---|---|
| Process |
pslist, pstree, psscan, cmdline, envars
|
| Network |
netscan, netstat
|
| Malware |
malfind, ldrmodules, hollowprocesses
|
| DLLs |
dlllist, modules, modscan
|
| Credentials |
hashdump, lsadump, cachedump
|
| Files |
filescan, dumpfiles, handles
|
| Registry |
hivelist, printkey, userassist
|
| Memory |
memmap, vadinfo, vadyarascan
|
# Basic analysis
python3 vol.py -f memory.dmp windows.pslist
python3 vol.py -f memory.dmp windows.pstree
python3 vol.py -f memory.dmp windows.netscan
# Targeted analysis
python3 vol.py -f memory.dmp windows.cmdline --pid 1234
python3 vol.py -f memory.dmp windows.dlllist --pid 1234
python3 vol.py -f memory.dmp windows.handles --pid 1234
# Dumping
python3 vol.py -f memory.dmp -o /output windows.malfind --dump
python3 vol.py -f memory.dmp -o /output windows.memmap --pid 1234 --dump
# Scanning
python3 vol.py -f memory.dmp windows.vadyarascan --yara-file rules.yar-
svchost.exenot spawned byservices.exe? -
lsass.exehas multiple instances? - Misspelled system processes?
- Processes running from
\Temp\or\Users\? - Unsigned processes with network connections?
-
cmd.exe/powershell.exespawned by Office apps? - Processes with
ExitTimeset but still active? - Memory regions with
PAGE_EXECUTE_READWRITE?
Part of the Incident Response & Log Aggregation Branch
- ../../../README.md - IncidentResponse section index
- ../LiveData/live_data_collection.md - How the memory dump was captured
- ../Disks/autopsy_kape.md - Disk forensics for persistence artifacts after memory analysis
- ../../SIEM/splunk.md - SIEM correlation of memory-derived IOCs
๐ Source: IncidentResponse/Digital-Forensics/Memory/volatility_cheatsheet.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Incident Response
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics