Back to catalog
Static reviewDevelopment

Skill dossier

testing-ransomware-recovery-procedures

Source declaration

Tests and validates ransomware recovery procedures - backup restore operations (e.g. with Restic), RTO/RPO target verification, recovery sequencing, and clean-restore validation - to confirm organizational resilience against destructive ransomware attacks. Use when validating that recovery plans work under realistic conditions, measuring RTO/RPO against business requirements, or testing restore integrity after simulated encryption.

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

Tests and validates ransomware recovery procedures - backup restore operations (e.g. with Restic), RTO/RPO target verification, recovery sequencing, and clean-restore validation - to confirm organizational resilience against destructive ransomware attacks. Use when validating that recovery plans work under realistic conditions, measuring RTO/RPO against business requirements, or testing restore integrity after simulated encryption.

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.

Tests and validates ransomware recovery procedures - backup restore operations (e.g. with Restic), RTO/RPO target verification, recovery sequencing, and clean-restore validation - to confirm organizational resilience against destructive ransomware attacks. Use when validating that recovery plans work under realistic conditions, measuring RTO/RPO against business requirements, or testing restore integrity after simulated encryption. 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

  • Testing Ransomware Recovery Procedures [Source statement; provisional, not tested. Evidence: skills/testing-ransomware-recovery-procedures/SKILL.md:L55]
  • Workflow [Source statement; provisional, not tested. Evidence: skills/testing-ransomware-recovery-procedures/SKILL.md:L76]
  • Step 1: Define Recovery Test Scope [Source statement; provisional, not tested. Evidence: skills/testing-ransomware-recovery-procedures/SKILL.md:L78]
  • Step 2: Prepare Test Environment [Source statement; provisional, not tested. Evidence: skills/testing-ransomware-recovery-procedures/SKILL.md:L89]
  • Step 3: Execute Restore and Measure RTO [Source statement; provisional, not tested. Evidence: skills/testing-ransomware-recovery-procedures/SKILL.md:L102]
  • Step 4: Validate Data Integrity Post-Restore [Source statement; provisional, not tested. Evidence: skills/testing-ransomware-recovery-procedures/SKILL.md:L124]
  • Step 5: Test Credential Rotation and Security Hardening [Source statement; provisional, not tested. Evidence: skills/testing-ransomware-recovery-procedures/SKILL.md:L140]
  • Step 6: Document Results and Calculate Gap [Source statement; provisional, not tested. Evidence: skills/testing-ransomware-recovery-procedures/SKILL.md:L150]

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/testing-ransomware-recovery-procedures/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
4
Markdown files
2
scripts
1
references
1
Size
33.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/testing-ransomware-recovery-procedures/LICENSEOther11 KB
skills/testing-ransomware-recovery-procedures/references/api-reference.mdReference3.8 KB
skills/testing-ransomware-recovery-procedures/scripts/agent.pyScript11.3 KB
skills/testing-ransomware-recovery-procedures/SKILL.mdInstruction7.6 KB

SKILL.md frontmatter

{
  "name": "testing-ransomware-recovery-procedures",
  "description": "Tests and validates ransomware recovery procedures - backup restore operations (e.g. with Restic), RTO/RPO target verification, recovery sequencing, and clean-restore validation - to confirm organizational resilience against destructive ransomware attacks. Use when validating that recovery plans work under realistic conditions, measuring RTO/RPO against business requirements, or testing restore integrity after simulated encryption.",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "incident-response",
    "ransomware",
    "disaster-recovery",
    "backup",
    "rto",
    "rpo",
    "resilience"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ],
  "mitre_attack": [
    "T1486",
    "T1490",
    "T1070",
    "T1078",
    "T1489"
  ],
  "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
    Action

    Testing Ransomware Recovery Procedures

    Source-described action candidate under “Testing Ransomware Recovery Procedures”; not verified execution.

  2. 02
    Decision

    When to Use

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

  3. 03
    Action

    Workflow

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

  4. 04
    Action

    Step 1: Define Recovery Test Scope

    Source-described action candidate under “Step 1: Define Recovery Test Scope”; not verified execution.

  5. 05
    Action

    Step 2: Prepare Test Environment

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

  6. 06
    Action

    Step 3: Execute Restore and Measure RTO

    Source-described action candidate under “Step 3: Execute Restore and Measure RTO”; not verified execution.

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

    Detection to Decision - Time from simulated alert to restore decision

    Source-described action candidate under “Step 3: Execute Restore and Measure RTO”; not verified execution.

  2. 08
    Action

    Backup Locate - Time to identify and select the correct clean restore point

    Source-described action candidate under “Step 3: Execute Restore and Measure RTO”; not verified execution.

  3. 09
    Action

    Restore Execution - Time to restore data/VM/application from backup

    Source-described action candidate under “Step 3: Execute Restore and Measure RTO”; not verified execution.

  4. 10
    Action

    Validation - Time to verify data integrity and application functionality

    Source-described action candidate under “Step 3: Execute Restore and Measure RTO”; not verified execution.

  5. 11
    Action

    Service Restoration - Time until the system is fully operational

    Source-described action candidate under “Step 3: Execute Restore and Measure RTO”; not verified execution.

  6. 12
    Action

    Step 4: Validate Data Integrity Post-Restore

    Source-described action candidate under “Step 4: Validate Data Integrity Post-Restore”; not verified execution.

  7. 13
    Action

    Step 5: Test Credential Rotation and Security Hardening

    Source-described action candidate under “Step 5: Test Credential Rotation and Security Hardening”; not verified execution.

  8. 14
    Action

    Rotate all service account passwords and API keys

    Source-described action candidate under “Step 5: Test Credential Rotation and Security Hardening”; not verified execution.

  9. 15
    Action

    Verify MFA is enabled on all administrative accounts

    Source-described action candidate under “Step 5: Test Credential Rotation and Security Hardening”; not verified execution.

  10. 16
    Action

    Confirm EDR/AV agents are running and reporting to management console

    Source-described action candidate under “Step 5: Test Credential Rotation and Security Hardening”; not verified execution.

  11. 17
    Action

    Validate firewall rules block known C2 indicators

    Source-described action candidate under “Step 5: Test Credential Rotation and Security Hardening”; not verified execution.

  12. 18
    Action

    Check that restored systems have latest security patches

    Source-described action candidate under “Step 5: Test Credential Rotation and Security Hardening”; not verified execution.

  13. 19
    Action

    Step 6: Document Results and Calculate Gap

    Source-described action candidate under “Step 6: Document Results and Calculate Gap”; not verified execution.

  14. 20
    Action

    Key Concepts

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

  15. 21
    Action

    Tools & Systems

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

  16. 22
    Action

    Common Pitfalls

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

  17. 23
    Action

    References

    Source-described action candidate under “References”; 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

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

Network access is mentioned

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

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

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/testing-ransomware-recovery-procedures/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/testing-ransomware-recovery-procedures/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/testing-ransomware-recovery-procedures
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.