Conducting Memory Forensics With Volatility
Overview
Cybersecurity skill for conducting memory forensics with volatility. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"conducting memory forensics with volatility"
"Performs memory forensics analysis using Volatility 3 to extract evidence of mal"
An endpoint has been contained during an active incident and volatile evidence must be preserved
EDR alerts suggest process injection or fileless malware that only exists in memory
Encryption keys need to be recovered from a ransomware-infected system before shutdown
Credential theft (Mimikatz, LSASS dumping) is suspected and evidence must be confirmed
A rootkit or kernel-level compromise is suspected and disk-based analysis is insufficient
Do not use for analyzing disk images or file system artifacts; use disk forensics tools (Autopsy, FTK) for those tasks.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Memory acquisition tool deployed or available: WinPmem, Magnet RAM Capture, DumpIt, or AVML (Linux)
- Volatility 3 installed with Python 3.8+ and required symbol tables
- Sufficient storage for memory dumps (equal to system RAM size, typically 8-64 GB)
- YARA rules for malware detection in memory (Florian Roth's signature-base, custom rules)
- Reference baseline of normal processes and DLLs for the OS version being analyzed
- Chain of custody documentation for evidence handling
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Scope the Analysis — Define what memory forensics artifacts or data sources to examine and the investigation timeline.
- Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
- Extract Key Indicators — Use volatility to parse and extract relevant memory forensics data points from collected artifacts.
- Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
- Build Timeline — Construct a chronological sequence of events related to memory forensics.
- Document Analysis — Write findings report with evidence, conclusions, and recommendations.
Tools
- volatility — Primary tool for this skill
- Forensic Toolkit — Evidence collection and analysis
- Timeline Tools — Chronological event reconstruction
- Log Analysis Platform — Centralized log parsing and search
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: conducting-memory-forensics-with-volatility3description: Use when performing memory forensics analysis using Volatility 3 to extract4 evidence of malware execution, process injection, network connections, and credential5 theft from RAM dumps captured during incident response. Covers memory acquisition,6 process analysis, DLL inspection, and malware detection. Activates for requests7 involving memory forensics, RAM analysis, Volatility framework, memory dump investigation,8 volatile evidence analysis, or live memory acquisition.9domain: cybersecurity10tags:11- memory-forensics12- volatility13- RAM-analysis14- process-injection15- DFIR16subdomain: incident-response17mitre_attack:18- T100319- T105520- T162021- T157422version: 1.0.023author: oyi7724license: Apache-2.025nist_csf:26- RS.MA-0127- RS.MA-0228- RS.AN-0329- RC.RP-0130category: cybersecurity31metadata:32 source: https://skillmd.com/skills/oyi77/conducting-memory-forensics-with-volatility33---3435# Conducting Memory Forensics With Volatility3637## Overview3839Cybersecurity skill for conducting memory forensics with volatility. Follows industry best practices and security standards.4041## When to Use42**Trigger phrases:**43- "conducting memory forensics with volatility"44- "Performs memory forensics analysis using Volatility 3 to extract evidence of mal"454647- An endpoint has been contained during an active incident and volatile evidence must be preserved48- EDR alerts suggest process injection or fileless malware that only exists in memory49- Encryption keys need to be recovered from a ransomware-infected system before shutdown50- Credential theft (Mimikatz, LSASS dumping) is suspected and evidence must be confirmed51- A rootkit or kernel-level compromise is suspected and disk-based analysis is insufficient5253**Do not use** for analyzing disk images or file system artifacts; use disk forensics tools (Autopsy, FTK) for those tasks.545556## When NOT to Use5758- When you lack proper authorization for testing59- For production systems without change management60- When the task requires legal or compliance expertise beyond technical scope616263## Prerequisites6465- Memory acquisition tool deployed or available: WinPmem, Magnet RAM Capture, DumpIt, or AVML (Linux)66- Volatility 3 installed with Python 3.8+ and required symbol tables67- Sufficient storage for memory dumps (equal to system RAM size, typically 8-64 GB)68- YARA rules for malware detection in memory (Florian Roth's signature-base, custom rules)69- Reference baseline of normal processes and DLLs for the OS version being analyzed70- Chain of custody documentation for evidence handling7172## Workflow7374```python75# Example: IOC detection76import re7778IOC_PATTERNS = {79 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",80 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",81 "hash_md5": r"\b[a-f0-9]{32}\b",82 "hash_sha256": r"\b[a-f0-9]{64}\b",83}8485def extract_iocs(text: str) -> dict:86 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}87```88891. **Scope the Analysis** — Define what memory forensics artifacts or data sources to examine and the investigation timeline.902. **Preserve Evidence** — Create forensic copies of relevant data. Maintain chain of custody documentation.913. **Extract Key Indicators** — Use volatility to parse and extract relevant memory forensics data points from collected artifacts.924. **Correlate Findings** — Cross-reference extracted data with other sources (threat intel, logs, timelines).935. **Build Timeline** — Construct a chronological sequence of events related to memory forensics.946. **Document Analysis** — Write findings report with evidence, conclusions, and recommendations.9596## Tools9798- **volatility** — Primary tool for this skill99- **Forensic Toolkit** — Evidence collection and analysis100- **Timeline Tools** — Chronological event reconstruction101- **Log Analysis Platform** — Centralized log parsing and search102103104## Process1051061. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1071. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1081. **Reporting** — Document IOCs, write findings, provide remediation recommendations109110## Verification111112- [ ] All memory forensics procedures executed completely and documented113- [ ] Findings validated against multiple data sources114- [ ] False positives identified and filtered115- [ ] Results documented with evidence and timestamps116- [ ] Recommendations provided with risk-based prioritization117118## Anti-Rationalization Table119120| Rationalization | Reality |121|---|---|122| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |123| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |124| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |