mcpField
S
security-incident-playbook-generator

security-incident-playbook-generator

github.com/patricio0312revSecurity63213 installsUpdated 41w ago
Repository

About security-incident-playbook-generator

A security-planning skill for preparing structured incident response playbooks. Its checklist covers response phases, containment, communications, evidence collection, and post-incident review.

Key features

  1. 01Structured response phases
  2. 02Containment procedures
  3. 03Communication templates
  4. 04Evidence collection rules
  5. 05Post-incident review checklist

Use cases

  1. 01Drafting an incident response playbook
  2. 02Defining containment and evidence procedures
  3. 03Preparing incident communication templates

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/patricio0312rev/skills --skill security-incident-playbook-generator

After installing, type/security-incident-playbook-generatorin Claude Code to confirm it loaded.

Details

From the project README

Security Incident Playbook Generator

Prepare for security incidents with structured response plans.

Incident Response Phases

# Security Incident Response Playbook

## Phase 1: Detection & Triage (0-15 min)

### Detection Sources

- Security alerts (CloudWatch, Sentry)
- User reports
- Anomaly detection
- Penetration test findings

### Initial Assessment

- [ ] Identify incident type
- [ ] Assess severity (P0-P3)
- [ ] Determine scope
- [ ] Alert on-call security

## Phase 2: Containment (15-60 min)

### Immediate Actions

- [ ] Isolate affected systems
- [ ] Revoke compromised credentials
- [ ] Block malicious IPs
- [ ] Enable enhanced monitoring

### Evidence Preservation

- [ ] Capture logs
- [ ] Take system snapshots
- [ ] Document timeline
- [ ] Preserve artifacts

## Phase 3: Eradication (1-24 hours)

- [ ] Remove malware
- [ ] Close vulnerabilities
- [ ] Reset passwords
- [ ] Update firewall rules

## Phase 4: Recovery (24-72 hours)

- [ ] Restore from backup
- [ ] Verify system integrity
- [ ] Resume operations
- [ ] Monitor for reinfection

## Phase 5: Post-Incident (1 week)

- [ ] Document lessons learned
- [ ] Update procedures
- [ ] Security training
- [ ] Notify affected users (if required)

Output Checklist

  • Response phases defined
  • Containment procedures
  • Communication templates
  • Evidence collection rules
  • Post-incident review ENDFILE

Comments

Markdown supported