competition-forensic-timeline

Correlates EVTX, PCAP, registry, and memory artifacts into replayable forensic incident timelines.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-forensic-timeline-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-forensic-timeline
Source: https://github.com/dbx0/skills/tree/main/skills/forensics-dfir/collection/competition-forensic-timeline
Command: npx skills add https://github.com/dbx0/skills --skill competition-forensic-timeline-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning many scattered forensic artifacts into one coherent, replayable chronology is the hardest part of DFIR work. This Skill guides the reconstruction of attacker activity by anchoring events, normalizing timestamps, and correlating artifacts across sources so you can prove the exact order of compromise, persistence, and exfiltration. ## Core Features & Use Cases - Timeline Anchor Selection: Identify the smallest reliable anchors such as first execution, first logon, first network session, or first mailbox action, while recording clock source, timezone, and drift. - Cross-Artifact Correlation: Link EVTX, Sysmon, registry, Amcache, prefetch, browser, mail, PCAP, memory, and filesystem artifacts using shared identifiers like PID, logon ID, GUID, message ID, and hash. - Decisive Story Compression: Reduce the full chronology to the minimal sequence proving initial access, persistence, lateral movement, or exfiltration, keeping inferred edges separate from confirmed events. - Use Case: During a CTF or incident response engagement, you receive EVTX logs, a PCAP, and registry hives from a compromised host. Use this Skill to build the ordered chain from foothold to persistence and pinpoint the exact event where the decisive artifact appears. ## Quick Start Ask the assistant to build a forensic timeline correlating the provided EVTX logs, PCAP, and registry artifacts to reconstruct the attacker's actions in order.

Frequently Asked Questions about competition-forensic-timeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a forensic timeline from multiple artifacts?

Start by picking the smallest reliable anchor such as first execution or first logon, then normalize timestamps, timezones, and hostnames before correlating. Link artifacts using shared identifiers like PID, logon ID, or hash, and compress the result into the minimal chain proving the attack path.

How to correlate EVTX logs with PCAP and registry artifacts?

Match on shared identifiers rather than timestamps alone: process IDs, logon IDs, session IDs, hostnames, IPs, and file hashes. Record each source's clock origin and drift first, since delayed logging or timezone differences can reorder events incorrectly.

When should I use this skill instead of a PCAP analysis skill?

Use this skill when the challenge is chronology and cross-artifact correlation across many evidence sources. If the hard part is packet reassembly, protocol framing, or extracting transferred objects from a capture, switch to the dedicated PCAP protocol skill instead.

Why does timestamp sorting alone break forensic timelines?

Clock drift, missing timezones, daylight-saving ambiguity, and delayed logging can reorder events when sorted naively. Always record the time source per artifact and validate ordering with causal identifiers like parent process IDs and logon IDs.

What are the limitations of cross-artifact timeline correlation?

Correlation depends on artifacts sharing linkable identifiers; without them, edges remain inferred rather than confirmed. The skill explicitly separates observed events from inferred transitions and flags missing validation steps instead of merging them into the confirmed chronology.