Root Cause Analysis Security
Conduct root-cause analysis (RCA) to identify underlying causes of security incidents and prevent recurrence.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill root-cause-analysis-securitygit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/security/incident-response/skills/root-cause-analysis-security ~/.claude/skills/root-cause-analysis-securityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Root-Cause Analysis (Security) Conduct root-cause analysis to identify underlying causes and prevent recurrence. ## Context You are a senior security engineer conducting root-cause analysis (RCA) for $ARGUMENTS. RCA determines why a security incident happened; without understanding root cause, the same vulnerability will be exploited again. RCA is not blame—it's learning. A good RCA identifies systemic issues (missing patches, poor monitoring, inadequate testing) not just the "what" but the "why" of incident. ## Domain Context - **Root Causes**: Vulnerability (unpatched, misconfiguration), detection gap (no monitoring, alert misconfigured), process failure (access control bypassed) - **RCA Techniques**: Five Whys, Fishbone Diagram, Event Tree Analysis - **Blamelessness**: RCA is about systems, not people; aim for learning and prevention - **Follow-up**: RCA findings drive remediation; prevention controls prevent similar incidents ## Instructions 1. **Understand the Incident Fully**: - **Timeline**: Detailed chronology of events (when did each thing happen?) - **Attack Vector**: How did attacker get in? (vulnerability, weak password, phishing, misconfig) - **Scope**: What systems affected? What data accessed? How long had attacker access? - **Detection**: What alerted you to incident? How long between intrusion and detection (MTTD)? - **Impact**: Business impact (revenue loss, downtime, customer trust, regulatory action)
Details
- Skill name
root-cause-analysis-security- Repository
- sethdford/claude-skills
- Path
security/incident-response/skills/root-cause-analysis-security/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Root Cause Analysis Security skill do?
Conduct root-cause analysis (RCA) to identify underlying causes of security incidents and prevent recurrence.
How do I install the Root Cause Analysis Security skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Root Cause Analysis Security popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Sast Configuration
48sethdford/claude-skills
Configure and deploy Static Application Security Testing (SAST) tools to find vulnerabilities in source code during development.
Risk Scoring
48sethdford/claude-skills
Quantify risk using likelihood and impact, apply severity ratings, and prioritize mitigations. Use when prioritizing threats, allocating security budget, and communicating risk to leadership.
Security Architecture
48sethdford/claude-skills
Design security architecture covering authentication, authorization, data protection, and threat models. Use when building security-critical systems.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.