Back to catalog
Static reviewDevelopment

Skill dossier

performing-ransomware-tabletop-exercise

Source declaration

Plans and facilitates tabletop exercises simulating ransomware incidents, using realistic scenarios based on threat actors like LockBit and ALPHV/BlackCat with injects covering double extortion and backup destruction, then evaluates responses against NIST CSF and CISA guidelines. Use when planning or running a ransomware tabletop exercise or incident response readiness drill.

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

Plans and facilitates tabletop exercises simulating ransomware incidents, using realistic scenarios based on threat actors like LockBit and ALPHV/BlackCat with injects covering double extortion and backup destruction, then evaluates responses against NIST CSF and CISA guidelines. Use when planning or running a ransomware tabletop exercise or incident response readiness drill.

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.

Plans and facilitates tabletop exercises simulating ransomware incidents, using realistic scenarios based on threat actors like LockBit and ALPHV/BlackCat with injects covering double extortion and backup destruction, then evaluates responses against NIST CSF and CISA guidelines. Use when planning or running a ransomware tabletop exercise or incident response readiness drill. 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/performing-ransomware-tabletop-exercise/SKILL.md:L76]
  • Step 1: Design the Exercise Scenario [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-tabletop-exercise/SKILL.md:L78]
  • Step 2: Prepare Exercise Materials [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-tabletop-exercise/SKILL.md:L113]
  • Step 3: Facilitate the Exercise [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-tabletop-exercise/SKILL.md:L131]
  • Step 4: Evaluate and Score Responses [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-tabletop-exercise/SKILL.md:L163]
  • Step 5: Document Findings and Remediation Plan [Source statement; provisional, not tested. Evidence: skills/performing-ransomware-tabletop-exercise/SKILL.md:L178]

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/performing-ransomware-tabletop-exercise/SKILL.md:L1-L54]

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
8
Markdown files
5
scripts
2
references
4
Size
61.5 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-ransomware-tabletop-exercise/assets/template.mdReference2.2 KB
skills/performing-ransomware-tabletop-exercise/LICENSEOther11 KB
skills/performing-ransomware-tabletop-exercise/references/api-reference.mdReference2.6 KB
skills/performing-ransomware-tabletop-exercise/references/standards.mdReference2.2 KB
skills/performing-ransomware-tabletop-exercise/references/workflows.mdReference3.1 KB
skills/performing-ransomware-tabletop-exercise/scripts/agent.pyScript6.4 KB
skills/performing-ransomware-tabletop-exercise/scripts/process.pyScript22.5 KB
skills/performing-ransomware-tabletop-exercise/SKILL.mdInstruction11.5 KB

SKILL.md frontmatter

