Home › Defensive Security › Memory Forensics
Memory Forensics
Acquisition, Volatility 3 workflows, process/handle analysis and malware in RAM.
▶ Here to build, not read? Jump to the Hands-On Practice.
Prerequisites: Operating Systems · DFIR Fundamentals
Overview
Acquisition, Volatility 3 workflows, process/handle analysis and malware in RAM. In one line: memory forensics decides where trust is placed, and misplaced trust is where the security problem lives. That's the theory you need — the understanding comes from doing it, so the walkthrough below is the heart of this chapter.
How it works
Mechanically, memory forensics comes down to three things: what data is trusted, where it crosses a boundary, and what happens on the other side. The diagram traces that path; you'll walk it for real, step by step, in the practice below.
flowchart TD
A["Memory Forensics"] --> B["Concepts & terminology"]
A --> C["Internal mechanics"]
C --> D["Trust boundaries"]
D --> E["Attack surface"]
D --> F["Defensive controls"]
E --> G["Detection & telemetry"]
F --> G
G --> H["Verification in the lab"]
- Trust boundary — where data or control passes between components of different privilege or trust.
- Attack surface — the set of points an attacker can interact with.
- Primary control — the single measure that most reduces this technique's impact.
- Telemetry — the log or signal a defender uses to detect the technique.
Hands-On Practice
Mission. Reconstruct an intrusion from a memory image with Volatility 3.
🧪 Lab setup — Defensive Security
Wazuh dashboard— https://localhost:5601 (or :443) — SIEM/XDR UI, rules, alertsvictim host + agent— generates the telemetry you hunt over
# blue-lab/docker-compose.yml — Defensive part environment
# Wazuh ships an official single-node compose. Pull it and bring it up:
# git clone https://github.com/wazuh/wazuh-docker -b v4.x
# cd wazuh-docker/single-node && docker compose up -d
# Then add a target that generates events:
services:
victim:
image: ubuntu:22.04
container_name: blue-victim
command: sleep infinity
networks: [labnet]
# (install the Wazuh agent in 'victim', or run Sysmon on a Windows VM,
# then run Atomic Red Team tests to generate detections.)
networks:
labnet:
driver: bridgeTarget for this lesson: dfir-box with a lab RAM image under /evidence (e.g. a CyberDefenders image). Full setup: Defensive Security lab environment.
Guided walkthrough
vol -f /evidence/mem.raw windows.pslistExpected output
A tree including a suspicious powershell.exe under winword.exe.vol -f /evidence/mem.raw windows.psscanExpected output
A process missing from pslist but present in psscan.vol -f /evidence/mem.raw windows.netscanExpected output
An outbound TCP connection to 185.x.x.x:443 from the suspicious PID.vol -f /evidence/mem.raw windows.malfindExpected output
RWX private memory with MZ/shellcode in the suspicious process.vol -f /evidence/mem.raw windows.dumpfiles --pid <pid>Expected output
The malicious module written to disk for static analysis.Live terminal
labserver/README.md), then click Connect lab runner and paste the token. Until then, copy commands from the walkthrough and run them in your own Kali terminal.
Try it yourself
Challenge 1. Recover the command line the attacker ran.
Hint
There's a plugin for process command lines.
Solution
windows.cmdline reveals the full command, often the encoded PowerShell payload.
Challenge 2. Find persistence established by the intrusion.
Hint
Registry run keys live in memory too.
Solution
windows.registry.printkey on the Run keys, or windows.getsids/services plugins.
Challenge 3. Build a short timeline of the attacker's actions from the memory artefacts.
Hint
Correlate process start times, network connections and files.
Solution
Combine pslist times + netscan + cmdline into a narrative; export with timeliner.
Quick quiz
Detect & defend (blue-team view)
- The live equivalents: EDR flags Office→PowerShell, injected RWX memory, and beaconing.
- Turn each memory finding into a detection (Sigma for the process lineage, network rule for the C2).
Skills check
You can move on when you can, without notes:
Check Yourself
Quick self-test — answers hidden. If you can't answer without notes, redo the relevant walkthrough step.
Q1. In one sentence, what security problem does Memory Forensics address or create?
Show answer
Memory Forensics matters because its behaviour determines where trust is placed; misplacing that trust is the root of the associated bug class.
Q2. Name one trust boundary involved in Memory Forensics and what crosses it.
Show answer
Any point where attacker-influenced data meets privileged processing — e.g. user input reaching an interpreter, or a token reaching a verifier.
Q3. Give one attack against Memory Forensics and the single control that most reduces its impact.
Show answer
State the attack precisely, then the primary control (validation, encoding, isolation, authentication, or least privilege) — not a laundry list.
Interview angles
- Walk me through how Memory Forensics works, then tell me where you would attack it.
- How would you detect Memory Forensics being abused in an environment you defend?
- What is the difference between mitigating and eliminating the risk associated with Memory Forensics?
Pitfalls & Best Practice
Common mistakes
- Treating memory forensics as a checkbox instead of understanding the mechanism — defences copied without comprehension fail silently.
- Trusting client-side or default controls to enforce a server-side security property.
- Testing only the happy path and never the abuse cases or malformed input.
- Fixing the symptom (one payload) instead of the class (the missing control).
Do this instead
- Push security decisions to a single, well-tested enforcement point rather than scattering checks.
- Fail closed: when in doubt, deny and log, so misconfiguration reduces access rather than expanding it.
- Instrument the trust boundaries so the same event is visible to offence (as a target) and defence (as a signal).
- Validate your understanding of memory forensics empirically in the lab before trusting it in production.
- Prefer safe, high-level APIs and secure defaults over hand-rolled primitives.
Reference
MITRE ATT&CK Mapping
No single ATT&CK technique maps cleanly to this concept. Once you apply it offensively or defensively, map the specific behaviour using the ATT&CK chapter.
OWASP Mapping
- See OWASP Top 10 for the relevant category when this applies to web systems.
CWE Mapping
- No direct weakness ID; when this concept fails in code it usually surfaces as one of the CWE Top 25 entries.
CAPEC Mapping
- No single attack pattern; see the CAPEC chapter to map behaviour to patterns.
CVE References
- No canonical CVE for a concept page. Search the NVD for concrete instances when studying real cases.
NIST References
- NIST CSRC Publications — search for the control family or guide relevant to this topic.
RFC References
- No governing RFC for this topic. Where a protocol is involved, its RFC is linked from the relevant networking chapter.
Research Papers
- Reflections on Trusting Trust — Ken Thompson, 1984
- Smashing the Stack for Fun and Profit — Aleph One, Phrack 49, 1996
- The Protection of Information in Computer Systems — Saltzer & Schroeder, 1975
Books
- File System Forensic Analysis — Brian Carrier
- The Art of Memory Forensics — Ligh, Case, Levy & Walters
- Windows Forensic Analysis — Harlan Carvey
Official Documentation
Related Chapters
- Defensive Security Methodology
- Security Operations Center
- SIEM
- Intrusion Detection Systems
- Intrusion Prevention Systems
- Endpoint Detection and Response
Part of the Defensive Security section of Cybersecurity-Mastery. 🟠 Advanced · ~72 min hands-on · Last updated 2026-08-12.