ACTION REQUIRED (execute immediately after reading)
NOW: Read../field-journal/precedent-pentest.mdor organizational IR authorization instructionsNOW: Confirm it isforensics/attributionrather than offensive scanningNOW: Establish a case; read-only copies of evidence take priority (write protection for original media)NEXT: tool-index; Volatility etc. often manualACT: Preserve hashes → timeline → key artifacts
Applicable Scenarios
- Memory dump analysis (Volatility 2/3)
- Disk / E01 / landed file timeline
- PCAP attribution and protocol reconstruction (can be combined with
protocol-reverse/) - Host artifacts: Prefetch, Shimcache, Event Log, browser history
- Incident response IOC extraction (combined with
malware-analysis//threat-hunting/)
Workflow
1. Preservation
□ 计算 SHA256;记录时区与采集命令
□ 工作在副本上;原始只读
□ chain of custody 备注写入 timeline
2. Memory
vol -f mem.dmp windows.info
vol -f mem.dmp windows.pslist
vol -f mem.dmp windows.netscan
vol -f mem.dmp windows.cmdline
3. Host Artifacts
□ 事件日志:Security / PowerShell / Sysmon
□ 持久化:Run 键、服务、计划任务、WMI
□ 执行痕迹:Amcache、Prefetch、BAM
4. Network
□ tshark 统计会话与 DNS
□ 导出可疑流 → protocol-reverse 或 malware C2 分析
Toolchain
| Tool | Purpose |
|---|---|
| Volatility 3 | Memory |
| Timeline Explorer / Plaso | Super timeline |
| tshark | PCAP |
| Eric Zimmerman toolset | Windows artifacts |
| Autopsy / FTK Imager | Disk |
References
references/forensics-triage.md../malware-analysis/../threat-hunting/../protocol-reverse/
Routing Context
Upstream: MASTER R25
Downstream: Deep dive into malicious samples → malware-analysis; rules → threat-hunting
Task Completion Self-Check
- Are hashes and copy strategy preserved?
- Is the timeline reproducible?
- Are IOCs desensitized and graded?
- Checklist?