Back to catalog
Static reviewDevelopment

Skill dossier

building-soc-playbook-for-ransomware

Source declaration

Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.

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

Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.

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.

Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques. 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-soc-playbook-for-ransomware/SKILL.md:L83]
  • Step 1: Define Detection Triggers [Source statement; provisional, not tested. Evidence: skills/building-soc-playbook-for-ransomware/SKILL.md:L85]
  • Step 2: Build Triage Decision Tree [Source statement; provisional, not tested. Evidence: skills/building-soc-playbook-for-ransomware/SKILL.md:L125]
  • Step 3: Containment Procedures [Source statement; provisional, not tested. Evidence: skills/building-soc-playbook-for-ransomware/SKILL.md:L148]
  • Step 4: Evidence Collection and Preservation [Source statement; provisional, not tested. Evidence: skills/building-soc-playbook-for-ransomware/SKILL.md:L191]
  • Step 5: Eradication and Recovery [Source statement; provisional, not tested. Evidence: skills/building-soc-playbook-for-ransomware/SKILL.md:L213]
  • Step 6: Post-Incident Documentation [Source statement; provisional, not tested. Evidence: skills/building-soc-playbook-for-ransomware/SKILL.md:L236]

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-soc-playbook-for-ransomware/SKILL.md:L1-L62]

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
30.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/building-soc-playbook-for-ransomware/LICENSEOther11 KB
skills/building-soc-playbook-for-ransomware/references/api-reference.mdReference2.2 KB
skills/building-soc-playbook-for-ransomware/scripts/agent.pyScript5.9 KB
skills/building-soc-playbook-for-ransomware/SKILL.mdInstruction11.6 KB

SKILL.md frontmatter

{
  "name": "building-soc-playbook-for-ransomware",
  "description": "Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.\n",
  "domain": "cybersecurity",
  "subdomain": "soc-operations",
  "tags": [
    "soc",
    "ransomware",
    "incident-response",
    "playbook",
    "nist",
    "mitre-attack",
    "containment"
  ],
  "mitre_attack": [
    "T1486",
    "T1490",
    "T1489",
    "T1566",
    "T1059.001"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access",
      "monetization"
    ],
    "techniques": [
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1110",
        "name": "Brute Force",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1018",
        "name": "Convert to Cryptocurrency",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "F1047",
        "name": "Transfer of funds",
        "tactic": "monetization",
        "source": "f3"
      }
    ]
  },
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Platform Hardening",
    "Restore Object",
    "Restore Configuration",
    "Restore Software",
    "Software Update"
  ],
  "nist_csf": [
    "DE.CM-01",
    "DE.AE-02",
    "RS.MA-01",
    "DE.AE-06"
  ]
}

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: Define Detection Triggers

    Source-described action candidate under “Step 1: Define Detection Triggers”; not verified execution.

  4. 04
    Action

    Create SIEM detection rules for early ransomware indicators:

    Source-described action candidate under “Step 1: Define Detection Triggers”; not verified execution.

  5. 05
    Action

    Step 2: Build Triage Decision Tree

    Source-described action candidate under “Step 2: Build Triage Decision Tree”; not verified execution.

  6. 06
    Action

    Step 3: Containment Procedures

    Source-described action candidate under “Step 3: Containment Procedures”; not verified execution.

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

    Step 4: Evidence Collection and Preservation

    Source-described action candidate under “Step 4: Evidence Collection and Preservation”; not verified execution.

  2. 08
    Action

    Step 5: Eradication and Recovery

    Source-described action candidate under “Step 5: Eradication and Recovery”; not verified execution.

  3. 09
    Input

    Upload encrypted sample and ransom note to ID Ransomware (https://id-ransomware.malwarehunterteam.com/)

    Source-described input candidate under “Step 5: Eradication and Recovery”; not verified execution.

  4. 10
    Action

    Check No More Ransom Project (https://www.nomoreransom.org/) for available decryptors

    Source-described action candidate under “Step 5: Eradication and Recovery”; not verified execution.

  5. 11
    Action

    Search for ransomware family IOCs in MalwareBazaar

    Source-described action candidate under “Step 5: Eradication and Recovery”; not verified execution.

  6. 12
    Action

    Verify backup integrity (offline/immutable backups not affected)

    Source-described action candidate under “Step 5: Eradication and Recovery”; not verified execution.

  7. 13
    Action

    Rebuild affected systems from known-good images

    Source-described action candidate under “Step 5: Eradication and Recovery”; not verified execution.

  8. 14
    Action

    Restore data from last clean backup

    Source-described action candidate under “Step 5: Eradication and Recovery”; not verified execution.

  9. 15
    Action

    Validate restored systems before reconnecting to network

    Source-described action candidate under “Step 5: Eradication and Recovery”; not verified execution.

  10. 16
    Action

    Monitor restored systems for 72 hours for reinfection

    Source-described action candidate under “Step 5: Eradication and Recovery”; not verified execution.

  11. 17
    Action

    Step 6: Post-Incident Documentation

    Source-described action candidate under “Step 6: Post-Incident Documentation”; not verified execution.

  12. 18
    Action

    Key Concepts

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

  13. 19
    Action

    Tools & Systems

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

  14. 20
    Action

    Common Scenarios

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

  15. 21
    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.

Items warrant review

27 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 useNot observed
Medium

Network access is mentioned

18 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 18 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

9 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 9 location(s) in the collected text; 3 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-soc-playbook-for-ransomware/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-soc-playbook-for-ransomware/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-soc-playbook-for-ransomware
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.