Back to catalog
Static reviewDevelopment

Skill dossier

implementing-ransomware-backup-strategy

Source declaration

Designs a ransomware-resilient backup strategy using the 3-2-1-1-0 methodology (3 copies, 2 media types, 1 offsite, 1 immutable/air-gapped, 0 restore errors), configuring RPO/RTO-aligned schedules, isolating backup credentials, and automating restore testing. Use when planning ransomware backup resilience or air-gapped/immutable backup architecture.

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

Designs a ransomware-resilient backup strategy using the 3-2-1-1-0 methodology (3 copies, 2 media types, 1 offsite, 1 immutable/air-gapped, 0 restore errors), configuring RPO/RTO-aligned schedules, isolating backup credentials, and automating restore testing. Use when planning ransomware backup resilience or air-gapped/immutable backup architecture.

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 a ransomware-resilient backup strategy using the 3-2-1-1-0 methodology (3 copies, 2 media types, 1 offsite, 1 immutable/air-gapped, 0 restore errors), configuring RPO/RTO-aligned schedules, isolating backup credentials, and automating restore testing. Use when planning ransomware backup resilience or air-gapped/immutable backup architecture. 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/implementing-ransomware-backup-strategy/SKILL.md:L86]
  • Step 1: Classify Assets and Define Recovery Objectives [Source statement; provisional, not tested. Evidence: skills/implementing-ransomware-backup-strategy/SKILL.md:L88]
  • Step 2: Implement 3-2-1-1-0 Architecture [Source statement; provisional, not tested. Evidence: skills/implementing-ransomware-backup-strategy/SKILL.md:L100]
  • Step 3: Isolate Backup Credentials [Source statement; provisional, not tested. Evidence: skills/implementing-ransomware-backup-strategy/SKILL.md:L145]
  • Step 4: Configure Immutable Storage [Source statement; provisional, not tested. Evidence: skills/implementing-ransomware-backup-strategy/SKILL.md:L167]
  • Step 5: Automate Restore Testing [Source statement; provisional, not tested. Evidence: skills/implementing-ransomware-backup-strategy/SKILL.md:L221]

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/implementing-ransomware-backup-strategy/SKILL.md:L1-L65]

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

File inventory

PathTypeBytes
skills/implementing-ransomware-backup-strategy/assets/template.mdReference3.7 KB
skills/implementing-ransomware-backup-strategy/LICENSEOther11 KB
skills/implementing-ransomware-backup-strategy/references/api-reference.mdReference6.5 KB
skills/implementing-ransomware-backup-strategy/references/standards.mdReference2.5 KB
skills/implementing-ransomware-backup-strategy/references/workflows.mdReference3.7 KB
skills/implementing-ransomware-backup-strategy/scripts/agent.pyScript11.8 KB
skills/implementing-ransomware-backup-strategy/scripts/process.pyScript22.3 KB
skills/implementing-ransomware-backup-strategy/SKILL.mdInstruction12.2 KB

SKILL.md frontmatter