{
  "name": "performing-ransomware-tabletop-exercise",
  "description": "Plans and facilitates tabletop exercises simulating ransomware incidents, using realistic scenarios based on threat actors like LockBit and ALPHV/BlackCat with injects covering double extortion and backup destruction, then evaluates responses against NIST CSF and CISA guidelines. Use when planning or running a ransomware tabletop exercise or incident response readiness drill.\n",
  "domain": "cybersecurity",
  "subdomain": "ransomware-defense",
  "tags": [
    "ransomware",
    "incident-response",
    "tabletop-exercise",
    "defense",
    "preparedness"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.DS-11",
    "RS.MA-01",
    "RC.RP-01",
    "PR.IR-01"
  ],
  "mitre_attack": [
    "T1078",
    "T1190",
    "T1059",
    "T1486",
    "T1490"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "positioning",
      "monetization"
    ],
    "techniques": [
      {
        "id": "T1531",
        "name": "Account Access Removal",
        "tactic": "positioning",
        "source": "attack"
      },
      {
        "id": "F1018",
        "name": "Convert to Cryptocurrency",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "F1047",
        "name": "Transfer of funds",
        "tactic": "monetization",
        "source": "f3"
      },
      {
        "id": "F1017.001",
        "name": "Conversion to Physical Monetary Instruments: Cash",
        "tactic": "monetization",
        "source": "f3"
      }
    ]
  }
}

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: Design the Exercise Scenario

    Source-described action candidate under “Step 1: Design the Exercise Scenario”; not verified execution.

  4. 04
    Action

    Threat actor group and known TTPs

    Source-described action candidate under “Step 1: Design the Exercise Scenario”; not verified execution.

  5. 05
    Action

    Percentage of infrastructure encrypted

    Source-described action candidate under “Step 1: Design the Exercise Scenario”; not verified execution.

  6. 06
    Decision

    Whether backups are intact, partially compromised, or fully destroyed

    Source-described decision candidate under “Step 1: Design the Exercise Scenario”; not verified execution.

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

    Type of data exfiltrated (PII, PHI, financial, trade secrets)

    Source-described action candidate under “Step 1: Design the Exercise Scenario”; not verified execution.

  2. 08
    Action

    Applicable regulatory frameworks (GDPR, HIPAA, PCI DSS, SEC rules)

    Source-described action candidate under “Step 1: Design the Exercise Scenario”; not verified execution.

  3. 09
    Action

    Ransom amount and payment deadline

    Source-described action candidate under “Step 1: Design the Exercise Scenario”; not verified execution.

  4. 10
    Action

    Step 2: Prepare Exercise Materials

    Source-described action candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  5. 11
    Action

    Create the following documents for participants:

    Source-described action candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  6. 12
    Action

    Exercise Overview Briefing - Ground rules, objectives, scope, and participants

    Source-described action candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  7. 13
    Action

    Situation Reports (SITREPs) - One per phase, distributed as the exercise progresses

    Source-described action candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  8. 14
    Action

    Inject Cards - New information introduced at specific times to force decision-making

    Source-described action candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  9. 15
    Action

    Decision Point Worksheets - Structured forms for documenting group decisions

    Source-described action candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  10. 16
    Action

    Evaluation Scorecard - Criteria for assessing response quality

    Source-described action candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  11. 17
    Decision

    When to activate the incident response team

    Source-described decision candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  12. 18
    Decision

    Whether to shut down systems or contain selectively

    Source-described decision candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  13. 19
    Decision

    Whether to engage law enforcement (FBI IC3, CISA)

    Source-described decision candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  14. 20
    Decision

    Whether to pay the ransom and under what conditions

    Source-described decision candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  15. 21
    Decision

    When and how to notify regulators, customers, and the public

    Source-described decision candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  16. 22
    Action

    How to prioritize system recovery order

    Source-described action candidate under “Step 2: Prepare Exercise Materials”; not verified execution.

  17. 23
    Action

    Step 3: Facilitate the Exercise

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  18. 24
    Output

    Present each phase scenario and distribute SITREPs

    Source-described output candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  19. 25
    Action

    Introduce injects at predetermined times to increase pressure

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  20. 26
    Action

    Ask probing questions to test decision-making reasoning

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  21. 27
    Action

    Ensure all participant groups contribute (prevent IT from dominating)

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  22. 28
    Action

    Document all decisions, rationales, and action items

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  23. 29
    Action

    Track time management (many teams lose time on early phases)

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  24. 30
    Action

    Who makes the call to declare an incident? What criteria trigger it?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  25. 31
    Action

    How do we determine the scope of compromise from initial alerts?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  26. 32
    Action

    Do we have the forensic capability to investigate or do we need external help?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  27. 33
    Action

    What is our communication plan for employees? Do they know not to turn on affected machines?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  28. 34
    Action

    Have we isolated the network to prevent further encryption?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  29. 35
    Action

    Who authorizes system shutdowns that impact business operations?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  30. 36
    Action

    Under what conditions would we consider paying the ransom?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  31. 37
    Action

    What are the legal obligations for notification at this point?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  32. 38
    Action

    How do we handle the public leak of customer data?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  33. 39
    Action

    What is the recovery priority order? Is it documented or decided ad hoc?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  34. 40
    Action

    How long until critical business operations resume?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  35. 41
    Action

    What evidence preservation is required for law enforcement and insurance?

    Source-described action candidate under “Step 3: Facilitate the Exercise”; not verified execution.

  36. 42
    Action

    Step 4: Evaluate and Score Responses

    Source-described action candidate under “Step 4: Evaluate and Score Responses”; not verified execution.

  37. 43
    Action

    Step 5: Document Findings and Remediation Plan

    Source-described action candidate under “Step 5: Document Findings and Remediation Plan”; not verified execution.

  38. 44
    Action

    Exercise overview and objectives

    Source-described action candidate under “Step 5: Document Findings and Remediation Plan”; not verified execution.

  39. 45
    Action

    Scenario summary and injects

    Source-described action candidate under “Step 5: Document Findings and Remediation Plan”; not verified execution.

  40. 46
    Action

    Key decisions made and rationale

    Source-described action candidate under “Step 5: Document Findings and Remediation Plan”; not verified execution.

  41. 47
    Action

    Strengths observed

    Source-described action candidate under “Step 5: Document Findings and Remediation Plan”; not verified execution.

  42. 48
    Action

    Gaps identified with severity rating

    Source-described action candidate under “Step 5: Document Findings and Remediation Plan”; not verified execution.

  43. 49
    Action

    Remediation actions with owners and deadlines

    Source-described action candidate under “Step 5: Document Findings and Remediation Plan”; not verified execution.

  44. 50
    Decision

    Comparison to previous exercise results (if applicable)

    Source-described decision candidate under “Step 5: Document Findings and Remediation Plan”; not verified execution.

  45. 51
    Action

    Key Concepts

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

  46. 52
    Action

    Tools & Systems

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

  47. 53
    Action

    Common Scenarios

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

  48. 54
    Action

    Design scenario based on Cl0p MOO (Managed Operations Operator) TTPs: exploitation of MOVEit vulnerability for initial access, data exfiltration of 500,000 patient records, followed by encryption of EMR database servers

    Source-described action candidate under “Scenario: Healthcare System Double Extortion Exercise”; not verified execution.

  49. 55
    Action

    Participants: CISO, CIO, CMO (Chief Medical Officer), General Counsel, VP Communications, Director of Clinical Operations, Privacy Officer, External IR firm representative

    Source-described action candidate under “Scenario: Healthcare System Double Extortion Exercise”; not verified execution.

  50. 56
    Action

    Phase 1 inject: EMR system down, emergency department diverting patients to neighboring hospital

    Source-described action candidate under “Scenario: Healthcare System Double Extortion Exercise”; not verified execution.

  51. 57
    Action

    Phase 2 inject: HHS OCR (Office for Civil Rights) contacts organization about reports of patient data on dark web

    Source-described action candidate under “Scenario: Healthcare System Double Extortion Exercise”; not verified execution.

  52. 58
    Action

    Phase 3 inject: Attacker provides decryption key sample for $3.5M, 48-hour deadline

    Source-described action candidate under “Scenario: Healthcare System Double Extortion Exercise”; not verified execution.

  53. 59
    Action

    Key finding: Organization lacks documented criteria for ransom payment decision and had not pre-identified an OFAC-compliant payment mechanism

    Source-described action candidate under “Scenario: Healthcare System Double Extortion Exercise”; not verified execution.

  54. 60
    Action

    Remediation: Establish payment decision framework, pre-engage ransomware negotiation firm, update HIPAA breach notification procedures with specific timelines

    Source-described action candidate under “Scenario: Healthcare System Double Extortion Exercise”; not verified execution.

  55. 61
    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

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

23 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 23 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/performing-ransomware-tabletop-exercise/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 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/performing-ransomware-tabletop-exercise/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/performing-ransomware-tabletop-exercise
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.