ec-ecih

Guides incident response decisions using the ECIH 9-stage lifecycle and NIST 800-61 frameworks.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/yogiex/opencode-cyber-security-skills --skill ec-ecih-yogiex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ec-ecih
Source: https://github.com/yogiex/opencode-cyber-security-skills/tree/main/skills/ec-ecih
Command: npx skills add https://github.com/yogiex/opencode-cyber-security-skills --skill ec-ecih-yogiex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Responding to a security incident under pressure with incomplete information leads to costly mistakes like destroying forensic evidence, missing regulatory notification deadlines, or failing to fully eradicate attacker persistence. This Skill provides structured decision frameworks, playbooks, and checklists so incident handlers make the right call at each stage of the response lifecycle. ## Core Features & Use Cases - Full IR Lifecycle Guidance: Covers the ECIH 9-stage IH&R lifecycle mapped to NIST 800-61 and SANS PICERL, from preparation through post-incident lessons learned. - Incident-Type Playbooks: Step-by-step response guides for ransomware, data breach, account compromise, phishing/BEC, insider threat, DDoS, cloud incidents, and web application compromise. - Forensics & Compliance Support: Order of volatility, chain of custody procedures, evidence documentation templates, and regulatory notification timelines (GDPR 72-hour, HIPAA, PCI DSS). - Use Case: During a ransomware outbreak, use the ransomware playbook to isolate endpoints, capture memory before shutdown, document the ransom note as evidence, and follow the recovery sequence to restore from verified clean backups. ## Quick Start Ask the agent to walk you through containing and collecting evidence for a confirmed ransomware incident on an endpoint.

Frequently Asked Questions about ec-ecih

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

FAQPage Schema
How do I respond to a ransomware incident step by step?▼

Isolate the affected endpoint from the network immediately, capture memory before any shutdown, and screenshot the ransom note as evidence. Then reimage affected systems, restore from verified clean backups, and patch the initial infection vector such as exposed RDP or phishing.

What is the correct order of the incident response lifecycle?▼

The ECIH 9-stage lifecycle runs Preparation, Recording, Triage, Notification, Containment, Evidence Gathering, Eradication, Recovery, and Post-Incident. Containment always precedes eradication, and eradication precedes recovery.

Should I collect evidence before or after containment?▼

Collect volatile evidence like memory and network connections before full containment when possible, since powering off destroys it. However, if spread risk is high, contain first and accept the evidence trade-off consciously.

When must a data breach be reported under GDPR?▼

GDPR requires notifying the supervisory authority within 72 hours of detecting a breach involving personal data, even if the investigation is still ongoing. The clock starts at detection, not at confirmation of full scope.

Why does restoring from backup sometimes cause re-infection?▼

Restoring from a backup created after the initial compromise reintroduces the malware or backdoor. Always verify the backup predates the compromise and validate its integrity before restoring.

How does ECIH differ from NIST 800-61 incident response?▼

ECIH splits NIST's Detection and Analysis phase into Recording, Triage, and Notification, and separates Containment, Evidence Gathering, Eradication, and Recovery into distinct stages. This gives finer granularity while covering the same overall process.