{
  "name": "implementing-ransomware-backup-strategy",
  "description": "Designs a ransomware-resilient backup strategy using the 3-2-1-1-0 methodology (3 copies, 2 media types, 1 offsite, 1 immutable/air-gapped, 0 restore errors), configuring RPO/RTO-aligned schedules, isolating backup credentials, and automating restore testing. Use when planning ransomware backup resilience or air-gapped/immutable backup architecture.\n",
  "domain": "cybersecurity",
  "subdomain": "ransomware-defense",
  "tags": [
    "ransomware",
    "backup",
    "incident-response",
    "defense",
    "recovery",
    "immutable-storage"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_ai_rmf": [
    "MEASURE-2.7",
    "MAP-5.1",
    "MANAGE-2.4",
    "MANAGE-3.1",
    "MEASURE-3.1"
  ],
  "atlas_techniques": [
    "AML.T0070",
    "AML.T0066",
    "AML.T0082"
  ],
  "nist_csf": [
    "PR.DS-11",
    "RS.MA-01",
    "RC.RP-01",
    "PR.IR-01"
  ],
  "mitre_attack": [
    "T1078",
    "T1190",
    "T1059",
    "T1003",
    "T1110"
  ],
  "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: Classify Assets and Define Recovery Objectives

    Source-described action candidate under “Step 1: Classify Assets and Define Recovery Objectives”; not verified execution.

  4. 04
    Action

    Step 2: Implement 3-2-1-1-0 Architecture

    Source-described action candidate under “Step 2: Implement 3-2-1-1-0 Architecture”; not verified execution.

  5. 05
    Action

    Step 3: Isolate Backup Credentials

    Source-described action candidate under “Step 3: Isolate Backup Credentials”; not verified execution.

  6. 06
    Action

    Separate backup admin accounts from the production AD domain. Use local accounts on backup servers or a dedicated backup management domain.

    Source-described action candidate under “Step 3: Isolate Backup Credentials”; not verified execution.

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

    Dedicated backup network segment with firewall rules allowing only backup traffic (specific ports, specific source/destination IPs).

    Source-described input candidate under “Step 3: Isolate Backup Credentials”; not verified execution.

  2. 08
    Action

    MFA on backup console access using hardware tokens or authenticator apps, not SMS.

    Source-described action candidate under “Step 3: Isolate Backup Credentials”; not verified execution.

  3. 09
    Action

    Disable RDP on backup servers. Use out-of-band management (iLO/iDRAC/IPMI) for emergency access.

    Source-described action candidate under “Step 3: Isolate Backup Credentials”; not verified execution.

  4. 10
    Action

    Remove backup servers from domain or place in a dedicated OU with restricted GPO inheritance.

    Source-described action candidate under “Step 3: Isolate Backup Credentials”; not verified execution.

  5. 11
    Action

    Step 4: Configure Immutable Storage

    Source-described action candidate under “Step 4: Configure Immutable Storage”; not verified execution.

  6. 12
    Action

    Step 5: Automate Restore Testing

    Source-described action candidate under “Step 5: Automate Restore Testing”; not verified execution.

  7. 13
    Action

    Key Concepts

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

  8. 14
    Action

    Tools & Systems

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

  9. 15
    Action

    Common Scenarios

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

  10. 16
    Action

    Classify all 500 servers into three tiers: 50 Tier 1 (core banking, AD, DNS), 200 Tier 2 (email, file shares, web), 250 Tier 3 (dev, test, archive)

    Source-described action candidate under “Scenario: Financial Services Firm Implementing Ransomware-Resilient Backup”; not verified execution.

  11. 17
    Action

    Deploy Veeam Hardened Linux Repository on dedicated Ubuntu 22.04 servers with XFS immutability for primary backup

    Source-described action candidate under “Scenario: Financial Services Firm Implementing Ransomware-Resilient Backup”; not verified execution.

  12. 18
    Action

    Configure S3 Object Lock in Compliance mode for 30-day immutable cloud copy with Veeam Scale-Out Repository capacity tier

    Source-described action candidate under “Scenario: Financial Services Firm Implementing Ransomware-Resilient Backup”; not verified execution.

  13. 19
    Action

    Establish quarterly tape rotation to Iron Mountain for 7-year regulatory retention

    Source-described action candidate under “Scenario: Financial Services Firm Implementing Ransomware-Resilient Backup”; not verified execution.

  14. 20
    Action

    Remove all backup servers from the production AD domain and create isolated backup admin accounts with hardware MFA tokens

    Source-described action candidate under “Scenario: Financial Services Firm Implementing Ransomware-Resilient Backup”; not verified execution.

  15. 21
    Action

    Deploy SureBackup jobs: weekly for Tier 1, monthly for Tier 2, quarterly for Tier 3

    Source-described action candidate under “Scenario: Financial Services Firm Implementing Ransomware-Resilient Backup”; not verified execution.

  16. 22
    Action

    Conduct annual full recovery drill restoring AD, DNS, core banking, and dependent applications to validate documented RTO

    Source-described action candidate under “Scenario: Financial Services Firm Implementing Ransomware-Resilient Backup”; not verified execution.

  17. 23
    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

57 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

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

2 occurrences

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 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

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

Elevated privileges are referenced

8 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. 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.

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/implementing-ransomware-backup-strategy/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/implementing-ransomware-backup-strategy/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/implementing-ransomware-backup-strategy
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.