# incident-response-forensics

incident-response-forensics — a skill for collecting and analyzing digital evidence during security incident investigations. Preserves proof without corruption, gathers ephemeral data, and constructs an attack timeline.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 254 installs
- Author: securityskills
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/securityskills/skills/tree/HEAD/forensics/incident-response-forensics/SKILL.md
- Updated: 2026-08-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/incident-response-forensics

## What it does

The skill defines the correct sequence for responding to a system compromise. Start with a memory snapshot, then create a disk image through a write-blocker or verified snapshot with SHA-256 hashing and chain-of-custody documentation, while simultaneously collecting network logs from firewalls and proxies. The core principle: investigate the live system only read-only beyond initial collection—deeper probing triggers attacker tooling.

Next comes volatile data in strict order: network connections and routing, running processes, logged-in sessions, command histories. On Windows, examine Shimcache, Prefetch, and Event logs for logon events and process creation; on Linux check `/var/log/auth.log` and `.bash_history`. In cloud environments, review CloudTrail and `AssumeRole` chains. Normalize all artifacts into a unified timeline anchored to the first compromise indicator, then expand forward (persistence, lateral movement) and backward (reconnaissance, delivery).

Output includes IOCs with context, attack narrative mapped to ATT&CK techniques with evidence references, and a root-cause hypothesis. Requires familiarity with tools like WinPMEM, LiME, and log analysis utilities.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill incident-response-forensics -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/incident-response-forensics/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/incident-response-forensics/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill incident-response-forensics -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/incident-response-forensics/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill incident-response-forensics -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/incident-response-forensics/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install securityskills/skills forensics/incident-response-forensics/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/incident-response-forensics/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill incident-response-forensics -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/securityskills/skills --path forensics/incident-response-forensics
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/incident-response-forensics/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add securityskills/skills --skill incident-response-forensics -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/securityskills/skills/tree/HEAD/forensics/incident-response-forensics/SKILL.md

## When to use it
- collect evidence from a compromised system without destroying it
- map the attack timeline from initial access through data exfiltration
- identify lateral movement and persistence mechanisms
- determine the initial compromise vector
- document chain of custody for incident reports

## Example prompts
- What's the correct order to collect evidence from a breached Windows server?
- Build a timeline from a Linux disk image using logs and command history
- Find signs of lateral movement in Event logs across the network

## Similar
- [incident-response](https://affpapa.org/en/nevibecode/skills/devops-skills-incident-response.md) — skill · 455 installs
- [ssh-access-forensics](https://affpapa.org/en/nevibecode/skills/ssh-access-forensics.md) — skill · ★ 71 repo stars
- [agency-incident-responder](https://affpapa.org/en/nevibecode/skills/agency-incident-responder.md) — skill · ★ 85 repo stars
- [memory-forensics-volatility](https://affpapa.org/en/nevibecode/skills/memory-forensics-volatility.md) — skill · 3900 installs
- [incident-triage](https://affpapa.org/en/nevibecode/skills/incident-triage.md) — skill · 464 installs
- [incident-response-test-automator](https://affpapa.org/en/nevibecode/agents/incident-response-test-automator.md) — subagent · ★ 42780 repo stars

From the same set: [securityskills/skills](https://affpapa.org/en/nevibecode/by/securityskills/skills.md) — 21 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
