implementing-ransomware-backup-strategy

Featured

Designs and implements a ransomware-resilient backup strategy following the 3-2-1-1-0 methodology (3 copies, 2 media types, 1 offsite, 1 immutable/air-gapped, 0 errors on restore verification). Configures backup schedules aligned to RPO/RTO requirements, implements backup credential isolation to prevent ransomware from compromising backup infrastructure, and establishes automated restore testing. Activates for requests involving ransomware backup planning, backup resilience, air-gapped backup design, or backup recovery point objective configuration.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Implementing Ransomware Backup Strategy ## When to Use - Designing backup architecture that withstands ransomware encryption and deletion attempts - Migrating from traditional backup to ransomware-resilient backup with immutable storage - Establishing RPO/RTO targets for critical systems and validating them through restore testing - Isolating backup credentials and infrastructure from the production Active Directory domain - Meeting cyber insurance requirements for backup resilience and tested recovery capabilities **Do not use** as a substitute for endpoint protection, network segmentation, or incident response planning. Backups are a last line of defense, not a primary prevention control. ## Prerequisites - Inventory of critical systems, applications, and data classified by business impact (Tier 1/2/3) - Defined RPO (Recovery Point Objective) and RTO (Recovery Time Objective) per tier - Backup software supporting immutable repositories (Veeam 12+, Commvault, Rubrik, Cohesity) - Isolated backup network segment or air-gapped storage infrastructure - Separate backup admin credentials not joined to the production AD domain ## Workflow ### Step 1: Classify Assets and Define Recovery Objectives Map all systems into recovery tiers based on business impact: | Tier | Examples | RPO | RTO | Backup Frequency | |------|----------|-----|-----|------------------| | Tier 1 (Critical) | Domain controllers, ERP, databases | 1 hour | 4 hours | Hourly incremental, daily full | | Ti...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

recovering-from-ransomware-attack

Executes structured recovery from a ransomware incident following NIST and CISA frameworks, including environment isolation, forensic evidence preservation, clean infrastructure rebuild, prioritized system restoration from verified backups, credential reset, and validation against re-infection. Covers Active Directory recovery, database restoration, and application stack rebuild in dependency order. Activates for requests involving ransomware recovery, post-encryption restoration, or disaster recovery from ransomware.

36,355 Updated 2 months ago
mukul975
AI & Automation Listed

backup-disaster-recovery

Design backups that actually work when they are needed. Covers RPO and RTO definition, the 3-2-1 rule, encryption before leaving the host, ransomware-resistant immutable storage, restore drills, and the split between operational and legal retention. Invoke when 'we have backups but nobody has restored them' is true, after a near-miss, or before a major migration.

21 Updated 3 weeks ago
GoldenWing-360
AI & Automation Featured

implementing-immutable-backup-with-restic

Implements immutable backup strategy using restic with S3-compatible storage and object lock for ransomware-resistant data protection. Automates backup creation, integrity verification via restic check --read-data, snapshot retention policy enforcement, and restore testing. Integrates with AWS S3 Object Lock, MinIO, and Backblaze B2 for WORM (Write Once Read Many) storage that prevents backup deletion or encryption by ransomware actors.

36,355 Updated 2 months ago
mukul975