agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/business-continuity/backup-assurance/SKILL.md

backup-assurance

Skill0 starsChanged 15 days agoMITView on GitHub

Verify that backups will actually restore after ransomware or disaster — coverage vs. critical systems, 3-2-1-1-0 rule, immutability (object lock, hardened repositories), credential isolation of backup infrastructure, encryption, restore testing with measured RTO/RPO, and backup-attack detection. Use when assessing backup resilience, preparing for ransomware, or after backup deletion attempts.

The file

Files
SKILL.md

Backup Assurance

3-2-1-1-0

3 copies, 2 media/types, 1 off-site, 1 immutable or offline, 0 errors after verified restore tests.

Assessment checklist

AreaCheck
CoverageEvery system in critical-service-mapping has backups meeting its RPO; SaaS data (M365, Google, Salesforce) and cloud resources (databases, buckets, Kubernetes state/etcd, IaC state) included; identity systems (AD system state for forest recovery)
ImmutabilityS3 Object Lock (compliance mode), Azure immutable blob storage, hardened Linux repositories (e.g. Veeam hardened repo), tape/air gap; retention long enough to predate typical dwell time (≥ 30 days)
IsolationBackup servers not domain-joined to production AD (or separate admin forest), separate MFA-protected admin accounts, consoles not reachable from user networks, backup credentials not stored on production hosts
EncryptionBackups encrypted; keys stored separately and recoverable when primary IdP/KMS is down
MonitoringAlerts on backup job failures, retention changes, deletion of restore points, MFA disable on backup consoles, mass deletion API calls
Restore testingRegular tests per tier (critical quarterly), including full system restores and AD forest recovery drills; measured actual RTO vs. target
DocumentationRestore runbooks accessible offline

Ransomware-specific

Attackers target backups first: Veeam/other backup server CVEs, deleting VSS copies, wiping repositories, changing retention, disabling immutability. Ensure detections exist (ransomware-response precursors) and that at least one copy is out of reach of domain admin credentials.

Restore test record

System | Backup source | Restore point age | Started | Completed | RTO target/actual | Data validated by | Issues

Related skills

ransomware-recovery, recovery-exercise, critical-service-mapping, ransomware-response

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.