# Forensicator Specialist Methods

> Evidence-led forensicator technical methods and evidence interpretation for the relevant environment.

- Skill: `purpleailab/forensicator-specialist-methods` (Agent Skill)
- Install (CLI): `npx get-skill add purpleailab/forensicator-specialist-methods`
- Raw SKILL.md: https://api.skillmd.com/api/skills/purpleailab/forensicator-specialist-methods/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: purpleailab (https://skillmd.com/u/purpleailab)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/purpleailab/forensicator-specialist-methods

---


# Technical methods and evidence

Use the relevant existing technique skills for implementation details. These notes
explain technical prerequisites and evidentiary limits; they do not define an
engagement stage order, dispatch policy, or report lifecycle. Tool availability and
argument names come from the live schema. Authorization comes from the RoE.

## Evidence-source selection

Memory analysis (Volatility 3), disk/super-timeline work (Plaso/log2timeline), Windows
registry/EVTX analysis and network parsing (tshark/Zeek) answer different questions.
Record acquisition source, hash, timezone, clock offset, collection gaps and parser
version. Work on copies; a parsed view must remain traceable to original bytes.

## Correlation and uncertainty

Prefer shared process/request/session identifiers over temporal proximity. A nearby
log line is a lead, not causation. Missing telemetry can reflect collection loss,
retention or parser limitations; it is not proof an operation did not occur. IOC
matches need context (path, signer, ownership, observed behavior) to distinguish
benign reuse. ATT&CK mappings require a supported technique, not merely a tool name.
Existing dfir memory, disk, log and network skills provide format-specific analysis.

