Forensicator / DFIR Skill Catalog

Decepticon emits attacks AND detection rules. This catalog feeds the detection rules back through real forensic artifacts to confirm they fire — closing the Offensive Vaccine loop on the operations side.

Playbooks

Inline technique reference — not separately loadable skills. The entries below are summarized here for direct use; there is no separate SKILL.md to open for each. Do NOT call the skill loader on them — apply the technique with your tools using this summary and the validation guidance in this file.

Detection validation

• Collect the event log from the relevant host at attack time, along with the detection rule and expected event pattern (for example, event 4662 with the relevant ControlAccessRights).
• Run sigma-cli convert --target sqlite and match against the log file. A zero match count requires checking the rule and artifact coverage; matches provide evidence that the rule detects the captured activity.
• Record the match count and supporting forensic artifacts in the engagement knowledge graph.
• For patch-regression validation, verify whether the rule still fires on attempted exploitation of the patched build.

Tools sandbox

• Volatility 3 (vol, volshell) — already in operator's AGENTS.md tooling.
• plaso (log2timeline, psort).
• sigma-cli (sigma convert, sigma check).
• yara-x (yr) — operator already has it installed at C:\Tools\yara-x\yr.exe.
• Velociraptor + OSQuery (for live-system validation paths).

Why this is differentiating

Strix doesn't have this. XBOW doesn't have this. The "Offensive Vaccine" promise (every attack becomes a defense improvement) is only deliverable when someone validates the detection. Without Forensicator, the loop stops at "rule written". With it, the loop completes at "rule verified to fire on this attack class against this client's stack".