07-incident-response
IR playbook execution, evidence collection, forensic timeline analysis,
Install / Use
npx skills add Masriyan/Claude-Code-CyberSecurity-Skill --skill 07-incident-responseInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of 07-incident-response
07-incident-response scores 88/100 on our quality scale, 637th of 1,097 Security skills we index.
Its SKILL.md is 15 KB long, well organised into 43 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.
It has 441 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so 07-incident-response is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
07-incident-response compared with similar skills
All 4 of these similar skills score higher than 07-incident-response; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| 07-incident-response (this skill)by Masriyan | 88 | 441 | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 113.0k | 10d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.1k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 104.2k | 1d ago | MCP Server |
| crawl4aiby unclecode | 100 | 87.5k | today | MCP Server |
Frequently asked questions
- How do I install 07-incident-response?
- Run
npx skills add Masriyan/Claude-Code-CyberSecurity-Skill --skill 07-incident-response. The install tabs above show the steps for each supported agent. - Which AI agents does 07-incident-response work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is 07-incident-response safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is 07-incident-response still maintained?
- The repository was last updated about 2 months ago, so 07-incident-response is actively maintained.
Skill content
View source on GitHubname: Incident Response & Digital Forensics description: IR playbook execution, evidence collection, forensic timeline analysis, memory forensics, and post-incident reporting following NIST SP 800-61 and SANS PICERL methodology version: 3.1.0 author: Masriyan tags: [cybersecurity, incident-response, forensics, dfir, evidence, timeline, picerl, nist]
Incident Response & Digital Forensics
Purpose
Enable Claude to assist with structured incident response operations following NIST SP 800-61 and the SANS PICERL framework. Claude generates IR playbooks, guides evidence collection with chain of custody, constructs forensic timelines, interprets memory forensics output, and produces post-incident reports.
Activation Triggers
This skill activates when the user asks about:
- Creating an incident response playbook (ransomware, phishing, breach, etc.)
- Evidence collection and chain of custody procedures
- Forensic timeline construction from logs or artifacts
- Memory forensics using Volatility
- Post-incident report generation
- DFIR (Digital Forensics and Incident Response) procedures
- Containment and eradication strategies
- Root cause analysis for security incidents
- IR metrics, SLA tracking, or reporting for management
Prerequisites
pip install pyyaml jinja2 pandas python-dateutil
Recommended DFIR tools:
Volatility 3— Memory forensics frameworkAutopsy / Sleuth Kit— Disk forensicsplaso / log2timeline— Supertimeline generationKAPE— Evidence collection (Windows)Velociraptor— Enterprise-scale endpoint forensicsFTK Imager— Forensic imaging (Windows)dd / dcfldd / dc3dd— Disk imaging (Linux)
PICERL Framework Overview
Every IR engagement follows the PICERL lifecycle:
| Phase | Key Actions | Skill Outputs | |-------|------------|---------------| | Preparation | Verify tools, comms, access | Readiness checklist | | Identification | Confirm incident, scope, severity | Incident classification | | Containment | Isolate systems, stop spread | Containment actions list | | Eradication | Remove threat, close access | Eradication checklist | | Recovery | Restore systems, verify integrity | Recovery runbook | | Lessons Learned | Post-incident review | IR report + improvements |
Core Capabilities
1. IR Playbook Creation
When the user asks to create a playbook for a specific incident type:
Claude generates detailed, role-assigned playbooks in this structure:
Ransomware Response Playbook (Example):
# IR Playbook: Ransomware Attack
Version: 2.0 | Owner: SOC Manager | Review: Quarterly
## Trigger Conditions
- Multiple encrypted files discovered (ransom extension detected)
- Ransom note found on file shares or desktop
- EDR alert for mass file modification activity
- User reports files inaccessible with unfamiliar extensions
## Severity Classification
- CRITICAL: Domain controller / backup infrastructure affected
- HIGH: Production servers / business-critical data affected
- MEDIUM: Isolated workstation, contained environment
---
## Phase 1: Identification (Target: 15 minutes)
**IR Lead:**
- [ ] Confirm incident is ransomware (verify encrypted files + ransom note)
- [ ] Determine initial infection vector (phishing? RDP? Supply chain?)
- [ ] Identify Patient Zero — first encrypted system
- [ ] Assess scope: How many systems? Which business units?
- [ ] Declare incident severity and notify stakeholders
- [ ] Open incident ticket and begin documentation
**Forensics:**
- [ ] DO NOT REBOOT infected systems (preserve volatile evidence)
- [ ] Capture memory dump: `winpmem_mini_x64_rc2.exe output.raw`
- [ ] Collect running processes: `tasklist /v > processes.txt`
- [ ] Collect network connections: `netstat -ano > netstat.txt`
## Phase 2: Containment (Target: 30 minutes)
**Network Team:**
- [ ] Isolate affected systems (pull network cable or quarantine in VLAN)
- [ ] Block identified C2 IPs/domains at perimeter firewall
- [ ] Disable RDP externally if RDP was the initial vector
- [ ] Preserve network capture if encryption is still occurring
**Active Directory:**
- [ ] Identify all accounts used by the ransomware (service accounts, domain accounts)
- [ ] Reset passwords for all potentially compromised accounts
- [ ] Revoke active sessions for affected accounts
- [ ] Check for newly created privileged accounts
## Phase 3: Eradication
- [ ] Identify all persistence mechanisms (registry, services, scheduled tasks)
- [ ] Remove all malicious artifacts
- [ ] Verify no backdoors remain (check with Autoruns, process scanning)
- [ ] Patch the exploited vulnerability if one was used
## Phase 4: Recovery
- [ ] Restore from clean backup (verified pre-infection)
- [ ] Validate backup integrity before restoration
- [ ] Rebuild from gold image if backup compromised
- [ ] Verify data integrity after restoration
- [ ] Phased return to production
## Phase 5: Lessons Learned (Within 2 weeks)
- [ ] Full incident timeline documented
- [ ] Root cause identified and remediated
- [ ] Detection gaps addressed
- [ ] CSOC playbook updated
- [ ] Management report delivered
Other supported playbook types:
- Phishing Campaign Response
- Data Breach / Exfiltration
- Business Email Compromise (BEC)
- Insider Threat
- DDoS Attack
- Account Compromise / Credential Stuffing
- Supply Chain Compromise
- Cloud Misconfiguration / Breach
2. Evidence Collection & Chain of Custody
When the user asks to collect forensic evidence:
Order of Volatility (most volatile → least volatile):
1. CPU registers and cache
2. Routing tables, ARP cache, process table
3. Memory (RAM) — ALWAYS capture first
4. Temporary file systems, swap space
5. Running processes and open files
6. Network connections and open ports
7. Disk images
8. Log files (local + remote SIEM)
9. Physical media
Evidence Collection Commands:
# Windows — Live acquisition
winpmem_mini_x64_rc2.exe memory.raw # Memory dump
tasklist /svc > processes.txt # Running processes
netstat -ano > connections.txt # Network connections
wmic process get caption,processid,parentprocessid,commandline > process_full.txt
reg export HKLM reg_hklm.reg # Registry
dir /s /a "C:\Users\*\AppData\Roaming\*" > appdata.txt
# Linux — Live acquisition
sudo avml /tmp/memory.lime # Memory dump (avml)
ps auxf > processes.txt # Process tree
netstat -tulnap > connections.txt # Network connections
cat /proc/*/cmdline | strings > process_cmdlines.txt
ls -la /tmp/ /var/tmp/ /dev/shm/ > temp_dirs.txt
crontab -l -u root > crontabs.txt
find / -mtime -7 -type f > recently_modified.txt # Modified in last 7 days
Chain of Custody Template:
## Evidence Chain of Custody Form
| Field | Value |
|-------|-------|
| Evidence ID | IR-2025-001-E01 |
| Incident ID | IR-2025-001 |
| Description | Memory dump from HOSTNAME (192.168.1.100) |
| Collected by | [Analyst Name] |
| Collection time | 2025-05-28 14:30 UTC |
| Collection method | winpmem_mini_x64_rc2.exe |
| MD5 hash | [hash of evidence file] |
| SHA256 hash | [hash of evidence file] |
| Storage location | \nas\ir\IR-2025-001\evidence\ |
| Chain of custody | Analyst → Evidence Locker → Lab |
**Access Log:**
| Date/Time | Person | Purpose | Signature |
|-----------|--------|---------|-----------|
| 2025-05-28 14:30 | [Analyst] | Initial collection | [Sig] |
3. Forensic Timeline Analysis
When the user asks to build an incident timeline:
-
Collect timestamps from all available sources:
- Windows Event Logs (Security, System, Application, PowerShell)
- Web server access logs
- Firewall / proxy logs
- Email server logs (delivery, read receipts)
- File system timestamps (Modified, Accessed, Changed, Born)
- Registry LastWrite timestamps
- Prefetch timestamps (evidence of execution)
-
Normalize to UTC — Confirm system timezone before conversion
-
Generate supertimeline:
python scripts/timeline_builder.py --logs ./collected_logs/ --output timeline.csv python scripts/timeline_builder.py --logs ./logs/ --format html --start "2025-05-20" --end "2025-05-28" -
Identify the kill chain progression:
## Incident Timeline — [Incident ID]
[T-72h] 2025-05-25 09:15 UTC — DELIVERY
Phishing email received: "Invoice_May2025.pdf.exe" from spoofed sender
Mail log: SMTP delivery to user@victim.com from 185.x.x.x
[T-48h] 2025-05-26 14:22 UTC — EXECUTION
User executed attachment: Event 4688 (process creation)
Parent: outlook.exe → Child: powershell.exe -enc [base64]
[T-48h] 2025-05-26 14:22 UTC — C2 ESTABLISHED
Outbound connection: 203.x.x.x:443 (beacon_interval: 60s)
DNS query: malicious-c2.evil.com → 203.x.x.x
[T-24h] 2025-05-27 02:00 UTC — LATERAL MOVEMENT
PsExec from WORKSTATION01 to SERVER02 (admin$)
Event 4624 (login type 3) on SERVER02 from WORKSTATION01
[T-2h] 2025-05-27 12:30 UTC — DATA EXFILTRATION
Large POST request (450MB) to dropbox-like service
[T-0h] 2025-05-28 14:00 UTC — DETECTION
SOC analyst detected anomalous outbound transfer
4. Memory Forensics
When the user shares Volatility output or asks about memory forensics:
Essential Volatility 3 Commands:
# Process listing
python vol.py -f memory.raw windows.pslist
python vol.py -f memory.raw windows.pstree # Show parent-child
python vol.py -f memory.raw windows.psscan # Find hidden processes
# Network connections
python vol.py -f memory.raw windows.netscan
python vol.py -f memory.raw windows.netstat
# DLL and module analysis
python vol.py -f memory.raw windows.dlllist --pid [PID]
python vol.py -f memory.raw windows.modscan # All loaded modules
# Malware detection
python vol.py -f memory.raw windows.malfind # Injected code
python vol.py -f memory.raw windows.hollowfind # Process hollowing
# Registry from memory
python vol.py -f memory.raw windows.registry.hivelist
python vol.py -f memory.raw windows.registry.printkey --key "SOFTWARE\Microsoft\Windows\CurrentVersion\Run"
# File artifacts
python vol.py -f memory.raw windows.filescan
python vol.py -f memory.raw windows.dumpfiles --physaddr [addr]
Suspicious Memory Indicators:
- Process without corresponding disk file (process hollowing)
explorer.exeorsvchost.exewith unusual parent- Network connections from system processes (lsass.exe, csrss.exe)
- Executable memory regions flagged by
windows.malfind - Stacked THREADS in injected shellcode regions
5. Post-Incident Report
When the user asks for an IR report for management or compliance:
# Post-Incident Report — [Incident ID]
**Classification:** CONFIDENTIAL
**Incident Type:** [Ransomware / Data Breach / etc.]
**Severity:** [Critical / High / Medium]
**Incident Window:** [Start] to [End] UTC
**Systems Affected:** [Count and names]
**Data Impact:** [Data at risk / confirmed exfiltrated]
**Report Date:** [Date]
**Report Author:** [IR Lead]
---
## 1. Executive Summary
[3-4 sentences: what happened, how it happened, impact, and current status]
## 2. Incident Timeline
[Key events table with timestamps]
## 3. Root Cause Analysis
**Initial Vector:** [Phishing / Unpatched service / Credential theft / etc.]
**Root Cause:** [Specific technical cause]
**Contributing Factors:**
- [Factor 1: e.g., no MFA on VPN]
- [Factor 2: e.g., delayed patch deployment]
## 4. Impact Assessment
- **Systems Compromised:** [List]
- **Data Accessed/Exfiltrated:** [Description + quantity]
- **Business Impact:** [Downtime hours, revenue impact, regulatory]
- **Customer/Partner Impact:** [If applicable]
## 5. Containment & Remediation Actions
[Chronological list of actions taken]
## 6. Compliance Notification Requirements
- **GDPR:** [Required if EU personal data — 72-hour
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
113.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
80.1kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
104.2k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.5kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
