Back to catalog
Static reviewDevelopment

Skill dossier

building-incident-response-playbook

Source declaration

Designs and documents structured incident response playbooks with step-by-step procedures per incident type, decision trees, escalation criteria, RACI matrices, and SOAR platform integration, aligned to NIST SP 800-61r3 and SANS PICERL. Use when creating or maturing an IR program, documenting response runbooks for a new incident type, or designing SOAR playbooks.

The author's original description, preserved in English. It describes intent, not verified performance.

Designs and documents structured incident response playbooks with step-by-step procedures per incident type, decision trees, escalation criteria, RACI matrices, and SOAR platform integration, aligned to NIST SP 800-61r3 and SANS PICERL. Use when creating or maturing an IR program, documenting response runbooks for a new incident type, or designing SOAR playbooks.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Designs and documents structured incident response playbooks with step-by-step procedures per incident type, decision trees, escalation criteria, RACI matrices, and SOAR platform integration, aligned to NIST SP 800-61r3 and SANS PICERL. Use when creating or maturing an IR program, documenting response runbooks for a new incident type, or designing SOAR playbooks. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/building-incident-response-playbook/SKILL.md:L53]
  • Step 1: Select and Scope the Incident Type [Source statement; provisional, not tested. Evidence: skills/building-incident-response-playbook/SKILL.md:L55]
  • Step 2: Define the Playbook Structure [Source statement; provisional, not tested. Evidence: skills/building-incident-response-playbook/SKILL.md:L78]
  • Step 3: Write Decision Trees and Escalation Criteria [Source statement; provisional, not tested. Evidence: skills/building-incident-response-playbook/SKILL.md:L129]
  • Step 4: Define Specific Technical Procedures [Source statement; provisional, not tested. Evidence: skills/building-incident-response-playbook/SKILL.md:L152]
  • Step 5: Integrate with SOAR Platform [Source statement; provisional, not tested. Evidence: skills/building-incident-response-playbook/SKILL.md:L173]
  • Step 6: Test and Maintain the Playbook [Source statement; provisional, not tested. Evidence: skills/building-incident-response-playbook/SKILL.md:L183]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/building-incident-response-playbook/SKILL.md:L1-L30]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
32.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/building-incident-response-playbook/LICENSEOther11 KB
skills/building-incident-response-playbook/references/api-reference.mdReference2.3 KB
skills/building-incident-response-playbook/scripts/agent.pyScript9.5 KB
skills/building-incident-response-playbook/SKILL.mdInstruction10.1 KB

SKILL.md frontmatter

{
  "name": "building-incident-response-playbook",
  "description": "Designs and documents structured incident response playbooks with step-by-step procedures per incident type, decision trees, escalation criteria, RACI matrices, and SOAR platform integration, aligned to NIST SP 800-61r3 and SANS PICERL. Use when creating or maturing an IR program, documenting response runbooks for a new incident type, or designing SOAR playbooks.",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "IR-playbook",
    "runbook",
    "NIST-800-61",
    "SOAR-integration",
    "response-procedures"
  ],
  "mitre_attack": [
    "T1486",
    "T1566",
    "T1190",
    "T1041",
    "T1078"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Select and Scope the Incident Type

    Source-described action candidate under “Step 1: Select and Scope the Incident Type”; not verified execution.

  4. 04
    Action

    Identify the top incident types based on organizational risk assessment and historical data

    Source-described action candidate under “Step 1: Select and Scope the Incident Type”; not verified execution.

  5. 05
    Action

    Scope each playbook to a single incident type for clarity (do not combine unrelated scenarios)

    Source-described action candidate under “Step 1: Select and Scope the Incident Type”; not verified execution.

  6. 06
    Action

    Define trigger conditions that activate the playbook

    Source-described action candidate under “Step 1: Select and Scope the Incident Type”; not verified execution.

Inspect all extracted workflow candidates (38 candidate steps)
  1. 07
    Action

    Step 2: Define the Playbook Structure

    Source-described action candidate under “Step 2: Define the Playbook Structure”; not verified execution.

  2. 08
    Output

    Step 3: Write Decision Trees and Escalation Criteria

    Source-described output candidate under “Step 3: Write Decision Trees and Escalation Criteria”; not verified execution.

  3. 09
    Action

    Any P1 incident: Immediate escalation to IR lead and CISO

    Source-described action candidate under “Step 3: Write Decision Trees and Escalation Criteria”; not verified execution.

  4. 10
    Action

    Data exfiltration confirmed: Legal counsel and privacy officer notified

    Source-described action candidate under “Step 3: Write Decision Trees and Escalation Criteria”; not verified execution.

  5. 11
    Action

    Customer data involved: Customer notification process activated

    Source-described action candidate under “Step 3: Write Decision Trees and Escalation Criteria”; not verified execution.

  6. 12
    Action

    Third-party involvement: Vendor security contact engaged

    Source-described action candidate under “Step 3: Write Decision Trees and Escalation Criteria”; not verified execution.

  7. 13
    Action

    Law enforcement needed: General counsel authorizes before contact

    Source-described action candidate under “Step 3: Write Decision Trees and Escalation Criteria”; not verified execution.

  8. 14
    Action

    Step 4: Define Specific Technical Procedures

    Source-described action candidate under “Step 4: Define Specific Technical Procedures”; not verified execution.

  9. 15
    Output

    Write tool-specific instructions for each step (not generic guidance):

    Source-described output candidate under “Step 4: Define Specific Technical Procedures”; not verified execution.

  10. 16
    Action

    Step 5: Integrate with SOAR Platform

    Source-described action candidate under “Step 5: Integrate with SOAR Platform”; not verified execution.

  11. 17
    Action

    Map each playbook step to a SOAR action (API call, script, human decision point)

    Source-described action candidate under “Step 5: Integrate with SOAR Platform”; not verified execution.

  12. 18
    Action

    Define automation boundaries (what runs automatically vs. what requires analyst approval)

    Source-described action candidate under “Step 5: Integrate with SOAR Platform”; not verified execution.

  13. 19
    Action

    Build enrichment automations for the triage phase

    Source-described action candidate under “Step 5: Integrate with SOAR Platform”; not verified execution.

  14. 20
    Action

    Create containment automations with approval gates for high-impact actions

    Source-described action candidate under “Step 5: Integrate with SOAR Platform”; not verified execution.

  15. 21
    Action

    Configure notification automations for stakeholder communication

    Source-described action candidate under “Step 5: Integrate with SOAR Platform”; not verified execution.

  16. 22
    Action

    Step 6: Test and Maintain the Playbook

    Source-described action candidate under “Step 6: Test and Maintain the Playbook”; not verified execution.

  17. 23
    Action

    Validate the playbook through exercises and maintain currency:

    Source-described action candidate under “Step 6: Test and Maintain the Playbook”; not verified execution.

  18. 24
    Action

    Conduct tabletop exercises with the IR team walking through the playbook

    Source-described action candidate under “Step 6: Test and Maintain the Playbook”; not verified execution.

  19. 25
    Action

    Perform live-fire exercises simulating the incident type in a test environment

    Source-described action candidate under “Step 6: Test and Maintain the Playbook”; not verified execution.

  20. 26
    Action

    Review and update after every real incident that uses the playbook

    Source-described action candidate under “Step 6: Test and Maintain the Playbook”; not verified execution.

  21. 27
    Action

    Schedule quarterly reviews for accuracy of contact lists, tool procedures, and escalation paths

    Source-described action candidate under “Step 6: Test and Maintain the Playbook”; not verified execution.

  22. 28
    Action

    Track playbook metrics: mean time to contain, mean time to resolve, false positive rate

    Source-described action candidate under “Step 6: Test and Maintain the Playbook”; not verified execution.

  23. 29
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  24. 30
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  25. 31
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  26. 32
    Action

    Interview SOC analysts to document their current ad hoc process

    Source-described action candidate under “Scenario: Building a Phishing Response Playbook from Scratch”; not verified execution.

  27. 33
    Action

    Define the trigger: user reports phishing email via abuse@ mailbox or phishing button

    Source-described action candidate under “Scenario: Building a Phishing Response Playbook from Scratch”; not verified execution.

  28. 34
    Output

    Write triage steps: extract email headers, check sender reputation, analyze URLs/attachments in sandbox

    Source-described output candidate under “Scenario: Building a Phishing Response Playbook from Scratch”; not verified execution.

  29. 35
    Decision

    Define containment: quarantine email from all mailboxes, block sender domain, reset passwords if credentials entered

    Source-described decision candidate under “Scenario: Building a Phishing Response Playbook from Scratch”; not verified execution.

  30. 36
    Action

    Build SOAR automation: auto-extract IOCs from reported email, enrich via VirusTotal, create case in TheHive

    Source-described action candidate under “Scenario: Building a Phishing Response Playbook from Scratch”; not verified execution.

  31. 37
    Action

    Test with simulated phishing email and measure response time improvement

    Source-described action candidate under “Scenario: Building a Phishing Response Playbook from Scratch”; not verified execution.

  32. 38
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

24 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

15 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 15 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

8 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/building-incident-response-playbook/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/building-incident-response-playbook/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/building-incident-response-playbook
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.